resolvconf (1.79ubuntu10) bionic; urgency=medium
* Fix race of not injecting resolved config into resolvconf on LXD
container boot. LP: #1763108
-- Dimitri John Ledkov Thu, 12 Apr 2018 12:46:24
+0100
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged => Fix Released
** Packa
** Tags added: id-5acd885138c94c5bb1f96431
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1762899
Title:
/etc/resolv.conf empty after upgrading from 16.04 to 18.40
Status
I think we need to handle this via removal of the resolvconf package on
upgrade. Removal (not purge) seems to be sufficient.
Dimitri, is there any remaining reason for systemd to not conflict: with
resolvconf?
** Changed in: resolvconf (Ubuntu)
Status: Incomplete => Triaged
** Changed in
Yes it is, at 1.79ubuntu9
--
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/1762899
Title:
/etc/resolv.conf empty after upgrading from 16.04 to 18.40
Status in resolvconf
Thanks for reporting. After this upgrade, is the resolvconf package
still installed?
** 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.
h
5 matches
Mail list logo