Sure the Arch or package maintainers could provide migration scripts for stuff like that (there probably are rolling distros who do that?) or when they split packages but usually you are fine if you read the announcements and act accordingly.
Sorry that wasn’t meant like that, I was just pointing out that that was at least communicated in Archnews which not everything is, for example the firewalld package split you have to catch in the package update warnings which is easy to miss.
Yeah there’s a lot of things you can do, but I bet most people just hit yes and go about their day, which is how they break their system. I’ve done it at least once (come back from vacation and pacman hits you with 300+ new packages), but also have broken arch by trying to install stuff by following old deprecated guides. It’s not hard to break, but it’s also very achievable to have a problem free time.
Jup. I think I’ve had some 3 actual issues the past 2 years on EndeavourOS. But the Endeavour team did a good job of warning me on Discord/RSS or at least provide tutorials and explanations afterwards.
One of the issues was in regard to Grub (fixed by Timeshift rollback and a one-liner), one was in regard to some rogue Nvidia bug crashing the login window (fixed by Timeshift rollback and waiting a few days before updating again), and one was Nvidia removing support for GTX1000 cards and older (Nvidia, WHYYYYYYYY?!).
For reference, I had what felt like similar annoying bugs (and much worse) on Windows 10 about every month, but without any useful support from Microsoft. :(
and one was Nvidia removing support for GTX1000 cards and older (Nvidia, WHYYYYYYYY?!).
Yeah this one REALLY sucked on my laptop still running a 960M. But hey, after the fix (which I think was just locking the driver package?) I just don’t gotta worry anymore, so that’s cool.
One day I will figure out what other Arch users do and why my installation had not a single issue in the 3 years it has been running so far.
I don’t get new issues all the time like op says, but I do have a few nagging issues that I’m too lazy to fix.
Usually it’s graphics drivers going boom on update.
Yeah but that was communicated in Archnews: https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-kernel-modules/
Sure the Arch or package maintainers could provide migration scripts for stuff like that (there probably are rolling distros who do that?) or when they split packages but usually you are fine if you read the announcements and act accordingly.
The question was how they make the arch go boom by running pacman -Syyu and I gave the most probable reason. Thanks for hitting me with RTFM
Sorry that wasn’t meant like that, I was just pointing out that that was at least communicated in Archnews which not everything is, for example the firewalld package split you have to catch in the package update warnings which is easy to miss.
Yeah there’s a lot of things you can do, but I bet most people just hit yes and go about their day, which is how they break their system. I’ve done it at least once (come back from vacation and pacman hits you with 300+ new packages), but also have broken arch by trying to install stuff by following old deprecated guides. It’s not hard to break, but it’s also very achievable to have a problem free time.
I was thinking the same thing, I have installed it on a laptop and it’s almost boring how it just works.
TBH, pacman aur is damn easier than managing PPA’s on Ubuntu
Jup. I think I’ve had some 3 actual issues the past 2 years on EndeavourOS. But the Endeavour team did a good job of warning me on Discord/RSS or at least provide tutorials and explanations afterwards.
One of the issues was in regard to Grub (fixed by Timeshift rollback and a one-liner), one was in regard to some rogue Nvidia bug crashing the login window (fixed by Timeshift rollback and waiting a few days before updating again), and one was Nvidia removing support for GTX1000 cards and older (Nvidia, WHYYYYYYYY?!).
For reference, I had what felt like similar annoying bugs (and much worse) on Windows 10 about every month, but without any useful support from Microsoft. :(
EDIT: speaking of the devil. A fourth issue just popped up.
Yeah this one REALLY sucked on my laptop still running a 960M. But hey, after the fix (which I think was just locking the driver package?) I just don’t gotta worry anymore, so that’s cool.