Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Thorsten Glaser t.glaser at tarent.de
Sat Sep 28 01:53:56 BST 2019

On Fri, 27 Sep 2019, Mark Hindley wrote:

> Thanks. The aim of preventing accidental removal of systemd is very
> reasonable. However, using this approach the hurdle you create even to a user
> who really wants to uninstall is pretty high. Few people will continue having
> seen the 'You are about to do something potentially harmful' warning.

And isn’t that precisely the goal? To prevent most users from
“just hitting Enter” to switch away from the default?

I’d assume people wanting to install elogind to proceed
according to documentation telling them that this message
is expected (but to still review what APT wants to do!)
(or just have enough of a clue about Debian to do this
anyway) so this is what I’d suggested, independent even
of the rest of the discussion.

«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”	(#nosec)    ‣‣‣ Please let MySQL and MariaDB finally die!

More information about the Debian-init-diversity mailing list