Mark,

thank you for your response.

Yes, documenting build instructions wherever those are different from
Debian's would be great!

Still, could you comment on how (in)compatible libsystemd-dev and
libelogind-dev are?

Looking at the content of the binary packages, both contain almost the
same set of headers.
Is there any chance one will "virtually" provide the other?

Regards,
Andrey.

On Thu, 30 Apr 2020 at 11:50, Mark Hindley <mark@???> wrote:
>
> As you have discovered, building directly on the host system does not
> work if the system uses elogind and the package has a build dependency
> on libsystemd-dev. However, it will work fine in a build chroot. Try
> using pbuilder and the pbdebuild command and/or cowbuilder.
> There are also other options that should work, but I have not used
> myself, like qemu-builder and sbuild.
>
> Changing all the libsystemd-dev dependencies present in Debian would
> require forking about 200 additional packages and is not feasible at the
> moment.
>
> However, we ought to add this build technique to the release notes so
> that users know that plain debuild will not work on an elogind system if
> the package has libsystemd-dev build dependency.