nixCraft on Mastodon

you are viewing a single comment's thread
view the rest of the comments
[–] 38 points 1 week ago (5 children)

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

  • source
  • hideshow 10 child comments
  • [–] 11 points 1 week ago

    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.

  • source
  • parent
  • [–] 4 points 1 week ago

    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.

  • source
  • parent
  • [–] 2 points 1 week ago

    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.

  • source
  • parent
  • [–] -4 points 1 week ago (3 children)

    Isn't Debian pretty clear that they don't support upgrades and it's likely to break if you try?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 6 points 1 week ago (1 child)

    No, you may be thinking about combining repos from different releases aka frankendebian? That isn't supported. Upgrades are definitely supported.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 week ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 week ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 week ago

    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.

  • source
  • parent
  • [–] 1 point 1 week ago (1 child)

    I remember them having this in the docs in the past, recommending a reinstall instead. But it seems that is no longer the case.

  • source
  • parent
  • hideshow 2 child comments