[Bug 1990187] Re: systemd-resolved recommends libnss-resolve in kinetic, pulls it into minimal system where it was explicitly excluded before

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 251.4-1ubuntu6

---------------
systemd (251.4-1ubuntu6) kinetic; urgency=medium

  * test: deny-list TEST-36-NUMAPOLICY on ppc64el (LP: #1989969)
    File: debian/patches/lp1989969-test-deny-list-TEST-36-NUMAPOLICY-on-ppc64el.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0f61b31fbeb57cf7e47a5f0922fd2ff47b81caa7
  * debian/control: drop systemd-resolved Recommends: (LP: #1990187)
    libnss-resolve was previously explicitly excluded from ubuntu-minimal,
    and this Recommends: reverses that change. While here, drop
    libnss-myhostname too, because it is in universe and there is no real
    need for systemd-resolved to Recommends: it.
    File: debian/control
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=88c134fac13b738efdcc657e160350c061d0a018
  * debian/control: set Priority: important on systemd-resolved (LP: #1990278)
    Since this package used to be a part of the systemd binary package,
    systemd-resolved would be installed by debootstrap by default. Retain
    this previous behavior by setting Priority: important on
    systemd-resolved.
    File: debian/control
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1d9ca06dfe8351ed4d03073fbafa5e2212fe4fcb

systemd (251.4-1ubuntu5) kinetic; urgency=medium

  * enable building systemd-boot for riscv64 (LP: #1989457)

 -- Nick Rosbrook <nick.rosbrook at canonical.com>  Tue, 20 Sep 2022
11:19:06 -0400

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990187

Title:
  systemd-resolved recommends libnss-resolve in kinetic, pulls it into
  minimal system where it was explicitly excluded before

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In kinetic, systemd-resolved now Recommends: libnss-resolve, pulling
  it into the ubuntu-minimal seed.

  In the past we briefly had libnss-resolve seeded (between xenial and
  bionic LTSes but not in any LTS) but it was removed because:

   - it was redundant; /etc/resolv.conf was consistent and correct.
   - its presence could mask wrong DNS configuration resulting in difficult-to-debug differences in behavior between applications that did use nss_resolved via /etc/nsswitch.conf and those that did not (examples: i386 binaries that could not use nss_resolved because it was not installed; statically-linked go implementations that parsed /etc/resolve.conf directly and did not load NSS modules)

  This new recommends was noticed specifically because of some broken
  kinetic container images where /etc/resolv.conf was broken (empty) and
  *some* applications still worked via nss but others failed by trying
  to use the DNS protocol directly.  (I.e.: 2nd point above)

  I believe systemd-resolved should drop its recommends on libnss-
  resolve for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990187/+subscriptions