Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)

Ansgar ansgar at debian.org
Thu Jul 2 13:29:40 BST 2020

Control: tag -1 - moreinfo

On Thu, 2020-07-02 at 12:58 +0100, Mark Hindley wrote:
> On Wed, Jul 01, 2020 at 12:35:18PM +0200, Axel Beckert wrote:
> > Is it still the case that the buildds use aptitude for resolving
> > dependencies on experimental builds? Because aptitude might be even
> > more "creative" than apt in that regards.

They use a different resolver as indicated in the log.  There are other
small differences too between unstable and experimental (or backports
which has similar differences IIRC).

> Thanks. That is one for Angar.
> It seems possible that the presence of libpam-elogind-compat in experimental
> makes aptitude and/or apt try an invalid solution.

No; at least adding a build-conflict on libpam-elogind-compat doesn't
change the result.

Adding a build-conflict on elogind or libpam-elogind instead of
libelogind0 works too (as least with "kopete"; did only test that one
package), so the problem might also be the `Provides: logind` in


More information about the Debian-init-diversity mailing list