Control: reassign -1 isc-dhcp-client On Mon, 28 Nov 2022 10:24:55 +0100 Helmut Grohne <hel...@subdivi.de> wrote:
Package: systemd-resolved,isc-dhcp-clientHi, When systemd-resolved started replacing and providing resolvconf, things looked good, but isc-dhcp-client no longer propagates DNS servers to resolved. This used to work when resolvconf and systemd-resolved were coinstallable and one used resolvectl to implement resolvconf. The crux is that resolvconf contains the integration scripts that make isc-dhcp-client run resolvconf even when resolvconf is provided by systemd-resolved. Now that systemd-resolved conflicts with resolvconf, it broke that integration, which is bad. I briefly talked to Michael about this and he figured that we wouldn't want to go through the extra resolvconf layer and rather do things directly. Indeed, this is what has happened for ifupdown already. ifupdown now contains /etc/network/if-*.d/resolved and integrates directly. NetworkManager does it directly likewise. isc-dhcp-client should likely do it as well. Thus I think a good solution to this bug would be: * isc-dhcp-client ships scripts to directly integrate with resolved. * systemd-resolved Breaks isc-dhcp-client in versions that don't integrate.
It would be preferable if isc-dhcp-client ships the resolved integration bits. The Debian package could steal from the Ubuntu package which appears to have some corresponding hooks:
# apt-file list isc-dhcp-client | grep resolved isc-dhcp-client: /etc/dhcp/dhclient-enter-hooks.d/resolved-enter isc-dhcp-client: /etc/dhcp/dhclient-exit-hooks.d/resolved [Note: I did not have a look at those hook scripts at all] I don't think we need a Breaks here. With that said, I'm going to reassign this bug to isc-dhcp-client. Regards, Michael
OpenPGP_signature
Description: OpenPGP digital signature
