LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 11-06-2014, 03:24 AM   #1
andrixnet
Member
 
Registered: Oct 2012
Location: Romania
Distribution: Slackware
Posts: 115

Rep: Reputation: Disabled
Question slackpkg and SlackwareARM on RaspberryPI


I have a working slackwareARM-14.1 installation on a Raspberry PI. (fatdog guide).

Today I tried to update packages using slackpkg tool.
slackpkg update
This is what I get after downloading CHECKSUMS.md5.asc:
Code:
ERROR: Verification of the  gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of date
or has been tampered with.
A manual check with gpg on that file yields a valid signiture by an unknown key.

How can I get slackpkg to work in this case?
Is the mirror tampered with?
Is slackpkg interpreting something wrong?
 
Old 11-06-2014, 04:58 AM   #2
slacksam
Member
 
Registered: Oct 2012
Location: Germany
Distribution: Slackware, Salix, Manjaro, Arch
Posts: 152

Rep: Reputation: 22
I had the same issue on my RasPi with Slackware 14.1.
After setting CHECKGPG=off in /etc/slackpkg/slackpkg.conf I could make the update.
 
1 members found this post helpful.
Old 11-06-2014, 09:59 AM   #3
lems
Member
 
Registered: May 2004
Distribution: BSD
Posts: 269

Rep: Reputation: 119Reputation: 119
Just in case: did you run
Code:
slackpkg update gpg
before running slackpkg update ?
 
Old 11-06-2014, 10:41 AM   #4
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 854

Rep: Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642
Quote:
Originally Posted by andrixnet View Post
I have a working slackwareARM-14.1 installation on a Raspberry PI. (fatdog guide).

Today I tried to update packages using slackpkg tool.
slackpkg update
This is what I get after downloading CHECKSUMS.md5.asc:
Code:
ERROR: Verification of the  gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of date
or has been tampered with.
A manual check with gpg on that file yields a valid signiture by an unknown key.

How can I get slackpkg to work in this case?
Is the mirror tampered with?
Is slackpkg interpreting something wrong?
Upgrade slackpkg manually then re-run slackpkg.
 
Old 11-07-2014, 04:34 AM   #5
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 487
Blog Entries: 13

Rep: Reputation: 47
After upgrading slackpkg you may need to reedit the mirrors to uncomment your preferred one again.
 
Old 11-07-2014, 12:12 PM   #6
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 854

Rep: Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642
Quote:
Originally Posted by louigi600 View Post
After upgrading slackpkg you may need to reedit the mirrors to uncomment your preferred one again.
Looking at the slackpkg install script, this should not be necessary. It should leave behind a .new file if the packaged one doesn't match your edited one - which it won't since the packaged one has all of the mirror hosts commented out.
Is this not the case?
 
Old 11-07-2014, 12:57 PM   #7
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 487
Blog Entries: 13

Rep: Reputation: 47
Not sure if it's the case with the last update but I recall having to do that more then once.
It might be that slackpkg will ask you what to do with the .new files (even the ones you kept from previous installs/updates).
I get frustrated after the number of .new files grows and every now and then I decide to be prompted with actions for each and I may have accepted the new mirrors file accidentally or something like that ...

Next time I'll keep an eye out.
 
Old 11-07-2014, 05:11 PM   #8
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 854

Rep: Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642
Quote:
Originally Posted by louigi600 View Post
Not sure if it's the case with the last update but I recall having to do that more then once.
It might be that slackpkg will ask you what to do with the .new files (even the ones you kept from previous installs/updates).
I get frustrated after the number of .new files grows and every now and then I decide to be prompted with actions for each and I may have accepted the new mirrors file accidentally or something like that ...

Next time I'll keep an eye out.
If you upgradepkg slackpkg manually as I suggested, slackpkg cannot ask about the .new file so the mirror list will remain intact. Also presumably it won't try to update itself again since it's already at the correct version.

I have not used slackpkg but it seems logical.
 
Old 11-11-2014, 01:28 AM   #9
andrixnet
Member
 
Registered: Oct 2012
Location: Romania
Distribution: Slackware
Posts: 115

Original Poster
Rep: Reputation: Disabled
After I did the update, which included slackpkg itself, I did try again
Code:
slackpkg update
with option CHECKGPG=on

This time it worked perfectly.

I haven't encountered the same problem on the x86 platform however.
There might have been a small bug in slackpkg or a data inconsistency in the slackarm repository somehow.

Thank you all for the suggestions.
 
Old 11-11-2014, 01:41 AM   #10
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 854

Rep: Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642Reputation: 642
Quote:
Originally Posted by andrixnet View Post
After I did the update, which included slackpkg itself, I did try again
Code:
slackpkg update
with option CHECKGPG=on

This time it worked perfectly.

I haven't encountered the same problem on the x86 platform however.
There might have been a small bug in slackpkg or a data inconsistency in the slackarm repository somehow.

Thank you all for the suggestions.
You are encouraged to read the change log :-)
ftp://ftp.arm.slackware.com/slackwar.../ChangeLog.txt

Last edited by drmozes; 11-11-2014 at 02:15 AM.
 
Old 11-12-2014, 02:17 AM   #11
andrixnet
Member
 
Registered: Oct 2012
Location: Romania
Distribution: Slackware
Posts: 115

Original Poster
Rep: Reputation: Disabled
Totally missed that info. Thank you.
 
Old 11-22-2014, 06:22 PM   #12
OldHolborn
Member
 
Registered: Jul 2012
Distribution: Slackware
Posts: 187

Rep: Reputation: 153Reputation: 153
I got bitten by this too, yes, I too failed to fully read the changelog!

If you do as root "gpg --list-keys" you'll see

Slackware ARM (Slackware ARM Linux Project<mozes@slackware.com>

slackpkg from 14.0 however expects this

ARMedslack Security (ARMedslack Linux Project Security) <security@armedslack.org>

edit /usr/libexec/slackpkg/core-functions.sh and change line 126 accordingly then rerun slackpkg
 
Old 12-23-2014, 10:00 AM   #13
happycamper
LQ Newbie
 
Registered: Jul 2006
Distribution: Slackware
Posts: 1

Rep: Reputation: 0
I also ran into this problem recently when installing Slackware64 14.1 on a laptop. After running the initial 'slackpkg update', I thought that there might be an issue with one of the mirrors. But a quick Google search helped to identify the issue.

It was caused by the system clock being totally incorrect; it was set to sometime in 1980.. Check by running 'date', and checking its output.

Simple fix with 'ntpdate pool.ntp.org', and verified by running 'slackpkg update' again. All is well.

Although the primary issue addressed in this thread may not have been due to the date, I thought it would be useful to post here for any that may need it. This can also happen to Slackers running on a Pi.
 
  


Reply

Tags
gpg, signing, slackpkg, update


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
remote desktop to Raspberrypi boloo Linux - Newbie 3 11-05-2014 06:22 AM
SlackwareARM on RaspberryPI and soft/hard float andrixnet Slackware - ARM 20 10-08-2014 08:02 PM
[SOLVED] Slackpkg, Slackpkg Plus, Slackware 14.1 x86_64 install.log delay or slow to write bamunds Slackware 7 04-22-2014 11:12 AM
[SOLVED] typos in latest /etc/slackpkg/mirrors(.new) [slackpkg-2.82.0-noarch-8.tgz] wailingwailer Slackware 4 09-22-2012 04:04 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 12:22 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration