4 ms·
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-keycha
by akimbostrawman 1y ago
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#Upgrade_system_regularly https://wiki.archlinux.org/title/Pacman/Package_signing#Upgr...
- dijit 1y agoListen, dude, this isn’t litigation. 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.
- akimbostrawman 1y agoI disagree that having to update a package which is also now a automatic service qualifies as broken. Sure there are issues but they are usually either self induced e.g. AUR, easily fixable e.g. keyring update or broadcasted publicly with a fix e.g. archnews. At the end of the day arch is firmly a do it yourself distro where some user intervention is expected.
- dijit 1y agoRight so, > I've also been using Linux for years (Arch, btw) and never had an update break my install or cause issues Is an anecdote that is worthy of being attacked with my own, given the context that people might come away thinking that Arch updates do not break their system.. right?
- akimbostrawman 1y agoRight, just make sure that anecdote actually applies.