https://security-tracker.debian.org/tracker/CVE-2024-47176, archive
As of 10/1/24 3:52 UTC time, Trixie/Debian testing does not have a fix for the severe cupsd security vulnerability that was recently announced, despite Debian Stable and Unstable having a fix.
Debian Testing is intended for testing, and not really for production usage.
https://tracker.debian.org/pkg/cups-filters, archive
So the way Debian Unstable/Testing works is that packages go into unstable/ for a bit, and then are migrated into testing/trixie.
Issues preventing migration:
∙ ∙ Too young, only 3 of 5 days old
Basically, security vulnerabilities are not really a priority in testing, and everything waits for a bit before it updates.
I recently saw some people recommending Trixie for a "debian but not as unstable as sid and newer packages than stable", which is a pretty bad idea. Trixie/testing is not really intended for production use.
If you want newer, but still stable packages from the same repositories, then I recommend (not an exhaustive list, of course).:
- Opensuse Leap (Tumbleweed works too but secure boot was borked when I used it)
- Fedora
If you are willing to mix and match sources for packages:
- Flatpaks
- distrobox — run other distros in docker/podman containers and use apps through those
- Nix
Can get you newer packages on a more stable distros safely.
Maybe it's just been good luck, or maybe I pay enough attention to what apt is going to do and know how to deal with it but I've been daily driving sid for years and am convinced it's more stable than arch based on friends I have that run arch...maybe it's just I'm more experienced but it really doesn't break that much. Obviously ymmv.
I think that it's partially due to Debian's focus on stability. If they call it "stable" it's rock solid; if they call it "unstable" it's still fairly usable, it's just the 0.1% odds that it'll evoke Cthulhu in the process.
In my Sid times I managed to break it, but to be fair it was more like a Frankendebian at that point.