pacman-keyring or what that package is called gets stale really quick over longer periods of time. Large updates are quite smooth in Arch, but IIRC, -Syyu has helped me before.
The extra y just forces a database update. The mechanism to detect when not to update the database is a simple timestamp compare, and shouldn’t break. archlinux-keyring might need a “manual” update if an Arch Linux system is left without updates for a longer period of time. That’s the only situation doing pacman -Sy, then pacman -S archlinux-keyring is recommended, and it needs to be followed with pacman -Syu to avoid a partial upgrade.
Was any of this different in the later 2010s? Thanks for that, but I feel like there was a time when there was a mentioning of a database upgrade in the wiki.
Not everyone uses their computer all the time.
Still no reason … unless the repo is volatile, and potentially you have a corrupt version, a simple -Syu is always enough.
Over a year, many repos become relative volatile.
pacman-keyring or what that package is called gets stale really quick over longer periods of time. Large updates are quite smooth in Arch, but IIRC, -Syyu has helped me before.
The extra
yjust forces a database update. The mechanism to detect when not to update the database is a simple timestamp compare, and shouldn’t break.archlinux-keyringmight need a “manual” update if an Arch Linux system is left without updates for a longer period of time. That’s the only situation doingpacman -Sy, thenpacman -S archlinux-keyringis recommended, and it needs to be followed withpacman -Syuto avoid a partial upgrade.Was any of this different in the later 2010s? Thanks for that, but I feel like there was a time when there was a mentioning of a database upgrade in the wiki.
Maybe I’m confusing it with multilib enabling
Pfft, the losers 😎