Julian Andres Klode writes ("Re: Bug#883573: Reevaluate libpam-systemd systemd-sysv dependency ordering (746578)"): > 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.
I think that perhaps systemd-shim should be marked M-A foreign. Its function is to provide a dbus service which AIUI is not architecture-dependent. I can easily upload such a change at this stage of the buster cycle. > > FAOD, I regard myself as a caretaker for system-shim. > > Then please adopt the package? I definitely don't feel the sense of knowledge or ownership that would be appropriate for that. > On Tue, Dec 05, 2017 at 05:36:10PM +0000, Ian Jackson wrote: > > 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 What ? Why do these packages depend on system-sysv ? (I mean, for systemd-cron it's kind of obvious but for most of the others it is not.) I checked gpsd as that was something I thought I knew something about and that Depends on netbase | systemd-sysv, which is rather different and seems OK. I reran your search in sid with --not -FDepends netbase and got a shorter list. freeipa-server friendly-recovery lava-dispatcher lava-server mandos micro-httpd munin numad pk4 prometheus prometheus-node-exporter runit-systemd systemd-cron That still seems to have quite a few false positives (micro-httpd, mandos), as well as some minority packages that seem to have gained or maybe always had unfortunate specific init system dependencies (freeipa-server, friendly-recovery). I haven't investigated them in detail. Do you have an example package that is causing the installation failure ? Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.