[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-05-11 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.130ubuntu6 --- initramfs-tools (0.130ubuntu6) cosmic; urgency=medium * Fix formatting for the generated netplan config: headers were missing. -- Mathieu Trudel-Lapierre Thu, 10 May 2018 12:12:03 -0400

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-04-09 Thread Mathieu Trudel-Lapierre
unbound attempts to add itself as a local resolver (pointing to 127.0.0.1). I think this will require specific integration work so that unbound can properly update/ tell systemd-networkd that it wants to be able to serve as a resolver. ** Changed in: squid3 (Ubuntu) Status: New => Invalid

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-04-09 Thread Mathieu Trudel-Lapierre
sendmail only uses an update-libc.d script to reload the daemon on changes to resolv.conf, which should be sufficient for DNS resolution to remain working as it did with resolvconf; seeing as the nameserver will generally not change from 127.0.0.53 ** Changed in: sendmail (Ubuntu) Status:

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-03-26 Thread Mathieu Trudel-Lapierre
Looks like the current behavior should be sufficient for postfix to integrate as well as it did with resolvconf: marking this Invalid. ** Changed in: postfix (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-16 Thread Launchpad Bug Tracker
This bug was fixed in the package ndisc6 - 1.0.3-3ubuntu1 --- ndisc6 (1.0.3-3ubuntu1) bionic; urgency=medium * debian/control: Drop resolvconf to a Suggests:. It's not absolutely necessary to have resolvconf installed to use rdnssd, and resolvconf might fight with

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-16 Thread Mathieu Trudel-Lapierre
dnsmasq Suggests: resolvconf only, and checks before using it. None of the steps involved would break with resolvconf not being present, integration just happens via /etc/resolv.conf normally. ** Changed in: dnsmasq (Ubuntu) Status: New => Invalid -- You received this bug notification

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-16 Thread Mathieu Trudel-Lapierre
vpnc and vpnc-scripts check for existance of /sbin/resolvconf and only Suggests: resolvconf. DNS integration by modifying /etc/resolv.conf (and thus the systemd symlink) should work appropriately and let systemd- resolved know about the new nameservers. ** Changed in: vpnc-scripts (Ubuntu)

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-09 Thread Brian Murray
dnssec-trigger actually has and has had a Breaks with resolvconf so that task seems unnecessary. ** Changed in: dnssec-trigger (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu.

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-06 Thread Steve Langasek
fetchmail integrates with resolvconf via /etc/resolvconf/update- libc.d/fetchmail; I think this warrants another look. ** Changed in: fetchmail (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-06 Thread Brian Murray
fetchmail suggests resolvconf and does not actually utilize it. ** Changed in: fetchmail (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu.

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2017-10-24 Thread Scott Moser
** Changed in: cloud-initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2017-09-19 Thread Steve Langasek
netscript-2.4 is an alternate network manager package which would make its own technology selections independent of Ubuntu defaults and systemd. ** Changed in: netscript-2.4 (Ubuntu) Status: New => Won't Fix ** Changed in: whereami (Ubuntu) Status: New => Triaged ** Changed in:

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2017-09-19 Thread Steve Langasek
isc-dhcp-client only suggests resolvconf, it does not interface with it. ** Changed in: isc-dhcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu.

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2017-09-19 Thread Steve Langasek
dibbler-client doesn't interface with resolvconf, it only recommends it. This does not warrant carrying an Ubuntu delta. ** Changed in: dibbler (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2017-08-29 Thread Scott Moser
I've added open-iscsi and cloud-initramfs-tools and initramfs-tools as also affects. These packages are affected by the generic problem where 'configure_networking' from initramfs-tools is executed in the initramfs ('ip=dhcp' for example) and then the link is left up. In those cases we need to