Bug#1101965: systemd-resolved declares ineffective Replaces for systemd due to the /usr-move potentially loosing /usr/lib/systemd/resolv.conf (DEP17 P1)

[Luca Boccassi]

On Thu, 3 Apr 2025 08:24:46 +0200 Helmut Grohne <helmut at subdivi.de>
wrote:
> Package: systemd-resolved
> Version: 257.4-9
> Severity: serious
> User: helmutg at debian.org
> Usertags: dep17p1
> Control: affects -1 + systemd
> 
> Dear systemd maintainers,
> 
> thanks for reintroducing systemd-resolved. I'm not sure why this pops
up
> now, but I now see a /usr-move regression. systemd-resolved now
installs
> /usr/lib/systemd/resolv.conf and in bookworm systemd contained
> /lib/systemd/resolv.conf. Consequently, systemd-resolved declares
> Replaces, but due to /usr-move such Replaces are not effective.
> 
> In principle, I consider this file important to the operation of a
> Debian installation as its loss may render DNS unusable.

Thanks for the report, I always forgot about these details. This file
actually not used, it's just a fallback, the dynamic one in /run/ is
the one we actually use. I've queued a fix to upgrade to Conflicts, it
will be in the next upload.