Bug#583991: marked as done (isc-dhcp-client uses different location for hooks)
Your message dated Mon, 12 Jul 2010 11:08:20 +
with message-id e1oygs0-0001kf...@franck.debian.org
and subject line Bug#570896: fixed in resolvconf 1.46
has caused the Debian Bug report #570896,
regarding isc-dhcp-client uses different location for hooks
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 ow...@bugs.debian.org
immediately.)
--
570896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: isc-dhcp-client
Version: 4.1.0-1
Severity: important
Hi,
I know that isc-dhcp-client is still in experimental. However, I think
that concerns that I raise here must be handle before a package is uploaded
in unstable.
With this version, you change the location of configuration files. In
particular, /etc/dhcp3/dhclient-{enter,exit}-hooks.d/ is changed into
/etc/dhcp/dhclient-{enter,exit}-hooks.d/
The problem is that external packages are using the previous location. When
installing the new isc-dhcp-client, some features (avahi, ...) are not here
anymore and other are broken (DNS with resolvconf, see below from this
particular problem)
If you decide to maintain this new location, I think you should clone this
bug report to each package shipping files in
/etc/dhcp3/dhclient-{enter,exit}-hooks.d/ and asking them to copy/symlink/...
their files into /etc/dhcp/dhclient-{enter,exit}-hooks.d/
Then, you should Breaks (or Conflicts) all packages that ship file in dhcp3 and
not in dhcp (ie something like
Breaks: avahi-autoipd (= last_version_without_/etc/dhcp/_files)
)
With resolvconf, the problem is even more serious. ie, installing the current
isc-dhcp-client breaks the DNS but removing (and reinstalling dhcp3-client)
does not solve the problem.
Here is what happens:
* isc-dhcp-client is installed, no /etc/dhcp/dhclient-enter-hooks.d/resolvconf
is present.
= on lease acquisition, /etc/resolv.conf is rewriten with internal scripts
breaking the symlink to /etc/resolvconf/run/resolv.conf
* I added /etc/dhcp/dhclient-enter-hooks.d/resolvconf (copied from
/etc/dhcp3/dhclient-enter-hooks.d/resolvconf)
= /etc/resolvconf/run/resolv.conf is now correctly updated but
/etc/resolv.conf has been changed and is a plain file now
* So DNS servers are incorrect and never updated anymore is /etc/resolv.conf
= users must manually recreate the /etc/resolv.conf symlink (not really a
problem for an experimental package)
This explain why it is important that there must never be a resolvconf package
installed (or even unpacked ?) without
/etc/dhcp/dhclient-enter-hooks.d/resolvconf together with the isc-dhcp-client
package. The dependency on your package must ensure this (and a new resolvconf
package must provide a /etc/dhcp/dhclient-enter-hooks.d/resolvconf is you
maintain this path change)
Regards,
Vincent (that will switch back to dhcp3-client for now)
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500,
'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-rc6-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages isc-dhcp-client depends on:
ii debianutils 3.2.1 Miscellaneous utilities specific t
ii ifupdown 0.6.9 high level tools to configure netw
ii isc-dhcp-common 4.1.0-1common files used by all the isc-d
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libssl0.9.8 0.9.8k-5 SSL shared libraries
isc-dhcp-client recommends no packages.
Versions of packages isc-dhcp-client suggests:
ii avahi-autoipd 0.6.25-1 Avahi IPv4LL network address confi
ii resolvconf1.45 name server information handler
-- no debconf information
---End Message---
---BeginMessage---
Source: resolvconf
Source-Version: 1.46
We believe that the bug you reported is fixed in the latest version of
resolvconf, which is due to be installed in the Debian FTP archive:
resolvconf_1.46.dsc
to main/r/resolvconf/resolvconf_1.46.dsc
resolvconf_1.46.tar.gz
to main/r/resolvconf/resolvconf_1.46.tar.gz
resolvconf_1.46_all.deb
to main/r/resolvconf/resolvconf_1.46_all.deb
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 570...@bugs.debian.org,
and the maintainer will reopen the
Bug#583991: marked as done (isc-dhcp-client uses different location for hooks)
Your message dated Mon, 12 Jul 2010 11:08:20 +
with message-id e1oygs0-0001kn...@franck.debian.org
and subject line Bug#583991: fixed in resolvconf 1.46
has caused the Debian Bug report #583991,
regarding isc-dhcp-client uses different location for hooks
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 ow...@bugs.debian.org
immediately.)
--
583991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: isc-dhcp-client
Version: 4.1.0-1
Severity: important
Hi,
I know that isc-dhcp-client is still in experimental. However, I think
that concerns that I raise here must be handle before a package is uploaded
in unstable.
With this version, you change the location of configuration files. In
particular, /etc/dhcp3/dhclient-{enter,exit}-hooks.d/ is changed into
/etc/dhcp/dhclient-{enter,exit}-hooks.d/
The problem is that external packages are using the previous location. When
installing the new isc-dhcp-client, some features (avahi, ...) are not here
anymore and other are broken (DNS with resolvconf, see below from this
particular problem)
If you decide to maintain this new location, I think you should clone this
bug report to each package shipping files in
/etc/dhcp3/dhclient-{enter,exit}-hooks.d/ and asking them to copy/symlink/...
their files into /etc/dhcp/dhclient-{enter,exit}-hooks.d/
Then, you should Breaks (or Conflicts) all packages that ship file in dhcp3 and
not in dhcp (ie something like
Breaks: avahi-autoipd (= last_version_without_/etc/dhcp/_files)
)
With resolvconf, the problem is even more serious. ie, installing the current
isc-dhcp-client breaks the DNS but removing (and reinstalling dhcp3-client)
does not solve the problem.
Here is what happens:
* isc-dhcp-client is installed, no /etc/dhcp/dhclient-enter-hooks.d/resolvconf
is present.
= on lease acquisition, /etc/resolv.conf is rewriten with internal scripts
breaking the symlink to /etc/resolvconf/run/resolv.conf
* I added /etc/dhcp/dhclient-enter-hooks.d/resolvconf (copied from
/etc/dhcp3/dhclient-enter-hooks.d/resolvconf)
= /etc/resolvconf/run/resolv.conf is now correctly updated but
/etc/resolv.conf has been changed and is a plain file now
* So DNS servers are incorrect and never updated anymore is /etc/resolv.conf
= users must manually recreate the /etc/resolv.conf symlink (not really a
problem for an experimental package)
This explain why it is important that there must never be a resolvconf package
installed (or even unpacked ?) without
/etc/dhcp/dhclient-enter-hooks.d/resolvconf together with the isc-dhcp-client
package. The dependency on your package must ensure this (and a new resolvconf
package must provide a /etc/dhcp/dhclient-enter-hooks.d/resolvconf is you
maintain this path change)
Regards,
Vincent (that will switch back to dhcp3-client for now)
-- System Information:
Debian Release: squeeze/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500,
'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-rc6-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages isc-dhcp-client depends on:
ii debianutils 3.2.1 Miscellaneous utilities specific t
ii ifupdown 0.6.9 high level tools to configure netw
ii isc-dhcp-common 4.1.0-1common files used by all the isc-d
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libssl0.9.8 0.9.8k-5 SSL shared libraries
isc-dhcp-client recommends no packages.
Versions of packages isc-dhcp-client suggests:
ii avahi-autoipd 0.6.25-1 Avahi IPv4LL network address confi
ii resolvconf1.45 name server information handler
-- no debconf information
---End Message---
---BeginMessage---
Source: resolvconf
Source-Version: 1.46
We believe that the bug you reported is fixed in the latest version of
resolvconf, which is due to be installed in the Debian FTP archive:
resolvconf_1.46.dsc
to main/r/resolvconf/resolvconf_1.46.dsc
resolvconf_1.46.tar.gz
to main/r/resolvconf/resolvconf_1.46.tar.gz
resolvconf_1.46_all.deb
to main/r/resolvconf/resolvconf_1.46_all.deb
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 583...@bugs.debian.org,
and the maintainer will reopen the
