This situation can only arise on a system which already had systemd-
resolved configured at install time, then had resolvconf installed on
top of it. The real question is, why are you installing resolvconf? It
should no longer be needed in 17.10.
** Changed in: resolvconf (Ubuntu)
Status: New => Incomplete
--
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/1741775
Title:
bad symlink "/etc/resolvconf/resolv.conf.d/original"
Status in resolvconf package in Ubuntu:
Incomplete
Bug description:
Ubuntu 17.10 amd_64
resolvconf 1.79ubuntu8
The symlink at "/etc/resolvconf/resolv.conf.d/original" points to
"../run/systemd/resolve/stub-resolv.conf". This is a broken link as
the relative path does not exist. This causes resolvconf to improperly
(re-)generate "/run/resolvconf/resolv.conf". The link should probably
instead point to the absolute path "/run/systemd/resolve/stub-
resolv.conf".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1741775/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp