Skip Navigation

Stable Linux distro with up to date packages

Maybe what I'm looking for is the holy grail, but what do you guys suggest as a Distro with a good balance between stability and up-to-date packages?

109 comments
  • OpenSuse Tumbleweed is a great choice for a rolling-release distro that is also really stable too.

    • I second OpenSuse Tumbleweed, only switched back to it after 7+ years and it's been great so far, no packages broke after update so far.

  • Just like the holy grail, a stable and up-to-date distro doesn't exist. Stability and recency of software typically constitute a tradeoff. Human software developers produce some number of bugs per line of code. Unless all changes made to a piece of software are bug fixes, new changes mean new bugs, almost invariably. Therefore the only way to stop the increase of bugs in a piece of software is to stop the changes to it or only do changes that address bugs. In the context of distros, a stable one is a distro where the number of bugs stays constant or decreases over time. This is how Debian, Ubuntu and every other distro that locks its software versions for a certain release work. After a release is out, only bug fix changes are permitted, with some special exceptions. The idea that there are multiple types of stability is a bit of a false narrative. Adding features, adds lines of code, which increases the number of defects. This is a fundamental fact of software engineering that's actively managed during the development cycle of most software. A collection of software like a rolling Linux distro that receives a constant stream of new features may feel bug-free to specific users, however that is typically a coincidence. Just because those X number of people didn't hit any significant defects during their usage, doesn't mean that you won't. This is true for every distro, however stable distros generally have an ever-decreasing number of bugs over their lifespan. In addition, bugs that are never fixed can be documented, workarounded and the workarounds will keep working for the lifespan of the release because there are no changes.

    With all of that out of the way I hope it's clearer why there's a tradeoff between stability and recency of software in distros. There are various strategies to have a bit of both and they typically revolve around letting the bits you want be recent, while keeping everything else stable. These days the easiest and most foolproof way to get new software is via Flatpak or Snap.

    You could of course abandon stability and go for recency via some rolling release distro and see if you step on any significant bugs. Maybe you won't and you'll be happy with that. Many people are.

    As a personal and professional Linux user that lives with and maintains a significant number of machines, I typically go for a stable base like Debian or Ubuntu LTS and update only the software I need via Flatpak, Snap and Docker. I no longer use PPAs. This provides a great balance between stability and recency. But that's just me.

  • I use to be like you. I used Arch for a long time then tried everything else that was similar like tumbleweed etc. Then I used Fedora and forgot about distrohopping entirely. I still use Arch on my pi4 though because it works nicely for use cases like that.

    However I will warn you anything can and will be unstable eventually. Its the nature of software, bugs will happen. For instance recently a package called ostree was pretty much broken on all distros even Fedora which is crazy.

  • Void Linux. A great compromise between being up to date and being stable AF. They're not bleeding edge, but cutting edge, most definitely. For example, they only recently transfered to kernel 6.3, while Arch had it months ago... with instability issues I might add. Void maintainers would rather let these wrinckles get ironed out than implement the latest and greatest.

    It is a rolling release distro, so nothing new there. Packages get regular updates, same as any other rolling release distro, except for the kernel packages which are carefully examined before being submitted in the repo. The number of precompiled packages is not huge, but the src templates are (you just have to compile them from source with xbps-src, which is a piece of cake when you already have the template file).

    The good thing is that all package templates get checked for buildability (test) on GH. If the template passes all tests, it makes it in the repo, if not, it doesn't, simple as that.

    If you think you would be comfortable with Arch, you'd be comfortable with Void as well 😉.

    • Besides those builders that run the checks made by the developers of the apps (is simple running a make check or whatever the build system the package uses, void Linux does have some problems mostly because of the small team.

      One of the biggest one is basically being stuck in 1.X series of musl forever until someone steps up and creates a solution that doesn't require to rebuild all packages because of an ABI breaking change in armv6l systems at 2.X musl series .

  • If you like Plasma or one of the other supported desktops, I suggest trying Siduction for this.

  • Guix is a source based (rolling release) distro. Any package operation you do like like installing, updating, or removing, can be rolled back. So if an update ever breaks anything you can just roll-back and wait for the fix. You can even pin that specific package and continue to upgrade the rest of your system. And every state is saved in a generation, so you can go to any state your system has ever been in package/configuration wise.

    Nix has all of these advantages as well.

109 comments