Can’t pacman -Syu my 32 box because one of the keys used to sign better than a dozen of the packages I need to upgrade expired today

I mean, yeah, I could just turn off signature verification, but the fact that that’s my choice is frustrating to say the least


I hate to say it, but the whole project seems a bit amateurish compared to what I’m used to from upstream

It’s not just this either, packages with broken dependencies are regularly pushed to production

Kind of tempted to switch this box over to just for the first-class i686 support

FWIW, finally got a response on the 32 IRC channel

pacman-key --refresh will download an updated key from a public keyserver

The right answer is to get the updated key into the official archlinux32-keyring package, but this stopgap works until that happens

@djmoch Have you ever considered #Slackware? If you use #Slackbuilds and #sbotool you can run a reasonably current system without as much jankiness.

@starbreaker I have some friends who use Slackware, but I've never much considered it, no. Reason being I actually thought it tended to run pretty far behind (a la Debian). Is that not the case?

@djmoch I don't think that's accurate. The current release (14.2) might still use a 4.19 kernel, but it's patched like crazy. Userland software is also generally up to date, as are #Slackbuilds. You can use Slackware Current if still want rolling releases, too, but I stick with 14.2 on machines that don't work well with #OpenBSD for whatever reason (like Nvidia graphics).

Sign in to participate in the conversation

A private Mastodon instance