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.
Lately, on my Rock-Pi 4 with slarm64, when launching
Code:
# slackpkg update && slackpkg upgrade-all
I get this error message:
Code:
[...]
Downloading http://dl.slarm64.org/slarm64/slarm64-current/testing/MANIFEST.bz2...
--2021-10-04 19:49:36-- http://dl.slarm64.org/slarm64/slarm64-current/testing/MANIFEST.bz2
Resolving dl.slarm64.org (dl.slarm64.org)... 193.151.15.132
Connecting to dl.slarm64.org (dl.slarm64.org)|193.151.15.132|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14 [application/x-bzip2]
Saving to: ‘/tmp/slackpkg.mJ4R82/testing-MANIFEST.bz2’
/tmp/slackpkg.mJ4R82/testi 100%[=====================================>] 14 --.-KB/s in 0s
2021-10-04 19:49:36 (483 KB/s) - ‘/tmp/slackpkg.mJ4R82/testing-MANIFEST.bz2’ saved [14/14]
Checksums
Downloading http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5...
--2021-10-04 19:49:36-- http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5
Resolving dl.slarm64.org (dl.slarm64.org)... 193.151.15.132
Connecting to dl.slarm64.org (dl.slarm64.org)|193.151.15.132|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 341770 (334K)
Saving to: ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5’
/tmp/slackpkg.mJ4R82/CHECK 100%[=====================================>] 333.76K 1.20MB/s in 0.3s
2021-10-04 19:49:36 (1.20 MB/s) - ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5’ saved [341770/341770]
Downloading http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5.asc...
--2021-10-04 19:49:36-- http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5.asc
Resolving dl.slarm64.org (dl.slarm64.org)... 193.151.15.132
Connecting to dl.slarm64.org (dl.slarm64.org)|193.151.15.132|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 691 [application/pgp-signature]
Saving to: ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5.asc’
/tmp/slackpkg.mJ4R82/CHECK 100%[=====================================>] 691 --.-KB/s in 0s
2021-10-04 19:49:36 (19.3 MB/s) - ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5.asc’ saved [691/691]
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. If you use mirrors.slackware.com
as your mirror, this could also mean that the mirror to
which you got redirected is not yet updated with the most
recent changes in the Slackware tree.
You need the GPG key of slarm64 AArch64 <security@slarm64.org>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
After
Code:
# slackpkg update gpg
Getting key from https://www.slackware.com/infra/keys/arm/GPG-KEY
Slackware Linux Project's GPG key added
doing
Code:
# slackpkg update && slackpkg upgrade-all
still fails.
Changing the mirror doesn't help either.
For updating my system I need to disable CHECKGPG in /etc/slackpkg/slackpkg.conf, but that's not recommended.
Any ideas how I can get rid of this error without disabling CHECKGPG?
On my system it still fails, also with the slackware.uk mirror:
Code:
# slackpkg update && slackpkg upgrade-all
[...]
Downloading http://slackware.uk/slarm64/slarm64-current/CHECKSUMS.md5.asc...
--2021-10-05 07:56:56-- http://slackware.uk/slarm64/slarm64-current/CHECKSUMS.md5.asc
Resolving slackware.uk (slackware.uk)... 2a02:2498:e004:2a::a861, 216.119.155.61
Connecting to slackware.uk (slackware.uk)|2a02:2498:e004:2a::a861|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 691 [application/pgp-signature]
Saving to: ‘/tmp/slackpkg.LWPBma/CHECKSUMS.md5.asc’
/tmp/slackpkg.LWPBma/CHECK 100%[=====================================>] 691 --.-KB/s in 0s
2021-10-05 07:56:56 (23.8 MB/s) - ‘/tmp/slackpkg.LWPBma/CHECKSUMS.md5.asc’ saved [691/691]
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. If you use mirrors.slackware.com
as your mirror, this could also mean that the mirror to
which you got redirected is not yet updated with the most
recent changes in the Slackware tree.
You need the GPG key of slarm64 AArch64 <security@slarm64.org>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
I'm out of ideas then! Mine updated OK late last night, and no changes this morning, so I can't re-try.
I do keep a local copy of both Slackware64-current and slarm64-current on a local NAS here - not really necessary for slarm64, but I have 3 or 4 machines running slackware and this saves on bandwidth! I rsync to slackwareUK daily and then update from there. GPG is still checked, though.
Might be worth trying rsyncing a local drive and then updating from there?
Otherwise you might have to wait and see if anyone else is having problems. Not sure what else to suggest.
I also have a local host system syncing a mirror locally, that's being updated daily, but setting the path as mirror to /etc/slackpkg/mirrors doesn't solve that issue:
Code:
# slackpkg update gpg && slackpkg update && slackpkg upgrade-all
Getting key from https://www.slackware.com/infra/keys/arm/GPG-KEY
Slackware Linux Project's GPG key added
Getting key from https://www.slackware.com/infra/keys/arm/GPG-KEY
Slackware Linux Project's GPG key added
Updating the package lists...
Downloading...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/CHECKSUMS.md5.asc...
Files //var/lib/slackpkg/CHECKSUMS.md5.asc and /tmp/slackpkg.guujH6/CHECKSUMS.md5.asc differ
Downloading...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/ChangeLog.txt...
List of all files
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/patches/MANIFEST.bz2...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/slarm64/MANIFEST.bz2...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/extra/MANIFEST.bz2...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/pasture/MANIFEST.bz2...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/testing/MANIFEST.bz2...
Checksums
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/CHECKSUMS.md5...
Linking /sshfs/rps/Mirror/Slackware/slarm64-current/CHECKSUMS.md5.asc...
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. If you use mirrors.slackware.com
as your mirror, this could also mean that the mirror to
which you got redirected is not yet updated with the most
recent changes in the Slackware tree.
You need the GPG key of slarm64 AArch64 <security@slarm64.org>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
Lately, on my Rock-Pi 4 with slarm64, when launching
Code:
# slackpkg update && slackpkg upgrade-all
I get this error message:
Code:
[...]
Downloading http://dl.slarm64.org/slarm64/slarm64-current/testing/MANIFEST.bz2...
--2021-10-04 19:49:36-- http://dl.slarm64.org/slarm64/slarm64-current/testing/MANIFEST.bz2
Resolving dl.slarm64.org (dl.slarm64.org)... 193.151.15.132
Connecting to dl.slarm64.org (dl.slarm64.org)|193.151.15.132|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14 [application/x-bzip2]
Saving to: ‘/tmp/slackpkg.mJ4R82/testing-MANIFEST.bz2’
/tmp/slackpkg.mJ4R82/testi 100%[=====================================>] 14 --.-KB/s in 0s
2021-10-04 19:49:36 (483 KB/s) - ‘/tmp/slackpkg.mJ4R82/testing-MANIFEST.bz2’ saved [14/14]
Checksums
Downloading http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5...
--2021-10-04 19:49:36-- http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5
Resolving dl.slarm64.org (dl.slarm64.org)... 193.151.15.132
Connecting to dl.slarm64.org (dl.slarm64.org)|193.151.15.132|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 341770 (334K)
Saving to: ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5’
/tmp/slackpkg.mJ4R82/CHECK 100%[=====================================>] 333.76K 1.20MB/s in 0.3s
2021-10-04 19:49:36 (1.20 MB/s) - ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5’ saved [341770/341770]
Downloading http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5.asc...
--2021-10-04 19:49:36-- http://dl.slarm64.org/slarm64/slarm64-current/CHECKSUMS.md5.asc
Resolving dl.slarm64.org (dl.slarm64.org)... 193.151.15.132
Connecting to dl.slarm64.org (dl.slarm64.org)|193.151.15.132|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 691 [application/pgp-signature]
Saving to: ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5.asc’
/tmp/slackpkg.mJ4R82/CHECK 100%[=====================================>] 691 --.-KB/s in 0s
2021-10-04 19:49:36 (19.3 MB/s) - ‘/tmp/slackpkg.mJ4R82/CHECKSUMS.md5.asc’ saved [691/691]
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. If you use mirrors.slackware.com
as your mirror, this could also mean that the mirror to
which you got redirected is not yet updated with the most
recent changes in the Slackware tree.
You need the GPG key of slarm64 AArch64 <security@slarm64.org>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
After
Code:
# slackpkg update gpg
Getting key from https://www.slackware.com/infra/keys/arm/GPG-KEY
Slackware Linux Project's GPG key added
doing
Code:
# slackpkg update && slackpkg upgrade-all
still fails.
Changing the mirror doesn't help either.
For updating my system I need to disable CHECKGPG in /etc/slackpkg/slackpkg.conf, but that's not recommended.
Any ideas how I can get rid of this error without disabling CHECKGPG?
check which keys are installed
Code:
sudo gpg --list-keys
Quote:
pub 2048R/C5DB61BC 2015-04-21
uid Your Name (Optional Comment)
sub 2048R/18C601D3 2015-04-21
remove all mentions slarm64 AArch64 <security[a]slarm64.org>
@sndwvs:
According to your advice, I deleted the slarm64 related gpg key, but I also had a gpg key of "Slackware ARM", which I also deleted. Then I ran "slackpkg update gpg", which added the key of "Slackware ARM", but a "slackpkg upgrade-all" says "You need the GPG key of slarm64 AArch64".
Here are the steps:
Code:
# gpg --list-keys
/root/.gnupg/pubring.gpg
------------------------
pub 1024D/9C7BA3B6 2007-01-27
uid SlackBuilds.org Development Team <slackbuilds-devel[at]slackbuilds.org>
sub 2048g/C575D49B 2007-01-27
Code:
# slackpkg update
[...]
Downloading http://slackware.uk/slarm64/slarm64-current/CHECKSUMS.md5.asc...
--2021-10-05 21:23:36-- http://slackware.uk/slarm64/slarm64-current/CHECKSUMS.md5.asc
Resolving slackware.uk (slackware.uk)... 2a02:2498:e004:2a::a861, 216.119.155.61
Connecting to slackware.uk (slackware.uk)|2a02:2498:e004:2a::a861|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 691 [application/pgp-signature]
Saving to: ‘/tmp/slackpkg.utnCiQ/CHECKSUMS.md5.asc’
/tmp/slackpkg.utnCiQ/CHECK 100%[=====================================>] 691 --.-KB/s in 0s
2021-10-05 21:23:36 (11.4 MB/s) - ‘/tmp/slackpkg.utnCiQ/CHECKSUMS.md5.asc’ saved [691/691]
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. If you use mirrors.slackware.com
as your mirror, this could also mean that the mirror to
which you got redirected is not yet updated with the most
recent changes in the Slackware tree.
Code:
# gpg --list-keys
/root/.gnupg/pubring.gpg
------------------------
pub 1024D/9C7BA3B6 2007-01-27
uid SlackBuilds.org Development Team <slackbuilds-devel[at]slackbuilds.org>
sub 2048g/C575D49B 2007-01-27
pub 2048R/1623FC33 2014-06-16
uid Slackware ARM (Slackware ARM Linux Project) <mozes[at]slackware.com>
sub 2048R/5EA4DF60 2014-06-16
Code:
# slackpkg upgrade-all
You need the GPG key of slarm64 AArch64 <security[at]slarm64.org>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
Whatever the issue is, it is something unique to your machine. Just updated slarm64-current here using slackpkg-15.0.7 with no issues.
All I can think of is to go through all the configuration files very carefully, and make sure everything is as it should be (only one mirror selected, etc).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.