** Changed in: fetchmail (Ubuntu)
Status: Confirmed => Invalid
** Changed in: freedombox-setup (Ubuntu)
Status: Confirmed => Invalid
** Changed in: open-iscsi (Ubuntu)
Status: Triaged => Invalid
** Changed in: openvpn (Ubuntu)
Status: Confirmed => Invalid
** Changed
** Changed in: dnscrypt-proxy (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf
The resolvconf interface is now implemented in the systemd-resolved
package and integrates correctly with systemd. There is no longer a
need for packages to port away from this interface.
** Changed in: android-androresolvd (Ubuntu)
Status: Triaged => Invalid
** Changed in: avahi (Ubuntu)
Does dhcpcd5 version 9.4.1-0.1 solve the issue for you?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf wit
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs integration
Status i
How will the initramfs-tools change be validated? What test case will be
run to make sure it's working as intended?
--
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/1713803
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
** Changed in: initramf
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
squid3: same story as sendmail, uses update-libc.d to get notified of
nameserver changes.
--
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/1713803
Title:
replacement of r
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: N
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
Touch seeded packages,
postfix takes a copy of resolv.conf for its own use, in its own queue
directory. This is already well integrated by way of either resolvconf
triggering the copy on changes (using update-libc.d) or by if-up / if-
down. This will need work to "improve" the integration story; however
postfix should st
dhcpcd5 is redundant as a DHCP implementation in Ubuntu; but it does
"integrate" with resolvconf by way of its own shipped dhcpcd-
hooks/20-resolv.conf. It does check before calling 'resolvconf -a' and
'resolvconf -d' to add/remove its own interface file; and uses this hook
file in order to integra
I had a quick look at unbound, it seems quite difficult. People who
install unbound probably want it so they can have DNSSEC supported in
their local resolver which we can't really do by integrating with
resolved. OTOH, if installing unbound replaces (in some sense) resolved
and everything else int
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203
--
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.ne
Marking open-iscsi high, because passing the configured network
interface from initramfs to root system needs to be done cleanly in the
non-resolvconf world (though this is likely going to be handled via
netplan rather than directly to resolved).
** Changed in: open-iscsi (Ubuntu)
Importance: M
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 systemd-re
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 bec
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)
It looks like open-iscsi makes use of resolvconf in debian/net-
interface-handler, but does check for its presence before doing so. That
said, there is not additional integration with anything to set
nameservers/search domains, so open-iscsi will need further
investigation to see if all is well wit
ndisc6 appears to Recommends: resolvconf (in rdnssd); will drop to a
Suggests. The code in the merge hook for resolvconf already checks
whether resolvconf is present before making use of it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Ubuntu has long carried a patch which "Eliminate all references to
/etc/resolvconf/run." However, freedombox-setup contains the following
code in a preseed file.
# Make sure DNS lookup work after resolvconf is installed
# and set up the Freedombox. Block init.d scripts from running using
# policy
On Fri, Feb 09, 2018 at 10:29:57PM -, Brian Murray wrote:
> pump also suggests resolvconf but the pump binary is modified to have a
> --no-resolvconf switch so this seems easy to workaround. It's worth
> noting that the resolvconf support is a separate patch in debian/patches
> so would be easy
pppconfig seems to fall in the same category as dnssec-trigger and
dnscrypt-proxy.
** Changed in: pppconfig (Ubuntu)
Importance: Undecided => Low
** Changed in: pppconfig (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch s
Integrating openvpn with resolvconf requires the user to take manual
action and modify their openvpn .conf file to call /etc/openvpn/update-
resolv-conf. That being said it'd be good to help users who rely on this
and are upgrading.
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Low
pump also suggests resolvconf but the pump binary is modified to have a
--no-resolvconf switch so this seems easy to workaround. It's worth
noting that the resolvconf support is a separate patch in debian/patches
so would be easy to drop.
** Changed in: pump (Ubuntu)
Importance: Undecided => Lo
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
Touch seeded packages, which is subscribed to resolvconf
dnscrypt-proxy is another package which suggests resolvconf and one
where the integration is not critical. It also seems like a minor issue.
** Changed in: dnscrypt-proxy (Ubuntu)
Importance: Undecided => Low
** Changed in: dnscrypt-proxy (Ubuntu)
Status: New => Confirmed
--
You recei
I've looked more closely at fetchmail and while the resolvconf
integration isn't critical to it working it does improve fetchmail, so
I'm reopening the bug task althought it is a minor issue.
** Changed in: fetchmail (Ubuntu)
Importance: Undecided => Low
** Changed in: fetchmail (Ubuntu)
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
Touch seeded packages, which is subscr
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
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.ne
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Invalid
--
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/1713803
Title:
replacement of resolvconf with
i see no direct calls to resolvconf or hooks installed by cloud-init.
Marking incomplete.
** Changed in: cloud-init (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 Ubunt
isc-dhcp now integrates with resolved.
** Changed in: isc-dhcp (Ubuntu)
Status: Invalid => 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/1713803
Tit
** Tags added: id-59a5e384b534421baba26a0a
--
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/1713803
Title:
replacement of resolvconf with systemd needs integration
Statu
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bu
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: sys
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
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launch
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
Touch seeded packages, which is subscr
bind9 integrates with resolvconf to register itself as a DNS server. It
is reasonable to expect something similar for integration with resolved.
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
android-androresolvd: "This only makes sense to install on a Debian
chroot running on Android."
** Changed in: android-androresolvd (Ubuntu)
Importance: Undecided => Low
** Changed in: android-androresolvd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because y
avahi's hook is for purposes of disabling .local resolution in the event
that a .local domain becomes available as a DNS search domain. This is
the unresolved integration/design issue LP: #327362.
** Changed in: avahi (Ubuntu)
Status: New => Triaged
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/330043
--
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.ne
** Tags added: netplan-transition
--
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/1713803
Title:
replacement of resolvconf with systemd needs integration
Status in andr
** Description changed:
There is a plan to remove resolvconf from the Ubuntu Server image.
resolvconf integrated with other parts of the system in 2 ways:
* hooks invoked on change (/etc/resolvconf/update.d/)
* resolvconf tool (invoked with -a and -d or -u)
Packages which install fi
I filed bug 1714308 to cover dns functionality in the initramfs.
** Description changed:
There is a plan to remove resolvconf from the Ubuntu Server image.
resolvconf integrated with other parts of the system in 2 ways:
* hooks invoked on change (/etc/resolvconf/update.d/)
* resolvconf
At https://bugs.launchpad.net/ubuntu/+source/open-
iscsi/+bug/1713537/comments/1 I described how open-iscsi (iscsi root)
works with resolvconf in xenial -> zesty. We will need a solution for
that path as well as 'root=squashfs:http://./squashfs' that MAAS now
uses.
It seems like we should hav
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 a
49 matches
Mail list logo