This bug was fixed in the package resolvconf - 1.63ubuntu14
---------------
resolvconf (1.63ubuntu14) precise-proposed; urgency=low
* Call db_go after the db_input command so that the debconf error
message is actually shown to the user.
resolvconf (1.63ubuntu13) precise-proposed; urgency=low
[ Stéphane Graber ]
* In is_immutable_file, if lsattr doesn't return anything on stdout,
return 1 and hide stderr. This fixes lsattr failing on non-ext
filesystems. (LP: #994539)
[ Steve Langasek ]
* Fix syntax of db_input command, which is part of why we're seeing
failures in bug #994539.
resolvconf (1.63ubuntu12) precise-proposed; urgency=low
* Instead of throwing an error that aborts the upgrade when
/etc/resolv.conf is immutable, pop a debconf error message to let the
user know what's happening, then clear the immutable flag and continue
with the installation. LP: #989585.
-- Stephane Graber <[email protected]> Mon, 14 May 2012 12:31:58 -0400
** Changed in: resolvconf (Ubuntu Precise)
Status: Fix Committed => 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/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
immutable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/989585/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
