Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34481 - [dhcpcd] should depend on dnsutils to set hostname according to dhcp

Attached to Project: Arch Linux
Opened by Wolfgang Mader (ReedWood) - Tuesday, 26 March 2013, 16:37 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 12 May 2015, 17:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

dhcpcd is able to set the hostname of the local host according to the information from the dhcp server via the hook

/lib/dhcpcd/dhcpcd-hooks/29-lookup-hostname

This hook used 'dig' or 'host' to derive the hostname. 'dig' and 'host' are part of dnsutils. Therefore, it must be installed and I argue that dhcpcd should depend on it.

Moreover, the file
/etc/hostname
must not be present.

There is discussion and a bug report over in the gentoo camp.
https://bugs.gentoo.org/433441?id=433441
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 12 May 2015, 17:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  See last comment by upstream developer.
Comment by Jakub Klinkovský (lahwaacz) - Saturday, 05 October 2013, 10:28 GMT
This could be generalized as "dhcpcd should track (optional) dependencies for hooks", there are other untracked dependencies:

- wpa_supplicant package for the 10-wpa_supplicant hook
- openresolv package for the 20-resolv.conf hook
- dnsutils package for the 29-lookup-hostname hook (mentioned above)
- inetutils package for the 30-hostname hook

All hooks check if the required tool is available, and some (like 30-hostname) provide a fallback solution, so dhcpcd works just fine without those dependencies. But I still think they should be tracked, at least as optional dependencies.
Comment by Roy Marples (rsmarples) - Thursday, 22 January 2015, 20:36 GMT
Newer dhcpcd's fall back to getent(1) so no dependancy needs to be made as such.

Loading...