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

[Ansgar <ansgar@debian.org>]

On Wed, 2020-07-08 at 11:04 +0200, Johannes Schauer wrote:
> What is happening here is, that aspcud chooses libelogind0 for installation and
> then apt decides that it refuses to install it because it doesn't want to
> remove libsystemd0 in favor of libelogind0 and by that replace an important
> package (apt would require the "yes, do as I say!" thing for that to work).

libsystemd0 doesn't seem special though?  It's `Priority: optional` and
doesn't have much else; I guess trying to uninstall libsystemd0 breaks
something else?

I'm not really motivated to debug problems caused by elogind though.

> But instead of re-assigning this to apt for ignoring part of the installation
> request by apt-cudf, maybe we can solve this differently.
> 
> Ansgar, can you tell me which preferences you pass for experimental
> installations on the buildds?

I don't know what buildds use, but I could reproduce the problem
locally with sbuild without setting anything special.

Ansgar