FS#17885 - [dhclient] personal dhclient.conf
Attached to Project:
Arch Linux
Opened by Gergely (imrehg) - Monday, 18 January 2010, 02:58 GMT
Last edited by Isenmann Daniel (ise) - Saturday, 30 January 2010, 10:23 GMT
Opened by Gergely (imrehg) - Monday, 18 January 2010, 02:58 GMT
Last edited by Isenmann Daniel (ise) - Saturday, 30 January 2010, 10:23 GMT
|
Details
Description:
Been trying to upgrade the dhclient package, but it fails, complaining that /etc/dhclient.conf already exists in the system. Checking it out in the package, it ideed has someone's personal dhclient.conf in it, causing the upgrade to break. Additional info: * dhclient 4.1.0.p1-2 Steps to reproduce: Try to upgrade from 3.1.2p1-3 -> 4.1.0.p1-2 |
This task depends upon
Closed by Isenmann Daniel (ise)
Saturday, 30 January 2010, 10:23 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with pkgversion -3
Saturday, 30 January 2010, 10:23 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with pkgversion -3
dhclient 3.x had script located in /sbin/
dhclient 4.x has script moved to /usr/sbin
I had to correct network script accordingly. This is not a big deal, would be nice though to get small warning.
In general if system files are moved it would be nice to get some sort of warning. Users are compiling their own software and knowing that that system file was moved could help troubleshoot user potential problems with custom compiled/modified software.
script "/etc/dhclient-script"
To fix http://bugs.archlinux.org/task/17904
Or maybe there is a better fix - there seems to be some packaging issue, since dhclient by default looks for its own script file in the wrong place :/
- Jakub's advice should be followed (i.e., the /etc/dhclient.conf file should ship with only the line `` script "/etc/dhclient-script ''); and
- the file currently shipped as /etc/dhclient.conf should instead be shipped as /etc/dhclient.conf.example.
It is also my opinion that Michal should open a separate bug for his issue, which I believe is quite different.
If the "vanilla" version of the program expects /sbin/dhclient-script, shouldn't this script be put there?
Or the program patched to look for the script inside /etc/ ?
1. Install the dhclient.conf file as dhclient.conf.example
2. Move dhclient-script back to /sbin/ where it is located as defined in the sourcecode
Daniel: I did some experimenting and it appears that, in the absence of an /etc/dhclient.conf file, dhclient will behave as if it had been given the file you intend to ship as /etc/dhclient.conf.example. Please verify this before committing to a solution, as my experiments may have been flawed (eg, I may have failed to nuke the cached leases, or any number of other oversights on my part).