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

[Luca Boccassi]

Control: severity -1 wishlist
Control: tags -1 wontfix

On Tue, 14 Mar 2023 15:05:20 +0100 Bastian Blank <waldi at debian.org>
wrote:
> Control: severity -1 serious
> 
> Let's make this RC, as it breaks updates.
> 
> The systemd-resolved package modifies a global config file
> /etc/resolv.conf.  This breaks any name resolution if resolved is not
> running.  Especially if it can't run at all.
> 
> | root at debian-sid:~# ls -al /etc/resolv.conf 
> | lrwxrwxrwx 1 root root 40 Mar 14 14:03 /etc/resolv.conf ->
/../run/systemd/resolve/stub-resolv.conf
> | root at debian-sid:~# getent hosts heise.de
> | 2a02:2e0:3fe:1001:302:: heise.de
> | root at debian-sid:~# systemctl stop systemd-resolved
> | root at debian-sid:~# getent hosts heise.de
> | root at debian-sid:~# 
> 
> Sorry, but the only person to know if resolved can be used is the
admin,
> not a package.

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.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230314/b5b34473/attachment-0001.sig>