25

More specifically, issues for one distro (or maybe family of distros if applicable) and not other distros.

I'll start: NixOS. I love how I can have my whole operating system configuration defined deterministically with configuration files, but what I believe is a serious flaw, is when you choose the "unstable" channel, the channel for receiving the latest packages rather than ones up to 6 months old: stable. Unstable package often build dependencies on device, and I've often faced build failures, why are new package versions given if they fail to build?!

Why can't Nixpkgs backend ensure that new package versions build successfully before shipping them to end users?! It would take a lot of work to do so, but I can't think of any other distros that have this problem: where installing a new package version that came out a few days or even a week ago, has a chance of failing after its made available in the distro's official package manager.

There are a handful of workarounds for your NixOS configuration in this case, but it happens too often for me and I shouldn't have to edit my config for to work around it.

you are viewing a single comment's thread
view the rest of the comments
[-] Zachariah@lemmy.world 10 points 1 day ago

Ubuntu distros really need a ridiculously simple way both via cli and gui to disable snaps.And it needs to be respected through updates and upgrades.

[-] frongt@lemmy.zip 11 points 1 day ago

Snarky answer: there is one, it's called not using Ubuntu

[-] Zorsith 9 points 1 day ago

Reject canonical, return to debian

this post was submitted on 22 Aug 2026
25 points (100.0% liked)

Linux

14763 readers
429 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS