slackpkg update fails to verify CHECKSUMS.md5 signature
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am unable to upgrade my system because the CHECKSUMS.md5 file cannot be verified. Also it looks like other files that are supposed to be saved to /tmp by slackpkg are not being saved either.
I've done nothing special to /tmp regarding permissions, or to any other permissions on my system.
I have upgraded my system with the /patches directory off my USB stick, but other parts of the system are still missing.
Quote:
slackpkg - version 2.81.1
What am I doing wrong?
I have also searched the Slack ARM forums, as well as the web looking for a solution, with no resolution.
EDIT:
The following returns nothing
Quote:
gpg --list-keys
I am using the following mirror, and have tried different mirrors with the same result:
I failed to also add during the edit that I am running Slackware arm 14.1. Also, here is the output of an attempt to try and import the gpg key using slackpkg:
You can fully disable gpg check in slackpkg.conf (ie set variable CHECKGPG=off), or temporarily at runtime as below :
Code:
$ slackpkg -checkgpg=off update
Thank you for your response. While this bypasses the problem I've encountered, it does not fix the problem. For now I will bypass GPG signatures, but I hope for some solution to the problem.
Thank you for your response. While this bypasses the problem I've encountered, it does not fix the problem. For now I will bypass GPG signatures, but I hope for some solution to the problem.
Do it manually.
Download the GPG key:
Code:
cd /tmp
wget -q http://arm.slackware.com/pgp-keys/GPG-KEY
openssl sha1 GPG-KEY
SHA1(GPG-KEY)= 3784c2338e7f64eefc4cee6242ed790b87506d1a
Compare that SHA1 sig with the version in the Slackware ARM master tree:
Download the new slackpkg package from the 14.1 patches:
Code:
cd /tmp
wget ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/patches/packages/slackpkg-2.82.0-noarch-12_slack14.1.txz
wget ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/patches/packages/slackpkg-2.82.0-noarch-12_slack14.1.txz.asc
Verify that it's been signed by the correct key:
Code:
# gpg --verify slackpkg-2.82.0-noarch-12_slack14.1.txz.asc slackpkg-2.82.0-noarch-12_slack14.1.txz
gpg: Signature made Mon 16 Jun 2014 08:25:55 PM BST using RSA key ID 1623FC33
gpg: Good signature from "Slackware ARM (Slackware ARM Linux Project) <mozes@slackware.com>"
You should be able to use slackpkg to update to the latest patch packages.
Please also read the change logs since there are often important update information in there, which if not followed exactly, could render your system unusable!
Last edited by drmozes; 07-22-2015 at 02:48 AM.
Reason: Added instructions to import GPG key. Only update slackpkg rather than all packages.
Thanks for the helpful reply. My issue, which as it turns out was not much of an issue, is resolved. For some reason the gpg key you recommended was not the key I was trying to import this morning. I do not remember exactly what I did this morning. I will chalk it up to user error and being a bit sleepy this morning.
Thanks for the helpful reply. My issue, which as it turns out was not much of an issue, is resolved. For some reason the gpg key you recommended was not the key I was trying to import this morning. I do not remember exactly what I did this morning. I will chalk it up to user error and being a bit sleepy this morning.
I apologize for the waste of time.
The issue is that if you install 14.1 and then try to use slackpkg to update it, it will fail because the GPG key was replaced _after_ 14.1 was released. There is a newer slackpkg in /patches which uses the new key, and since Slackware only provides updates in /patches (never in the main tree - apart from in one ARMedslack release where the Kernel had a filesystem corruption issue), you first need to manually update slackpkg from /patches.
I am considering replacing the slackpkg in the 14.1 main tree to avoid these sorts of issues. On the other hand, users really should be reading the Change Log and not blindly updating. If you were to blindly update from 14.1 to -current with one of the supported devices (not the community supported devices such as the RPi), you'd end up with a broken system.
We'll make this thread sticky. That should help in the future.
Also if your time/date is way off it will fail. I see your time stamp on the download:
Quote:
1969-12-31 17:10:42
set the date to the current date or setup time syncing and see if that helps. I had set both my pi's to sync from each other when I intended to sync one from the internet and the other from it and caught it when slackpkg failed.
Thank you for your reply. I have since fixed this after having difficulty using my raspberry pi due to out of date time. My little RPi is now chugging along and hosting all my Slackware mirrors, as well as seeding all Slackware installation disks.
Also if your time/date is way off it will fail. I see your time stamp on the download:
set the date to the current date or setup time syncing and see if that helps. I had set both my pi's to sync from each other when I intended to sync one from the internet and the other from it and caught it when slackpkg failed.
I've patched slackpkg to abort if the date is not current. I'll upload it with the next change batch in a couple of weeks.
I've patched slackpkg to abort if the date is not current. I'll upload it with the next change batch in a couple of weeks.
That would be great since I updated the date several times and it didn't stay updated. It wasn't until after about the third reboot, firmware upgrade, and kernel upgrade using "rpi-update". A warning message will be helpful from slackpkg.
Thank you for your reply. I have since fixed this after having difficulty using my raspberry pi due to out of date time. My little RPi is now chugging along and hosting all my Slackware mirrors, as well as seeding all Slackware installation disks.
Are you running a slackpkg mirror on yours? I started looking into doing that so i could have one server download all the updates then have the rest get updates from the first. Though at the time I had 4 systems the same, now I have 2 32bit and 2 64bit and two different Pi's and the BBB. I want to get the other two 32bit replaced with 64bit and and am thinking of dropping the Pi(1) and BBB for Rp2's to get those the same as well.
I have Slackwarearm-14.1, Slackware64-current and Slackware64-14.1 mirrored on my RPi B+. I am using an 8GB internal SD Card for the (full) installation and a 64GB USB stick to store the mirrors. I use these mirrors for quickly updating and installing virtual machines and my two laptops. I plan on setting up a PXE boot service on the RPi in the future. The mirrors are all http mirrors, hosted with Apache.
When you update each such as the virtual machines. Do they go out to the internet or do they get all the updates from your mirrors?
do you host a torrent of the instal iso's for others to download, are you using a command line BT?
I suppose I'm getting too OT, my mind is still on vacation.
That would be great since I updated the date several times and it didn't stay updated. It wasn't until after about the third reboot, firmware upgrade, and kernel upgrade using "rpi-update". A warning message will be helpful from slackpkg.
Unless your system has an RTC (Raspberry Pi's do not without an add-on), it'll never keep the time after a reboot/power cycle.
When you update each such as the virtual machines. Do they go out to the internet or do they get all the updates from your mirrors?
All the updates are pulled from the mirrors on my raspberry pi. The exception is for multilib stuff that is downloaded from alienbob's multilib repositories.
Quote:
do you host a torrent of the instal iso's for others to download, are you using a command line BT?
I suppose I'm getting too OT, my mind is still on vacation.
I set up rtorrent to download each Slackware ISO and left it seeding after the downloads were finished. It is not a tracker, just a seeder.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
