Bug#940681: elogind: Should only build-depend on libseccomp-dev on architectures supporting it

Mark Hindley mark at hindley.org.uk
Thu Sep 19 04:52:44 BST 2019

Control: tags -1 pending


On Thu, Sep 19, 2019 at 01:13:20AM +0200, John Paul Adrian Glaubitz wrote:
> Source: elogind
> Severity: normal
> Hello!
> Currently, elogind unconditionally build-depends on libseccomp-dev despite the fact
> that not all supported architectures in Debian currently support libseccomp [1].
> This results elogind being BD-Uninstallable on a couple of architectures [2] where
> the original systemd code builds fine [3].
> Thus, could you modify your debian/control such that it adopts what systemd does
> in this regard and if necessary make the necessary changes to elogind so it can
> be built on architectures without libseccomp support?

Thanks for the pointer on this.

Yes, happily.

I have made the changes in git and it will be in the next upload.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20190919/9273155a/attachment.sig>

More information about the Debian-init-diversity mailing list