Ubuntu
resolvconf package

RM: resolvconf, openresolv (and blacklist)

Bug #1990743 reported by Jonathan Kamens
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openresolv (Ubuntu)
Fix Released
High
Unassigned
resolvconf (Ubuntu)
Fix Released
High
Unassigned

Bug Description

systemd-resolved now implements the resolvconf interface, and Conflicts: with other implementations of resolvconf. Installing these other implementations on a full system or container will wrongly result in removal of the systemd-resolved package. We should drop resolvconf and openresolv now from the archive (and blacklist them). Users requesting resolvconf will be directed to systemd-resolved. Packages which depend/recommend systemd-resolved will also get the supported implementation going forward.

[Original description]
Setting up resolvconf (1.91ubuntu1) ...
cp: not writing through dangling symlink '/etc/resolvconf/resolv.conf.d/original'
dpkg: error processing package resolvconf (--configure):
 installed resolvconf package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 resolvconf
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ ls -l /etc/resolvconf/resolv.conf.d/original
lrwxrwxrwx 1 root root 39 Jan 2 2019 /etc/resolvconf/resolv.conf.d/original -> ../run/systemd/resolve/stub-resolv.conf

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: resolvconf 1.91ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 24 18:48:31 2022
InstallationDate: Installed on 2019-01-02 (1361 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

See original description
Revision history for this message
Jonathan Kamens (jik) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

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
Revision history for this message
Jonathan Kamens (jik) wrote :

*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 should fix bugs in it. 🤷

Steve Langasek (vorlon)
tags: added: foundations-triage-discuss
Revision history for this message
Steve Langasek (vorlon) wrote :

> 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: systemd-resolved, which Conflicts: with resolvconf. So the expected effect on upgrade is that resolvconf be removed in favor of systemd-resolved.

So, the preferred way to handle bugs in the resolvconf package is to remove it. It just hasn't been removed from the archive yet because there are reverse-dependencies inherited from Debian to be sorted through.

Revision history for this message
Jonathan Kamens (jik) wrote :

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 there's nothing more to be done here. :shrug:

Revision history for this message
Steve Langasek (vorlon) wrote :

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 get the supported implementation going forward.

Using this bug for the removal of resolvconf and openresolv.

Changed in resolvconf (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → High
summary: - resolvconf install fails upgrading from Jammy to Kinetic
+ RM: resolvconf, openresolv (and blacklist)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

Removing packages from kinetic:
 openresolv 3.12.0-2 in kinetic
  openresolv 3.12.0-2 in kinetic amd64
  openresolv 3.12.0-2 in kinetic arm64
  openresolv 3.12.0-2 in kinetic armhf
  openresolv 3.12.0-2 in kinetic i386
  openresolv 3.12.0-2 in kinetic ppc64el
  openresolv 3.12.0-2 in kinetic riscv64
  openresolv 3.12.0-2 in kinetic s390x
 resolvconf 1.91ubuntu1 in kinetic
  resolvconf 1.91ubuntu1 in kinetic amd64
  resolvconf 1.91ubuntu1 in kinetic arm64
  resolvconf 1.91ubuntu1 in kinetic armhf
  resolvconf 1.91ubuntu1 in kinetic i386
  resolvconf 1.91ubuntu1 in kinetic ppc64el
  resolvconf 1.91ubuntu1 in kinetic riscv64
  resolvconf 1.91ubuntu1 in kinetic s390x
Comment: Conflicts with systemd-resolved, which is now the preferred implementation as of kinetic; LP: #1990743
2 packages successfully removed.

Changed in resolvconf (Ubuntu):
status: Triaged → Fix Released
Changed in openresolv (Ubuntu):
status: New → Fix Released
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.