Been using it for 5+ years, not the best internet so it has happened to me a few times typically a minor annoyance like the other user said. What were the exact steps again? Makes the updating process even more tedious.
It’s worse when you’ve got to do manual intervention and that’s why I’m not updating now, legacy nvidia driver moved to the AUR (which I didn’t always update). If I could get a cheap AMD card it really would help here, especially as legacy and proprietary are also potential issues with installing a new distro too.
My system is mostly usable now despite being pretty out-of-date by Arch standards, I probably need to move to something else but being outdated (and not prepared) means I can’t just spin up a VM to try stuff out either.
Mostly nothing, but I did have issues once where a package changed but couldn’t be installed due to failing verification as the keyring wasn’t updated. That killed the desktop environment on boot but dropping into the console and updating the keyring specifically before trying the full update again fixed things.
After a while, but probably more than a month, you would need to refresh your keys as the ones that your system trusts would not match the signatures on what is being downloaded from the repo and you would be getting signature errors.
You’d just install archlinux-keyring first, and then do a full system upgrade. If that didn’t work you could refresh the keys with pacman-key (pacman-key --refresh-keys) and then install archlinux-keyring->upgrade.
Your system would work fine without updating, though I guess eventually a new version of HTML will come out in a decade or so and your browser won’t support it… but until then you’d be fine(security issues aside).
Arch is trash.
Arch is nice… but i would love someone to tell me what happens if i stop updating for a month or something of the like
Been using it for 5+ years, not the best internet so it has happened to me a few times typically a minor annoyance like the other user said. What were the exact steps again? Makes the updating process even more tedious.
It’s worse when you’ve got to do manual intervention and that’s why I’m not updating now, legacy nvidia driver moved to the AUR (which I didn’t always update). If I could get a cheap AMD card it really would help here, especially as legacy and proprietary are also potential issues with installing a new distro too.
My system is mostly usable now despite being pretty out-of-date by Arch standards, I probably need to move to something else but being outdated (and not prepared) means I can’t just spin up a VM to try stuff out either.
Mostly nothing, but I did have issues once where a package changed but couldn’t be installed due to failing verification as the keyring wasn’t updated. That killed the desktop environment on boot but dropping into the console and updating the keyring specifically before trying the full update again fixed things.
By now there’s an always-enabled service running that updates the keys from time to time. So this wine happen anymore on servers.
After a while, but probably more than a month, you would need to refresh your keys as the ones that your system trusts would not match the signatures on what is being downloaded from the repo and you would be getting signature errors.
You’d just install archlinux-keyring first, and then do a full system upgrade. If that didn’t work you could refresh the keys with pacman-key (pacman-key --refresh-keys) and then install archlinux-keyring->upgrade.
Your system would work fine without updating, though I guess eventually a new version of HTML will come out in a decade or so and your browser won’t support it… but until then you’d be fine(security issues aside).
so brave