On Tue, Dec 05, 2017 at 05:36:10PM +0000, Ian Jackson wrote: > Don Armstrong writes ("Bug#883573: Reevaluate libpam-systemd systemd-sysv > dependency ordering (746578)"): > > On Tue, 05 Dec 2017, Julian Andres Klode wrote: > > > I thus opened bug 883569 against systemd, but mbiebl would like to > > > get permission from the you first. > > I think it would be sensible for the TC to explicitly grant or > withhold permission. > > > As systemd-shim does not (appear to?) have an active maintainer, and > > this should be moot for stretch->buster, I don't personally see a > > problem. [Perhaps a NEWS entry or something in the release notes might > > be a nice gesture?] > > FAOD, I regard myself as a caretaker for system-shim.
Then please adopt the package? > > > Does anyone have a counter-argument? > > I don't. The argument presented in the head article seem to make > sense to me. But I don't feel I understand all the implications. > > One question I have is about this: "several packages now require just > systemd-sysv". Can someone refer to some examples, please ? > $ grep-aptavail -FDepends systemd-sysv --and --not -FDepends systemd-shim -nsPackage | grep -v ^jak friendly-recovery gpsd mandos micro-httpd munin numad pk4 prometheus prometheus-node-exporter runit-systemd systemd-cron gpsd micro-httpd numad pk4 prometheus prometheus-node-exporter systemd-cron freeipa-server tinysshd tinysshd I think another major problem (with bug 883555) though is that systemd-shim is not Multi-Arch: foreign like systemd-sysv. In that case, systemd-shim was first marked for install, but then for removal as systemd-shim:foreign was to be installed. And then it picked systemd-sysv somehow. In summary, libpam-systemd:foreign is currently not installable if systemd-shim is installed. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en