Bug#1032937: breaks upgrades if systemd-resolved can't run

[Samuli Suonpää]

> On 14. Mar 2023, at 17.34, Luca Boccassi <bluca at debian.org> wrote:
> 
> Exactly, so the admin shouldn't install a package that in the
> description says:
> 
> "Installing this package automatically overwrites /etc/resolv.conf and
> switches it to be managed by systemd-resolved."
> 
> if that's not what they want to achieve. I agree that the
> /etc/resolv.conf interface is garbage, but there's nothing we can do
> about it, that's just how it works.
> This is the only way read-only images can be supported sanely.

Why exactly is it necessary to overwrite /etc/resolv.conf at postinst, even if
the service will not and can not be started?

Wouldn’t it make more sense to make the symlink at a later stage? For
Instance when the service is actually started?

There’s no point in having resolv.conf symlink to
/run/systemd/resolve/stub-resolv.conf when systemd-resolved is not running.

Samuli