I’ve had the opposite experience. Updating my apt sources.list and running dist-upgrade always worked for me on Debian (though most of the time I just run unstable which is rolling) but on Arch it seems like if I don’t upgrade regularly sometimes I’ll get hit with signature key errors because the key database is outdated and then have to go run some other command to update the keys before a pacman -Syu will work. I love both distros, but there’s no better way to make your users not give a shit about security than making said security interrupt their workflow. Most of the time I just disable the key check in pacman.conf so that the damn thing will upgrade successfully.
I’ve had the opposite experience. Updating my apt sources.list and running dist-upgrade always worked for me on Debian (though most of the time I just run unstable which is rolling) but on Arch it seems like if I don’t upgrade regularly sometimes I’ll get hit with signature key errors because the key database is outdated and then have to go run some other command to update the keys before a pacman -Syu will work. I love both distros, but there’s no better way to make your users not give a shit about security than making said security interrupt their workflow. Most of the time I just disable the key check in pacman.conf so that the damn thing will upgrade successfully.