[Pkg-sysvinit-devel] Why is wheezy chroots switching to systemd on upgrades?

[Petter Reinholdtsen]

[James McCoy]
> See #746578 and #762194.
> 
> > Anyone got an idea why this happen?
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746578#61

Aha.  Thank you for the hint.  That seem like a bug that should be
fixed, given how many of the systemd sevices files that are not yet
working as they should.  The safe option for existing installations is
to keep sysvinit for jessie during upgrades, and try to make sure the
issues are fixed in time for jessie + 1.

Is there anything we can do on the sysvinit side to ensure upgrades
keep sysvinit while new installations get systemd?

It look like someone who have discussed the topic on a mailing list a
rarely read (debian-devel@) concluded that upgrades should switch to
systemd.  I am not conviced that is a good way to conclude in this
matter, and wonder if we should consult the technical committee to
check if this is what they intended.

-- 
Happy hacking
Petter Reinholdtsen