Earlier quoted context omitted.
I would say it's fair, but then it leads to an interesting problem that could happen. Build a tiny core, ask the community to extend: never be liable for any issue because important packages that are essentially required aren't part of the core and thus any criticism is invalid. Not saying that's happening here, but it could happen by this definition. But, ok, there are more issues anyway, for example it's pretty com…
Arch isn't liable regardless. It's a community driven project run by volunteers without contracts. >it's pretty common that you have to update archlinux-keychain before an upgrade can succeed because the signing keys "Since 2022-07-29, the archlinux-keyring-wkd-sync.service and the associated systemd timer have been created and enabled by default" https://wiki.archlinux.org/title/Pacman/Package_signing#Upgr...
The shit is broken sometimes, it’s ok, but we are here to be intellectually curious and have a discussion.
Lying to people about how broken it can be to update in reality is the opposite of that.
We aren’t here to pull down arch or the community; just here to spit facts.