This bug was fixed in the package resolvconf - 1.63ubuntu7
---------------
resolvconf (1.63ubuntu7) precise; urgency=low
[ Stéphane Graber ]
* Revert change from 1.63ubuntu5 where /etc/resolv.conf would be linkified
by the upstart/sysvinit job. This wasn't working as / wasn't necessarily
writable at the time.
Instead, make the link at package install time but make it a relative
link which should take care of the chroot usecase where you want
to copy /etc/resolv.conf from outside the chroot into the chroot.
Detect old flag file (/var/lib/resolvconf/convert) and re-run the
conversion code if it's present (to try and fix broken systems).
Use readlink -m when checking the link's destination.
(LP: #924836)
[ Steve Langasek ]
* Use readlink -m also in the postrm, to account for our relative links
-- Stephane Graber <[email protected]> Thu, 02 Feb 2012 14:28:45 -0500
** Changed in: resolvconf (Ubuntu Precise)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924836
Title:
network-manager does not tell plymouth it has started
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924836/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
