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.)

[–] hperrin@lemmy.ca 22 points 1 week ago (5 children)

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.

[–] Grail@multiverse.soulism.net 16 points 1 week ago (1 children)

Arch isn't for normal people.

[–] texture@lemmy.world 4 points 1 week ago

we dont talk about normies here

[–] Shayeta@feddit.org 13 points 1 week ago

You're not the first to be annoyed by that: https://github.com/bradford-smith94/informant

[–] Giloron@programming.dev 7 points 1 week ago

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.

[–] esc@piefed.social 7 points 1 week ago

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.

[–] Speiser0@feddit.org 3 points 1 week ago* (last edited 1 week ago)

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.

[–] stupidcasey@lemmy.world 1 points 1 week ago (1 children)

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.

[–] xthexder@l.sw0.com 9 points 1 week ago

99% of the time it is just automatic and part of the update. Usually it's only an issue if you are updating from a specific older version of something or have made a particular customization that breaks with the update.

Like others, I've got at least one system running Arch for 10+ years and I've only had to manually do something a handful of times. Usually it's just that I have to update the keyring first before the rest of the update.

[–] Luminous5481@anarchist.nexus 5 points 1 week ago

the announcement of required actions. it's the update news you get when you update.

[–] floquant@lemmy.dbzer0.com 5 points 1 week ago

The homepage of archlinux.org hosts announcements for required manual interventions

[–] rozodru@piefed.world 13 points 1 week ago

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.

[–] determinist@kbin.earth 8 points 1 week ago

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.

[–] JATothrim_v2@programming.dev 1 points 1 week ago

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.