Updates in -current this morning?
 

System: Slackware64-current with slackpkg+

Has anyone else been having problems updating this morning? Every attempt here has failed at the first hurdle (CHECKSUMS.md5.asc). It was working fine yesterday, but none of my machines will upgrade today. Slarm64-current (for RaspberryPi) updated perfectly, so not a network issue.

The error message is that the connection timed out. It doesn't matter if I try my local NAS, the backup USB-HDD or any of the mirrors, both here in the UK or USA, all produce the same error.

I'm assuming its a GPG issue, but I haven't tried turning GPG off, in case it isn't!

The only change I've made is to install a new router - the old one was getting flakey - but I can't see anything in the settings that would cause this.

All suggestions welcome!

--
Pete

pchristy,

It is failing for me also. I have tried several times over a 2 hour time, and I get a time out on Alien Bob repo.
No idea why.

Here is what I see:

I can access without problems. For sum unknown reason I can not get the CHECKSUMS.md5.

Marav: OK, but I can download the updates to my NAS without issue, and all other internet connections seem to be functioning perfectly. Also updating Slarm64 on the Pi worked without issue. Its ONLY Slackware that is giving problems, and it happen regardless of the mirror chosen. The issue only appears when I run slackpkg, and as its borking on the .asc file, I'm assuming its a GPG issue.

I can ping everything I've tried, both on my local net and outside, but I have no idea what to ping for GPG. Route all looks fine too.

Camorri: Thanks for confirming its not just me! Though I am puzzled that (so far) it only seems to be affecting you and me!

:(

--
Pete

Hi pchristy,
I also having the same problem with slackpkg, and it happen with the mirror that i hosted on local network

EDIT: I think the problem is only happen if you are using slackpkg+
because the host slakfinder.org had been down, you can edit the config file and remove that entry for slackpkg+ update.

removing slackpkg+ fixed this for me... regular slackpkg is fine
slackpkg+ is down

nhattu1986: YES! That was the correct answer!

I temporarily disabled the slackpkg+ update, and that allowed the other Slackware packages to update correctly!

Thank you very much!

:)

--
Pete

There's a mirror site for slackpkg+ that may be safer to use: https://slackware.nl/slackpkgplus/ because slakfinder seems to be down on a regular basis.

Has anyone pinged zerouno here? (They're the one in charge of slackpkgplus, right?)

I don't think we have heard anything from zerouno since Sept when we had the grep issue

Hopefully everything is alright with zerouno.

One thing that isn't mirrored is the dev version of slackpkg+, which really speeds up the whole slackpkg experience.

I mirrored the development branch after it was released. I managed to keep up with that version vs the stable branch for my home network.

pkg/slackpkg+-1.9.f-noarch-2mt.txz

Thanks for all the follow up replies! I was going to suggest that we needed a mirror site, and wondered if slackware.uk (popular here in the UK, and a lot of Europe) would host it, but if there's one in the Netherlands, perhaps I'll try that.

Yes, hope zerouno is OK. Is he associated with slackfinder, or just a user?

Cheers,

--
Pete

zerouno is the owner of slakfinder.org

FYI, I emailed Tadgy earlier about adding a mirror on slackware.uk.

edit: Also, for alienbob's mirror, he has the us.slackware.nl mirror which might be faster/closer than the main site.