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 Debian Testiny for a “debian but not as unstable as sid and newer packages than stable”, which is a pretty bad idea. 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.

  • mech@feddit.org
    2·
    8 days ago

    If for some reason you insist on using plain Debian but want newer packages on your private browsing-and-gaming desktop, regularly back up your data and run Debian Unstable.
    Actually read what apt does on a dist-update, and if it wants to remove packages you need without installing replacements, abort and try again tomorrow.

    On any important production system, regularly back up your data and run Stable. You lived without that shiny new feature yesterday, you’ll still survive without it today.