resolvconf should only convert /etc/resolv.conf to a symlink at initial installation time
Bug #922677 reported by
Stéphane Graber
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
One thing described in the MIR for resolvconf promotion in Precise is that resolvconf won't attempt to convert /etc/resolv.conf on upgrade.
Doing a local test here actually shows that to be wrong, so anyone currently assuming that making /etc/resolv.conf a regular file again will turn off resolvconf will have a bad surprise next time we update the package.
Related branches
Changed in resolvconf (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
This bug was fixed in the package resolvconf - 1.63ubuntu4
---------------
resolvconf (1.63ubuntu4) precise; urgency=low
* dhclient hook: Only trigger if /etc/resolv.conf is a symlink. linkify- resolvconf to false after initial
* postinst: Set resolvconf/
conversion, ensuring upgrades won't convert /etc/resolv.conf to
a symlink if the user manually converted it back to plain text.
(LP: #922677)
* Make resolvconf exit 0 when /etc/resolv.conf isn't a symlink
(instead of exit 1) and update the error message.
-- Stephane Graber <email address hidden> Fri, 27 Jan 2012 12:23:34 -0500