Timeline
Post
Remote status
Context
8
@lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip Just because Arch is terrible doesn't mean this applies to every other distro though.
@SuperDicq@minidisc.tokyo @lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip it does not have to do anything with arch itself. This can happen with every distro, if GRUB gets an update but fails or if the initcpio-Image was not build successfully.
The best way to avoid those issues is, by reading through the output of your package manager and ensuring that the installation of GRUB and the Initcpio process were successful.
@kitsune_yasu@waldbewohner.eu @lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip
This can happen with every distro, if GRUB gets an update but fails or if the initcpio-Image was not build successfully.I'm not that familiar with Arch, but it sounds extremely incompetent to me that Pacman would just continue updating and not fail if grub-install fails.
Debian, for example, has a transaction based package manager so that makes sure when failures like this happen the old stuff that was previously working is not overwritten. So that definitely sounds like a design flaw in Pacman.
@SuperDicq @lanodan @kitsune_yasu @volpeon pacman never does anything with a bootloader. There are two (three) main failure modes that pacman has:
- distro keyring not up to date, failing package authenticity check (archlinux-keyring needs to be updated first)
- pacman deletes initrds on transaction start meaning that if your system fails in the middle of an update, you not only have a system in an unknown state with half-extracted packages, but also no kernel to boot
- when using BTRFS, the free space check can fail because free space as reported by BTRFS isn't actually real and it doesn't use the specific btrfs library for getting free space
- distro keyring not up to date, failing package authenticity check (archlinux-keyring needs to be updated first)
- pacman deletes initrds on transaction start meaning that if your system fails in the middle of an update, you not only have a system in an unknown state with half-extracted packages, but also no kernel to boot
- when using BTRFS, the free space check can fail because free space as reported by BTRFS isn't actually real and it doesn't use the specific btrfs library for getting free space
@phnt@fluffytail.org @SuperDicq@minidisc.tokyo @lanodan@queer.hacktivis.me @kitsune_yasu@waldbewohner.eu @volpeon@icy.wyvern.rip
- distro keyring not update to date failing package authenticity check (archlinux-keyring needs to be updated first)Wait, that's not supposed to happen?
@lolitechengineer @phnt @SuperDicq It's not, other distros just have keyring put into a package, so it gets updated normally.
I got that one in my containers and well… tossed Arch out definitively because there's a point where it's just pure incompetence.
I got that one in my containers and well… tossed Arch out definitively because there's a point where it's just pure incompetence.
@lanodan @lolitechengineer @SuperDicq It is packaged and it gets updated when you update the system, but when you don't update for a long time, new packages can be signed with keys that aren't in your old system keyring and there's no automatic pre-upgrade step for updating that keyring. Hence why the manual update is necessary.
Gentoo solved this issue by force-updating the wkd on every update before emerge even resolves dependencies.
Gentoo solved this issue by force-updating the wkd on every update before emerge even resolves dependencies.
𝖙𝖗𝖚𝖘𝖙𝖊𝖉 
𝓉𝒽𝒾𝓈 
𝓴𝓮𝔂 
Replies
0
No replies yet.