by iam-TJ on 3/28/25, 8:38 PM with 3 comments
For operators already using Testing/Trixie/Debian 13 this will lead to dependency version conflicts and/or loss of existing service; for upgrades from Stable/Bookworm/Debian 12 likewise.
systemd-resolved package depends on the exact same version of other systemd packages. When they try to upgrade to newer versions the installed-but-orphaned systemd-resolved package will prevent it unless it is removed.
New installs can use resolvconf.
[0] https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098914
by dyingkneepad on 3/31/25, 7:37 PM
Man, I love and use Debian, but the thing I hate the most about it are these ancient email-based bug-reporting systems and package trackers, like the ones linked in your message. This shit is ancient, and horrible. Some time ago I reported a Debian bug using a HOWTO (what other distro requires a HOWTO in order to report a bug?) and absolutely lost track of it after my report was submitted: I could just never find my report again. I just gave up reporting Debian bugs. These ancient systems are definitely barring me from making contributions to the Debian project.
by patjensen on 3/29/25, 8:51 PM
by JackSlateur on 3/28/25, 11:05 PM
And bluca chose to fuck his users by breaking there shit on purpose.
Very nice, very systemd-ish :/