This was fixed in some release prior to 1.77ubuntu1.
** Changed in: resolvconf (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1085849
Title:
Please don't change the answer to linkify-resolvconf
Status in resolvconf package in Ubuntu:
Fix Released
Bug description:
Resolvconf postinst does this:
db_get resolvconf/linkify-resolvconf
if [ "$RET" = "true" ] ; then
[...]
# Create the link and make sure we don't convert it again on upgrade
[...]
ln -nsf ../run/resolvconf/resolv.conf /etc/resolv.conf
db_set resolvconf/linkify-resolvconf false
fi
The problem with the last line is that it obliterates the original
answer to the question, which makes debugging more difficult. This is
a non-trivial drawback in connection with bug #1000244 .
We could achieve the same result without the aforementioned drawback
if we used an additional debconf question to store the information
that we have made at least one attempt to linkify. Roughly:
db_get resolvconf/linkify-resolvconf
if [ "$RET" = "true" ] ; then
[...]
db_get resolvconf/already-linkified-resolvconf
if [ "$RET" != "true" ] ; then
ln -nsf ...
db_set resolvconf/already-linkified-resolvconf true
fi
fi
The additional debconf question would not be presented to the user and
would default to "false". (I am waiving here the more philosophical
objections that may be brought against the use of debconf as a
registry. :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1085849/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
