Debian Testing/Trixie 移除了 systemd-resolved。
今天，Debian 的 systemd 维护者从 Testing/Trixie/Debian 13（即将进入功能冻结阶段）中移除了 systemd-resolved 和 systemd-nspawn 包，原因是与技术委员会存在分歧。
对于已经在使用 Testing/Trixie/Debian 13 的操作人员，这将导致依赖版本冲突和/或现有服务的丢失；对于从 Stable/Bookworm/Debian 12 升级的用户同样如此。
systemd-resolved 包依赖于其他 systemd 包的确切版本。当用户尝试升级到新版本时，已安装但孤立的 systemd-resolved 包将阻止升级，除非将其移除。
新的安装可以使用 resolvconf。
查看原文
Debian's systemd maintainer today removed both systemd-resolved and systemd-nspawn packages [0] from Testing/Trixie/Debian 13 - soon to be in feature freeze - due to disagreements with the Technical Committee [1].<p>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.<p>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.<p>New installs can use resolvconf.<p>[0] https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/<p>[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098914