Your message dated Wed, 05 Aug 2026 17:31:09 +0000 with message-id <[email protected]> and subject line Bug#1143544: Removed package(s) from unstable has caused the Debian Bug report #667647, regarding isc-dhcp-client: man dhcp-options is wrong about the client behaviour on option host-name 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.) -- 667647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667647 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: isc-dhcp-client Version: 4.2.2.dfsg.1-4 Severity: normal The following is a quote from man dhcp-options. | option host-name string; | | This option specifies the name of the client. The name may or may not | be qualified with the local domain name (it is preferable to use the | domain-name option to specify the domain name). See RFC 1035 for | character set restrictions. This option is only honored by | dhclient-script(8) if the hostname for the client machine is not set. Unfortunately the last sentence is subtly wrong. To see why we need to look at /sbin/dhclient-script. | set_hostname() { | local current_hostname | | if [ -n "$new_host_name" ]; then | current_hostname=$(hostname) | | # current host name is empty, '(none)' or 'localhost' or differs from new one from DHCP | if [ -z "$current_hostname" ] || | [ "$current_hostname" = '(none)' ] || | [ "$current_hostname" = 'localhost' ] || | [ "$current_hostname" = "$old_host_name" ]; then | if [ "$new_host_name" != "$old_host_name" ]; then | hostname "$new_host_name" | fi | fi | fi | } So old_host_name and new_host_name are controlled by the atta^Wdhcp server. To reproduce set up a client machine running isc-dhcp-client named foo and a server running isc-dhcp-server. The server configuration should contain the following lines. | host foo { | hardware ethernet 11:22:33:44:55:66; # replace with foo's mac address | option host-name "foo"; | } Now machine foo runs dhclient and obtains a lease. It then releases the lease. Now change the option host-name to "bar". The client machine now runs dhclient again. In this second run old_host_name matches current_hostname, so it really updates the system hostname. And this is where the documentation is wrong. I suggest extending the last sentence to the following sentence. | This option is only honored by dhclient-script(8) if the hostname for | the client machine is not set or the dhcp server has previously sent | the hostname of the client machine and now sends a different name. If on the other hand the current behaviour is not desired, I suggest changing the dhclient-script to remove the || [ "$current_hostname" = "$old_host_name" ] check to match the description of the documentation. Thanks Helmut
--- End Message ---
--- Begin Message ---Version: 4.4.3-P1-8+rm Dear submitter, as the package isc-dhcp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1143544 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
