Your message dated Mon, 05 Feb 2024 22:49:43 +0000
with message-id <[email protected]>
and subject line Bug#1025062: fixed in isc-dhcp 4.4.3-P1-5~exp2
has caused the Debian Bug report #1025062,
regarding systemd-resolved Provides: resolvconf, but is missing the
isc-dhcp-client integration from resolvconf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1025062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025062
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-resolved,isc-dhcp-client
Hi,
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.
* resolvconf no longer participates in propagating DNS servers from
isc-dhcp-client to systemd-resolved. Neither on the interface level
nor on the package level.
Does that make sense?
Workaround: One can manually place the previous resolvconf script from
https://sources.debian.org/src/resolvconf/1.91%2Bnmu1/etc/dhcp/dhclient-enter-hooks.d/resolvconf/
Helmut
--- End Message ---
--- Begin Message ---
Source: isc-dhcp
Source-Version: 4.4.3-P1-5~exp2
Done: Santiago Ruano Rincón <[email protected]>
We believe that the bug you reported is fixed in the latest version of
isc-dhcp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Ruano Rincón <[email protected]> (supplier of updated isc-dhcp
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 05 Feb 2024 19:29:05 -0300
Source: isc-dhcp
Architecture: source
Version: 4.4.3-P1-5~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian ISC DHCP Maintainers <[email protected]>
Changed-By: Santiago Ruano Rincón <[email protected]>
Closes: 1025062
Changes:
isc-dhcp (4.4.3-P1-5~exp2) experimental; urgency=medium
.
[ Michael Gilbert ]
* Remove myself from the uploaders.
.
[ Santiago Ruano Rincón ]
* Add systemd-resolved integreation hooks. Taken from Ubuntu's. Thanks to
Ken Milmore <[email protected]>
(Closes: #1025062)
* Thanks Michael for all your work!
Checksums-Sha1:
bc43557070c6e7390f5930d376970a57507e5354 2278 isc-dhcp_4.4.3-P1-5~exp2.dsc
b9a0a081197f449380a2e8bb10abcd76b8cf4091 105404
isc-dhcp_4.4.3-P1-5~exp2.debian.tar.xz
fb9fdde5225d37a6f0442241bef93ad10d7e6911 11084
isc-dhcp_4.4.3-P1-5~exp2_amd64.buildinfo
Checksums-Sha256:
25e74f1452f6613eedf904201c6a3ab2cce7040b3f2f594dae30ea10d37582ba 2278
isc-dhcp_4.4.3-P1-5~exp2.dsc
779e28eda95eb8236a14adc3e161336b475c84efde8e999f5f8006765ac35b40 105404
isc-dhcp_4.4.3-P1-5~exp2.debian.tar.xz
eae132611cc3a73233006093ccbb208c856331fbcaf5598f709f22935d7e3299 11084
isc-dhcp_4.4.3-P1-5~exp2_amd64.buildinfo
Files:
e5d5e51352139d33154d585feedbb4ee 2278 net important
isc-dhcp_4.4.3-P1-5~exp2.dsc
6e8417aba45ee949bb9d9e08ea9ed844 105404 net important
isc-dhcp_4.4.3-P1-5~exp2.debian.tar.xz
69f139055f50eb948409c93515cd5c7f 11084 net important
isc-dhcp_4.4.3-P1-5~exp2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCZcFiTQAKCRBitBCJKh26
HWtTAP470RacznrnS1q2/dKb/DwAdgjDhEgEFH8QypJIpq+2+gD/buHw8Le8s+ph
ECeLfBHN1NPTBVV491RFMuEMlZ7JPwo=
=+vTu
-----END PGP SIGNATURE-----
--- End Message ---
