[Pkg-sysvinit-devel] A wish for help with Bug#765803 On automatic init system switching on upgrade
tg at mirbsd.de
Fri Nov 21 20:20:40 UTC 2014
Petter Reinholdtsen dixit:
>That is correct. But one can change the behaviour of future
>installations after asking and then interrupting the upgrade and
>requiring a new upgrade. Not the best user experience, but it might be
No, no, no, no, no! Absolutely not.
If you abort in such a script, the user has to manually play
around with dpkg-reconfigure, dpkg --remove or --purge, and
apt-get -f install, which will in some cases fail to DWYW,
or even remove half the system.
>Check in the config script which boot system is being used, and if it is
>sysvinit, ask if it is ok to switch to systemd. If the answer is no,
>write a file /etc/apt/preferences.d/no-systemd with the content
No, too late.
>abort the upgrade
Absolutely not, see above.
>Definitely not a good user experience, but perhaps that can be improved?
I’d classify it as catastrophic fail. It is probably actually better
to let apt continue to temporarily install systemd and then have the
user remove that later.
“The final straw, to be honest, was probably my amazement at the volume of
petty, peevish whingeing certain of your peers are prone to dish out on
-devel, telling each other how to talk more like a pretty princess, as though
they were performing some kind of public service.” (someone to me, privately)
More information about the Pkg-sysvinit-devel