hey hypothetically if I had an arch linux install that hadn't been updated in like a year and a half, how badly would it break if I did a quick pacman -Syu? Asking for a friend. #linux #archlinux

@HeyCallMeRed That would be 'interesting' for sure, although nobody will be able to predict the outcome, not knowing what you do on the system.

But SURELY you have a working backup, just in case, right???

@phoenixgee Backups are for cowards.
@HeyCallMeRed hmm, hm, hmm that would be very interesting to know.
@HeyCallMeRed eep. Definitely worth browsing through all the "blah requires manual intervention" posts on https://archlinux.org/ from the past 18 months when (or before) trying to do this...
Arch Linux

@ds yeah, that's the plan. Although the temptation to just go for it is there. l'appel du vide, and all that.
@HeyCallMeRed I've not tried this before but it could also be an option to use https://archive.archlinux.org/ to do a few smaller steps rather than one huge leap?
Index of /

@HeyCallMeRed I recently updated a friend's PC running EndeavourOS - the last update was 8 months ago - apart from a few missing mirror servers, it ran smoothly.

@HeyCallMeRed
Hypothetically speaking,

First check archlinix.org, than do upgrade.

Btw i think this here is the only thing where you needed to do something.

https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requires-manual-intervention/

Arch Linux - News: linux-firmware >= 20250613.12fe085f-5 upgrade requires manual intervention

@HeyCallMeRed It might give you signing errors, fail fast and not upgrade at all, the command here should prevent that https://wiki.archlinux.org/title/Pacman/Package_signing#Upgrade_system_regularly

Also https://wiki.archlinux.org/title/System_maintenance#Upgrading_the_system lists the usual advice: read the news, look out for changed configuration files, allocate some time do to the upgrade so you have time to fix it if anything breaks, and restart.

pacman/Package signing - ArchWiki

@HeyCallMeRed the update will prolly fail coz of some pkgs' signature not being verified, which comes from your pacman keyring having become stale. so, after a long time away, run your update thus:

sudo pacman --needed --noconfirm -S archlinux-keyring && sudo pacman -Syu

if that still doesn't work, there is a "nuclear" option, but hopefully you won't need it

edit: oh yeah, as a wise peep above said, also first review & action any relevant issues since last update in https://archlinux.org/news/

#Arch #ArchLinux #pacman #linuxwomen

Arch Linux - News

@HeyCallMeRed given the kernel update probably high but probably would have happened anyway.