Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

[Thorsten Glaser]

On Thu, 15 Aug 2019, Mark Hindley wrote:

> I am now wondering if the prime responsibliity for the system breakage here is
> down to apt's behaviour.
[…]
> At this point apt has failed to remove systemd/241-7 which depends on libsystemd
> (=241-7). Surely it should not then go on to try and remove the systemd
> dependency?

Unsure if that’s apt or dpkg. Plus, the failing prerm is in systemd,
not in libsystemd0.

For dpkg, it makes sense to remove libsystemd0 nevertheless, when
called literally; for apt, it doesn’t. (Interestingly enough,
the dpkg developer has been telling the apt developers for ages
that dpkg now can handle this kind of dependencies, and not to
use the “do what I said and ignore dependencies” mode any more.)

It does make sense to bring the developers of both apt and dpkg
into this, irrelevant of where an improvement can be done, unless
my beer-induced idea I already posted works.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**********

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**********