This bug was fixed in the package systemd - 231-7
---------------
systemd (231-7) unstable; urgency=medium
[ Michael Biebl ]
* fsckd: Do not exit on idle timeout if there are still clients connected
(Closes: #788050, LP: #1547844)
[ Martin Pitt ]
* 73-usb-net-by-mac.rules: Split kernel command line import line.
Reportedly this makes the rule actually work on some platforms. Thanks Alp
Toker! (LP: #1593379)
* debian/tests/boot-smoke: Only run 5 iterations
* systemd.postinst: Drop obsolete setcap call for systemd-detect-virt.
Drop corresponding libcap2-bin dependency.
* debian/tests/systemd-fsckd: Robustify check for "unit was running"
(LP: #1624406)
* debian/extra/set-cpufreq: Use powersave with intel_pstate.
This is what we did on xenial, and apparently powersave is still actually
better than performance. Thanks to Doug Smythies for the measurements!
(LP: #1579278)
* Ubuntu: Move ondemand.service from static to runtime enablement.
This makes it easier to keep performance, by disabling ondemand.service.
Side issue in LP: #1579278
* Revert "networkd: remove route if carrier is lost"
This causes networkd to drop addresses from unmanaged interfaces in some
cases. (Closes: #837759)
* debian/tests/storage: Avoid stderr output of stopping
systemd-cryptsetup@.service
* libnss-*.prerm: Remove possible [key=value] options from NSS modules as
well.
(LP: #1625584)
-- Martin Pitt <mp...@debian.org> Tue, 20 Sep 2016 15:03:06 +0200
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
Fix Committed
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
