Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Mark Hindley mark at hindley.org.uk
Sat Sep 21 10:21:48 BST 2019


On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
> Hello,
> When I looked I elogind a while back I was able to build a package without
> having a public libelogind0, I basically had that in my debian/rules file:
> # We only build the libelogind0 and libelogind-dev if we are building for
> # Devuan or its derivatives
> ifneq ($(shell dpkg-vendor --derives-from Devuan && yes), yes)
> export DH_OPTIONS=--no-package=libelogind0 --no-package=libelogind-dev
> endif

I have just tested this approach. The build and install seems OK. However,
applications using the sd-*(3) APIs through libsystemd.so (most notably
src:polickit-1) fail to match pids to sessions despite the session being
registered correctly with elogind.

Normal functionality is restored by installing libelogind0 and restarting



More information about the Debian-init-diversity mailing list