Upon further inspection, it turns out that systemd-resolved now
implements the resolvconf interface. We should drop resolvconf and
openresolv now from the archive, and users requesting resolvconf will be
directed to systemd-resolved. Packages which depend/recommend systemd-
resolved will also
Given your description, I don't think the upgrade left resolvconf
installed. I think I can my ansible playbook after running the upgrade
and it reinstalled resolvconf which had been uninstalled by the upgrade.
I guess if resolvconf can't be removed yet because of the reverse-
dependencies, then
> It's no skin off my nose—if it's deprecated I'll
> find something else to use—but it seems to me that
> if you're going to keep the package in the repository
> you should fix bugs in it.
Can you provide a full upgrade log for the affected system? systemd in
kinetic Recommends:
** Tags added: foundations-triage-discuss
--
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/1990743
Title:
resolvconf install fails upgrading from Jammy to Kinetic
*shrug* I've had this computer since 2016 and when I first set it up I
used resolvconf to configure it and have continued to do that.
It's no skin off my nose—if it's deprecated I'll find something else to
use—but it seems to me that if you're going to keep the package in the
repository you
resolvconf has not been installed by default in Ubuntu since before
18.04 LTS and is considered deprecated and should not be used. Is there
a reason that you have the package installed?
** Changed in: resolvconf (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
6 matches
Mail list logo
