[Bug 1625584] Re: Removing libnss-* does not remove corresponding options

[Martin Pitt]

Current SRU got shadowed by a security update, resetting. Will reupload
shortly.

** Changed in: systemd (Ubuntu Xenial)
       Status: Fix Committed => In Progress

** Tags removed: verification-needed

-- 
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/1625584

Title:
  Removing libnss-* does not remove corresponding options

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  libnss-{resolve,mymachines,myhostname} automatically add/remove
  themselves from /etc/nsswitch.conf on installation/removal.

  But when (manually) adding NSS action specifiers, these do not get
  removed along.

  SRU FIX: https://anonscm.debian.org/cgit/pkg-
  systemd/systemd.git/commit/?h=ubuntu-xenial&id=2d08d7e481

  TEST CASE:
    * Install libnss-mymachines. This will change the "hosts" line in /etc/nsswitch.conf from e. g. "files dns" to "files dns mymachines".
    * Edit the file to add an action specifier: "files dns mymachines [!UNAVAIL=return]"
    * Remove/purge libnss-mymachines.
    * In current xenial (229-4ubuntu7)/yakkety (231-6) the hosts line ends up as "files dns [!UNAVAIL=return]", i. e. the action specifier now applies to "dns" but should have been removed.
    * With the fixed version, the action specifier is completely gone.
    * Re-test with installing libnss-resolve (which inserts itself before "dns") and modifying to "files resolve [!UNAVAIL=return] dns [foo=bar]", then purge libnss-resolve again -- this should again remove the [!UNAVAIL=return] but *NOT* "dns [foo=bar]".

  Regression potential: This only affects package removal, so upgrades
  or new installs are not affected. Removals of
  libnss-{mymachines,myhostname,resolvle} must be tested carefully to
  ensure that they don't break nsswitch.conf in any way.

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