nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqufmlneg8tt9jwvk6p40t02lxhmkns6zlpu4cwrvxerczdnn4syzq4pd73q (nprofile…d73q) Haelwenn /элвэн/ :triskell: (nprofile…8m52) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqqdektuf27qpdltrrcwmywcduzu5q2rrunkcsahp7mhznuqlgjhjqdvlu27 (nprofile…lu27) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqhcrul0etnreherhra9vkg220qtjjw72dvezr8rceucj6jmapufxqr0pzxv (nprofile…pzxv) 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