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

Adam Borowski kilobyte at angband.pl
Sat Sep 28 22:44:15 BST 2019

On Sat, Sep 28, 2019 at 02:53:56AM +0200, Thorsten Glaser wrote:
> 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?

That's for when you're knowingly doing something very unusual, that in
normal circumstances breaks your whole system.

Using a different supported init system is not something that counts here.

> 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.

You might be comfortable with overriding all safety barriers, but that's not
something for regular users.

⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄⠀⠀⠀⠀ etc), let the drink age at least 3-6 months.

More information about the Debian-init-diversity mailing list