Bug#784604: systemd: can't remove systemd unless it is correctly running

[Brian May]

On Sat, 9 May 2015 at 21:21 Michael Biebl <biebl at debian.org> wrote:


> > Guessing this would have to be done for every package  from postrm, prerm
> > scripts however :-(
>
> Why? If your system is in such a (broken) state, is there a need to
> install/uninstall server packages? They wouldn't be really useful anyway.
>
> If I understood you correctly, all you want to do is switch back to
> sysvinit in such a case where. Allowing to uninstall systemd-sysv
> cleanly should be sufficient for that.
>

Yes, correct.

However, in a previous email to this bug report I posted the output of
"apt-get remove systemd" where it tried to remove packages like colord and
hplip, which failed, even before it got to the step of trying to remove
systemd. The result was a totally broken system, where the only resolution
given was to reinstall the packages it just removed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150509/f3115d18/attachment-0002.html>