3 ms·
they report everything upstream and push for it to get fixed there That's what most ditros do. Fedora and openSUSE anyway. While we wait for upstream to fix th
by mapleoin 14y ago
they report everything upstream and push for it to get fixed there
That's what most ditros do. Fedora and openSUSE anyway. While we wait for upstream to fix the issue and release a new version, we prefer to have a working package, though.
- pavanky 14y agoaur.
- sirclueless 14y agoTrue, though I think the "Push for it to get fixed" part is more important than you are giving credit for. Bugs from Arch are urgent, simply because all their users are stuck waiting on the fix which means affected users will be interested in updating and communicating about the upstream report. Also they are probably on an unpatched recent stable release, which makes a good baseline -- either the bug was fixed in master since the recent release, or it is still present and real. There's little question whether a bug is caused by a distro-specific patch or not, because Arch linux packages are more or less thin build scripts around unpatched sources. You find things like .desktop files and systemd unit files in the Arch package repo, but not many source patches that might introduce unreproducible bugs. It's easy to see why running Arch is painful for a sysadmin: You get stuck with all the variance in maintenance quality of upstream packages with not much recourse other than building a fixed package from source yourself (thankfully this is pretty easy with Arch's build system). On the other hand it's easy to see why this is great for the linux ecosystem: A popular distro running recent unpatched stable binaries means a lot of testing of releases soon after they come out, which surfaces upstream problems faster and encourages faster maintenance cycles and better upstream releases that benefit everyone.