I have an alias in bashrc called upgrade. It runs reflector looking for the fastest of the newest 10 near me. Then it upgrades the keyring, then yay -syu and then paccache -r.
I have the journal limited to 100mb so I don’t ever bother cleaning house on that.
I probably don’t review pacman logs as often as I should, but stuff rarely breaks and is normally pretty easy for me to figure out what when it does.
So I have a note written down that says “keyring” It’s unclear to me if that’s something I should do regularly, or just if I have a problem. If I’m not mistaken, it is possible for a package to need the updated keyring even if you do pacman -Syu regularly. But I also think it just pitches an error on that package, which will fail to update. Then you can just update the keyring, then rerun pacman -Syu and everything will be fine?
The archlinux-keyring package holds they gpg signatures used for signing the packages and if you go too long between upgrades it’s possible you won’t have a signature or an outdated one and a normal -syu will fail because of it. So I just upgrade keyring first and it gets ahead of that issue.
On hardware that I don't update often, the problem happens to me and this is the route I normally use. What I'm wondering is why the Arch guys don't implement this "automatically"... for example if the keyring is in the packages to be updated, we update it first and then the rest of the packages.
Probably boils down to the arch ethos of K.I.S.S. not making too many decisions for you.
@Shortbus
Yes it is true it may be for this reason.
Although honestly as a "shortcut" it could be convenient for many people who find themselves in a panic when they see this problem for the first time. Furthermore, adopting this behavior does not seem to me to go against the K.I.S.S.
Be that as it may with the K.I.S.S. you learn more than other distros and that's what I like about ArchLinux.