<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[What are the worst distro-specific problems you have faced?]]></title><description><![CDATA[<p dir="auto">More specifically, issues for one distro (or maybe family of distros if applicable) and not other distros.</p>
<p dir="auto">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?!</p>
<p dir="auto">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.</p>
<p dir="auto">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.</p>
]]></description><link>https://forum.ieu.app/topic/d7bfbf9d-a256-4b71-afcb-4c2d05ff35bb/what-are-the-worst-distro-specific-problems-you-have-faced</link><generator>RSS for Node</generator><lastBuildDate>Sat, 05 Sep 2026 18:40:50 GMT</lastBuildDate><atom:link href="https://forum.ieu.app/topic/d7bfbf9d-a256-4b71-afcb-4c2d05ff35bb.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 22 Aug 2026 09:25:34 GMT</pubDate><ttl>60</ttl></channel></rss>