[Bug 922677] Re: resolvconf should only convert /etc/resolv.conf to a symlink at initial installation time

[Louis Li]

I'm seeing this issue from a clean Ubuntu precise amd64 AMI
(http://cloud.ubuntu.com/ami/).

With nothing but vpnc installed, I did some of the following:

ubuntu at ip-10-116-125-233:~$ sudo vpnc myvpnc.conf
sudo vpnc myvpn.conf
resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything.
VPNC started in background (pid: 12101)...

(but it's not actually connected)

Upgrading resolvconf package:
Unpacking replacement resolvconf ...
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Setting up resolvconf (1.63ubuntu14) ...
Processing triggers for resolvconf ...
resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/922677

Title:
  resolvconf should only convert /etc/resolv.conf to a symlink at
  initial installation time

Status in “resolvconf” package in Ubuntu:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922677/+subscriptions