My machines got borked every time I tried to do a Debian or Fedora dist-upgrade following the official guide, like 4 times total. Rolling updates on Arch require manual intervention once in a blue moon and haven’t broken my system since I got rid of Nvidia
Ubuntu will actively break itself via snapd at like 2am on a Sunday.
Fedora could not do a fully system update on a 1GB VPS because dnf would OOM.
The dumbest thing I’ve seen Arch do in over a decade of using it is put RabbitMQ in its official repos while also rolling the latest version of Erlang which RabbitMQ doesn’t support.
I have Arch (btw) on my laptop which is the tinkering machine that only I use, and a Win10/Linux dual-boot desktop which is the one other people use that I’m not allowed to break. I had Fedora Silverblue on there originally because I figured it would be pretty stable, but it honestly gave me nothing but trouble. I switched that one over to CachyOS and it’s been smooth sailing ever since.
I had nothing but trouble with Suse, Fedora and Debían on my nightmare of a machine (laptop with AMD/nvidia GPUs) and honestly thought that was my lot until I hit upon Arch, which I have been more than happy with for over 3 years now.
All I know is I was ready to go through the process to go from 12 to 13 and their documentation was full of disclaimers saying that it’s not officially supported.
I’m 99% sure I was going with their official documentation, which you linked just there.
I can’t speak for what I read or how I interpreted it ~6 months ago, other than to say I understood upgrading was not supported and I was SOL that mine broke.
No, I’ve never used “sloppy backports” (as the only warning of lack of support I can currently find lists as a problem) and I knew that back then too, so that wasn’t the issue.
All I know is I was ready to go through the process to go from 12 to 13 and their documentation was full of disclaimers saying that it’s not officially supported.
My machines got borked every time I tried to do a Debian or Fedora dist-upgrade following the official guide, like 4 times total. Rolling updates on Arch require manual intervention once in a blue moon and haven’t broken my system since I got rid of Nvidia
Ubuntu will actively break itself via
snapdat like 2am on a Sunday.Fedora could not do a fully system update on a 1GB VPS because
dnfwould OOM.The dumbest thing I’ve seen Arch do in over a decade of using it is put RabbitMQ in its official repos while also rolling the latest version of Erlang which RabbitMQ doesn’t support.
I have Arch (btw) on my laptop which is the tinkering machine that only I use, and a Win10/Linux dual-boot desktop which is the one other people use that I’m not allowed to break. I had Fedora Silverblue on there originally because I figured it would be pretty stable, but it honestly gave me nothing but trouble. I switched that one over to CachyOS and it’s been smooth sailing ever since.
I had nothing but trouble with Suse, Fedora and Debían on my nightmare of a machine (laptop with AMD/nvidia GPUs) and honestly thought that was my lot until I hit upon Arch, which I have been more than happy with for over 3 years now.
Same, but with an ancient Nvidia card even…
Isn’t Debian pretty clear that they don’t support upgrades and it’s likely to break if you try?
So I should just reinstall my system every two years? What is this, Windows?
🤷
I felt the same way and held my nose to dive in to rolling release as a result.
No, you may be thinking about combining repos from different releases aka frankendebian? That isn’t supported. Upgrades are definitely supported.
All I know is I was ready to go through the process to go from 12 to 13 and their documentation was full of disclaimers saying that it’s not officially supported.
I did my best, and it broke.
Can you show me this documentation? Debian famously takes great care to ensure a good upgrade path with thorough instructions, like here https://www.debian.org/releases/stable/release-notes/upgrading.en.html but a typical desktop user would just edit apt repos and dist-upgrade.
I’m 99% sure I was going with their official documentation, which you linked just there.
I can’t speak for what I read or how I interpreted it ~6 months ago, other than to say I understood upgrading was not supported and I was SOL that mine broke.
No, I’ve never used “sloppy backports” (as the only warning of lack of support I can currently find lists as a problem) and I knew that back then too, so that wasn’t the issue.
I remember them having this in the docs in the past, recommending a reinstall instead. But it seems that is no longer the case.
All I know is I was ready to go through the process to go from 12 to 13 and their documentation was full of disclaimers saying that it’s not officially supported.
I did my best, and it broke.