slackpkg and SlackwareARM on RaspberryPI

andrixnet · 11-06-2014, 03:24 AM

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?

slacksam · 11-06-2014, 04:58 AM

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.

lems · 11-06-2014, 09:59 AM

Just in case: did you run

Code:

slackpkg update gpg

before running « slackpkg update »?

drmozes · 11-06-2014, 10:41 AM

Quote:

Originally Posted by andrixnet

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.

louigi600 · 11-07-2014, 04:34 AM

After upgrading slackpkg you may need to reedit the mirrors to uncomment your preferred one again.

drmozes · 11-07-2014, 12:12 PM

Quote:

Originally Posted by louigi600

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?

louigi600 · 11-07-2014, 12:57 PM

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.

drmozes · 11-07-2014, 05:11 PM

Quote:

Originally Posted by louigi600

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.

andrixnet · 11-11-2014, 01:28 AM

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.

drmozes · 11-11-2014, 01:41 AM

Quote:

Originally Posted by andrixnet

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

andrixnet · 11-12-2014, 02:17 AM

Totally missed that info. Thank you.

OldHolborn · 11-22-2014, 06:22 PM

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

happycamper · 12-23-2014, 10:00 AM

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.