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

[Axel Beckert]

Hi,

Mark Hindley wrote:
> > > I am struggling to understand how libelogind0 came to be installed in the build
> > > in the first place. Can you help me understand that?
> > 
> > No idea; apt's resolver is sometimes creative.  Other examples include
> > [1], [2], [3].
> > 
> >   [1]: https://buildd.debian.org/status/logs.php?pkg=hplip&ver=3.20.6%2Bdfsg0-1&arch=amd64
> >   [2]: https://buildd.debian.org/status/logs.php?pkg=gnome-applets&ver=3.37.2-1&arch=amd64
> >   [3]: https://buildd.debian.org/status/logs.php?pkg=kopete&ver=4%3A20.04.1-1&arch=amd64
> 
> Thanks. I have looked through these and, again, I can see no other regerences to
> either elogind or systemd that might explain this.
> 
> However, all 4 examples you have given relate to builds for
> experimental.


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.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE