Devuan bug report logs - #435
Need to document techniques for building packages depending on libsystemd-dev

Package: libelogind0; Maintainer for libelogind0 is Mark Hindley <mark@hindley.org.uk>; Source for libelogind0 is src:elogind.

Reported by: andrewbass@gmail.com

Date: Wed, 29 Apr 2020 21:33:01 UTC

Severity: normal

Tags: ceres, chimaera, patch

Merged with 562, 574, 609

Fixed in version 243.8-1

Done: dak@devuan.org

Full log

Message #18 received at 435@bugs.devuan.org (full text, mbox, reply):

Received: (at 435) by bugs.devuan.org; 30 Apr 2020 13:10:04 +0000
Return-Path: <mark@hindley.org.uk>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Thu, 30 Apr 2020 13:10:03 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id DB4CAF60C4D
	for <435@bugs.devuan.org>; Thu, 30 Apr 2020 15:00:00 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1jU8nG-0005qg-K6; Thu, 30 Apr 2020 13:59:58 +0100
Received: (nullmailer pid 31847 invoked by uid 1000);
	Thu, 30 Apr 2020 12:59:58 -0000
Date: Thu, 30 Apr 2020 13:59:58 +0100
From: Mark Hindley <mark@hindley.org.uk>
To: Andrey ``Bass'' Shcheglov <andrewbass@gmail.com>
Cc: 435@bugs.devuan.org
Subject: Re: [vlc] Unable to build the vlc package as it requires
 libsystemd-dev
Message-ID: <20200430125958.GB32762@hindley.org.uk>
References: <20200430001911.09fc09ad@proxima.2ka.mipt.ru>
 <20200430085019.GA14953@hindley.org.uk>
 <CADSg1JjfqgXBZBL+1hYLwiRJvGbUkc0-ZsoLmDsS5BY9FSrzXQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADSg1JjfqgXBZBL+1hYLwiRJvGbUkc0-ZsoLmDsS5BY9FSrzXQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

On Thu, Apr 30, 2020 at 03:41:08PM +0300, Andrey ``Bass'' Shcheglov wrote:
> 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?

They are reasonably compatible from a compilation perspective. That is by
design.  However, Debian only compiles against libsystemd-dev and it is not
known whether all packages would compile against libelogind-dev without some
sort of patching in of explicit support. Certainly patching was required for
policykit-1, although those changes have now been accepted upstream.

> 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?

That is currently the case for libsystemd0/libelogind0 only at runtime. Doing
libelogind-dev provides libsystemd-dev concerns me as I think we might introduce
FTBFS until we know that all source packages will build with either. Given the
number of source packages in Debian, that is a lot of testing. Hence why we
currently follow Debian and only build against libsystemd-dev.

Does that make sense?

Mark

Send a report that this bug log contains spam.

Devuan bug report logs - #435 Need to document techniques for building packages depending on libsystemd-dev

Devuan bug report logs - #435
Need to document techniques for building packages depending on libsystemd-dev