meanwhile I update NixOS like once a month and it always seems some maintainer has pushed a broken dependency for something and thus borks my entire rebuild. Last month it was some dependency for Krita, This month it’s some dependency for Lutris.
I need to get off NixOS. while it makes doing hard things easy, it’s infuriating when the easy things break and break often. But It’s like some abusive relationship, I want to leave NixOS but i’m so god damn addicted/in love with it and I always end up going back.
I’ve been using arch (Cachyos) for almost a year and the single time I had to roll back was because I didn’t read the notes, just ran the update. Totally my fault. Used the btrfs snapshot roll back and everything was fine.
Additionally, A update can ship a new stock version of a config that has fancy new options and some deleted ones, and your modifications to it in /etc can conflict.
Arch can either backup your version as .pacsave or install the updated file as .pacnew. It’s your task to merge your modifications to the updated configs, and these files can slowly pile-up over time until something breaks.
I’d have 2 snacks, over 10 years…
:( and that was my fault both times because I didn’t read the announcement of required actions before I ran the update
Read the what now?
the announcement of required actions. it’s the update news you get when you update.
The homepage of archlinux.org hosts announcements for required manual interventions
meanwhile I update NixOS like once a month and it always seems some maintainer has pushed a broken dependency for something and thus borks my entire rebuild. Last month it was some dependency for Krita, This month it’s some dependency for Lutris.
I need to get off NixOS. while it makes doing hard things easy, it’s infuriating when the easy things break and break often. But It’s like some abusive relationship, I want to leave NixOS but i’m so god damn addicted/in love with it and I always end up going back.
I’ve been using arch (Cachyos) for almost a year and the single time I had to roll back was because I didn’t read the notes, just ran the update. Totally my fault. Used the btrfs snapshot roll back and everything was fine.
Additionally, A update can ship a new stock version of a config that has fancy new options and some deleted ones, and your modifications to it in
/etccan conflict.Arch can either backup your version as
.pacsaveor install the updated file as.pacnew. It’s your task to merge your modifications to the updated configs, and these files can slowly pile-up over time until something breaks.