Bug#1064133: systemd-resolved: Using systemd-resolved as drop-in replacements breaks in conjunction with ifupdown

[Luca Boccassi]

Control: tags -1 -upstream
Control: tags -1 wontfix
Control: close -1

On Sun, 3 Mar 2024 01:14:03 +0100 Felix Jacobi <felix at jacobi-bs.de>
wrote:
> In my opinion, it should be possible to use systemd-resolved along
with 
> the original resolvconf again. This could re-allow using 
> systemd-resolved in cases, where the protocol specific identifiers
are 
> relevant (in conjunction with a custom resolvconf hook).
> 
> Maybe /usr/sbin/resolvconf could be managed with update-alternatives
or 
> the symlink from /usr/sbin/resolvconf to resolvectl could be shipped
in 
> a separate package?

Sorry, but the current setup is very much intentional. There is not
going to be yet-another-package, and there is not going to be update-
alternatives, which is an unholy mess. If you want to use sd-resolved,
just don't bother with ifupdown - there is no reason to use that in
2024, for headless systems use networkd and for GUI systems use
network-manager.

-- 
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/20240526/d43ecf14/attachment.sig>