im about to update 1956 arch packages at the same time. is my computer going to survive or will i be left with a totally broken system. vote now
Conversation
Notices
-
not good psdev 🏳️⚧️ (mothcompute@vixen.zone)'s status on Friday, 03-Jan-2025 18:41:16 JST not good psdev 🏳️⚧️ - polprog68k likes this.
-
polprog68k (gorplop@pleroma.m68k.church)'s status on Friday, 03-Jan-2025 18:41:36 JST polprog68k @mothcompute
grub> _ -
not good psdev 🏳️⚧️ (mothcompute@vixen.zone)'s status on Friday, 03-Jan-2025 18:55:26 JST not good psdev 🏳️⚧️ @gorplop you joke but i dug one of my older computers out of storage a few days ago and it booted to exactly that
polprog68k likes this. -
polprog68k (gorplop@pleroma.m68k.church)'s status on Friday, 03-Jan-2025 18:56:29 JST polprog68k @mothcompute on a serious note I once left an arch laptop not updated for a few months and all pacman keys expired screwing up the entire system on update >_> -
Gyroplast (gyroplast@furry.engineer)'s status on Saturday, 04-Jan-2025 06:54:31 JST Gyroplast Force-installing a current archlinux-keyring package adds missing and removes expired keys. If you're really desperate, you can download and extract the package manually right into your root, and run pacman-key -u afterwards to update the trustdb.
I made it a habit long ago to explicitly update only this package before a -Syu, but haven't seen it necessary with the new-ish archlinux-keyring-wkd-sync running these days. Would still do that on month- or year-old systems, though, it doesn't hurt. The issue is typically not keys expiring, but new keys being added, as new devs/TUs begin signing core/extra packages.
AUR is your real issue most of the time, in particular your AUR helper that needs to catch up with alpm. If your system critically relies on AUR packages.. well.. not a world I'd want to live in, but remember recompiling those. :)
polprog68k likes this.