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.
Is anyone else having problems installing the latest (27 Jan) updates of slarm64?
About half the packages fail to install with md5sum errors. I've tried the uk.slackware repository, the dl. repository and my own local one. If I turn off md5 checking, the same packages fail with gpg errors (yes, I did update gpg after switching mirrors).
on the night of the 27th all packages were updated after rebuilding and gpg signing of files, today I updated from dl.slarm64.org there were no such messages. please try again.
OK, upgraded to glibc-2.33 (and glibc-i18n) using upgradepkg, then re-ran slackpkg update gpg, slackpkg update and finally slackpkg upgrade-all. Still just get md5sum errors on all packages - at least I assume so! I stopped after two screenfulls!
Also tried upgrading slackpkg on its own, and got md5sum error. Maybe I should have used upgradepkg for slackpkg first? Will give that a try later this afternoon (have to go out for an hour, now).
Doesn't the filename have to have the path inluded? ie: /path/to/aaa_base... and that GPG-KEY seems to be a link, so again, I assume I need the full path?
Code:
gpg --verify http://dl.slarm64.org/slackware/slarm64-current/slarm64/a/aaa_base-14.2-aarch64-7.txz.asc http://dl.slarm64.org/slackware/slarm64-current/GPG-KEY
gpg: can't open `http://dl.slarm64.org/slackware/slarm64-current/slarm64/a/aaa_base-14.2-aarch64-7.txz.asc'
gpg: verify signatures failed: file open error
Code:
gpg --verify http://slackware.uk/slarm64/slarm64-current/slarm64/a/aaa_base-14.2-aarch64-7.txz.asc http://slackware.uk/slarm64/slarm64-current/GPG-KEY
gpg: can't open `http://slackware.uk/slarm64/slarm64-current/slarm64/a/aaa_base-14.2-aarch64-7.txz.asc'
gpg: verify signatures failed: file open error
I don't use gpg much - normally rely on slackpkg to take care of it for me, so apologies for any errors on my part!
gpg --verify aaa_base-14.2-aarch64-7.txz.asc GPG-KEY
gpg: Signature made Sun 21 Feb 2021 02:52:11 AM GMT using RSA key ID 4690E354
gpg: Can't check signature: public key not found
as root:
Code:
gpg --verify aaa_base-14.2-aarch64-7.txz.asc GPG-KEY
gpg: Signature made Sun 21 Feb 2021 02:52:11 AM GMT using RSA key ID 4690E354
gpg: BAD signature from "slarm64 AArch64 <security@slarm64.org>"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
