Ansgar, On Tue, Jun 30, 2020 at 07:43:52PM +0200, Ansgar wrote: > On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote: > > I am struggling to understand how libelogind0 came to be installed in the > > build > > in the first place. Can you help me understand that? > > No idea; apt's resolver is sometimes creative. Other examples include > [1], [2], [3]. > > [1]: > https://buildd.debian.org/status/logs.php?pkg=hplip&ver=3.20.6%2Bdfsg0-1&arch=amd64 > [2]: > https://buildd.debian.org/status/logs.php?pkg=gnome-applets&ver=3.37.2-1&arch=amd64 > [3]: > https://buildd.debian.org/status/logs.php?pkg=kopete&ver=4%3A20.04.1-1&arch=amd64
Thanks. I have looked through these and, again, I can see no other regerences to either elogind or systemd that might explain this. However, all 4 examples you have given relate to builds for experimental. Is that always the case? If so, I wonder if this is related to the presence in experimental of libpam-elogind-compat? Mark
