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.

  • Infernal_pizza@lemmy.dbzer0.comEnglish
    13·
    12 hours ago

    This is a fairly minor issue since it’s quite an easy fix, but it really annoys me that Debian doesn’t include the sbin folders in the default user path. Meaning that if you try to run a command that needs sudo, instead of telling you it needs sudo it just says the command doesn’t exist

    • folekaule@lemmy.world
      1·
      52 minutes ago

      I thought this was how unix always has been? Sbin is for root binaries. It doesn’t make sense to include a bunch of commands you don’t have permission to execute in the path. I remember this being the case back in the 90s and didn’t realize it was no longer the norm.