Update slarm64 md5/gpg issues?
 

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).

--
Pete

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.

I'm seeing the same issues with these packages using dl.slarm64.org:

FYI: The squeakycode.net mirror (in the US) hasn't been updated since Oct 2020. :(

Yes, that's pretty much what I'm getting too!

I had a look at all the gpg packages installed and found gpgme and libassuan were missing. I've installed those, but no change. I've tried:

http://slackware.uk/slarm64/slarm64-current/
https://slackware.uk/slarm64/slarm64-current/
ftp://slackware.uk/slarm64/slarm64-current/
and finally: http://dl.slarm64.org/slarm64/slarm64-current/

all with the same result.

Procedure:

slackpkg update gpg
slackpkg update (and answer "yes")
slackpkg install-new (nothing new to install)
slackpkg upgrade-all

Note: When downloading the packages, it seems to do so multiple times. It also seems to try and install them multiple times (see above list).

Yes, only one mirror is selected.

On the first run, about half of the packages updated successfully. The remainder threw up the errors seen above, and continue to do so.

I have run out of ideas!

--
Pete

thanks everyone, updated md5, gpg.

YES! That's fixed it!

Many thanks!

--
Pete

Problem is back again! Unable to update via slackpkg due to md5sum errors ...

--
Pete

this is because of glibc, update glibc first.

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).

--
Pete

check manually what gives:

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?

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!

--
Pete

download files aaa_base-14.2-aarch64-7.txz aaa_base-14.2-aarch64-7.txz.asc GPG-KEY

and then check

As user:
as root:
--
Pete

with this order, now

OK, that will take a while! To try and speed things up I've just done:
which was previously failing with md5sum error.

This time it has downloaded and installed correctly, so hopefully problem solved!

It is going to take quite a long time to do the full upgrade. I'll let you know how it goes in an hour or two's time! ;)

At the moment, it looks promising!

Many thanks!

--
Pete

Good.
I have updated my systems myself the problem is just glibc and then checking gpg. an initial manual update to glibc solved this problem.

The upgrade seems to have finally gone through OK, though my estimate of a couple of hours was some way off! It finally finished around 2100 (started at 1630!). I think it would have been quicker to re-install from scratch!

Funny thing is that I had previously upgraded glibc (at your suggestion), updated gpg and slackpkg and it still didn't work. This last time it did! One of life's mysteries, I guess!

Anyway, all sorted now! Many thanks for your help!

--
Pete