Arch has a news feed where it describes things that require manual intervention when upgrading: https://archlinux.org/
(You are informed at arch install that you have to read it before upgrading.)
What an awesome and amazing and definitely not annoying system. Automating that to show you only what you need based on the packages you have installed when you do the update would be so ridiculous. I’m glad it’s just a blog.
Notes with recommended user actions are provided per package after every update. Mostly to let you know about optional packages and tell you how to enable optional auto start for some things.
For things that need even more attention, there is a system that tracks read/unread news that also only show up when your system needs it.
There are messages with generic recommendations and post upgrade/post install scripts. They are rarely used because it goes against arch’s principles to run some (maybe fragile) script on your system. Reading news once a week/month before upgrade isn’t that inconvenient.
It’s actually helpful that it’s not filtered, because otherwise, I would only see a new post maybe once every 2 years, and would therefore not know if it still works, and feel lonely.
I get the building the system from scratch is good for learning the system and I’ve done it myself but this just feels like bad development, why not make it a simple script that you can choose to run or you know just make it part of the update itself like literally everyone else in the world.
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?
Arch has a news feed where it describes things that require manual intervention when upgrading: https://archlinux.org/ (You are informed at arch install that you have to read it before upgrading.)
What an awesome and amazing and definitely not annoying system. Automating that to show you only what you need based on the packages you have installed when you do the update would be so ridiculous. I’m glad it’s just a blog.
You’re not the first to be annoyed by that: https://github.com/bradford-smith94/informant
Welcome to Gentoo.
Notes with recommended user actions are provided per package after every update. Mostly to let you know about optional packages and tell you how to enable optional auto start for some things.
For things that need even more attention, there is a system that tracks read/unread news that also only show up when your system needs it.
There are messages with generic recommendations and post upgrade/post install scripts. They are rarely used because it goes against arch’s principles to run some (maybe fragile) script on your system. Reading news once a week/month before upgrade isn’t that inconvenient.
It’s actually helpful that it’s not filtered, because otherwise, I would only see a new post maybe once every 2 years, and would therefore not know if it still works, and feel lonely.
I get the building the system from scratch is good for learning the system and I’ve done it myself but this just feels like bad development, why not make it a simple script that you can choose to run or you know just make it part of the update itself like literally everyone else in the world.
The homepage of archlinux.org hosts announcements for required manual interventions
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.