Bug#746577: closed by Michael Biebl <biebl at debian.org> (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)

[Tollef Fog Heen]

]] Zack Weinberg 

> On 2014-05-03 12:18 PM, Tollef Fog Heen wrote:
> > Zack Weinberg wrote:
> >> 1) Switching from sysvinit to systemd (and vice versa, if necessary)
> >> should be accomplished via a command dedicated to the purpose; it
> >> should *not* occur as a side effect of installing, removing,
> >> upgrading, or downgrading any package.
> >
> > So you say.  I (with my systemd maintainer hat on) disagrees, and this
> > has already been in wheezy and works quite well.
> >
> >> 2) The procedure I described should be the official procedure for
> >> making the changeover.
> >
> > Again, you say so, but provide no rationale or reason why.
> 
> Fundamentally what I want is a bulletproof procedure for reverting to
> sysvinit in case something goes wrong.  I made an analogy earlier to
> how upgrading to a newer upstream kernel (with Debian's packaging)
> keeps the old kernel installed and trivially bootable, in case
> something goes wrong.  This is not because the kernel maintainers know
> of specific situations where something *will* go wrong; it is because
> there is a nontrivial chance that something *could* go wrong, and in
> the worst case that will render the system unbootable.

Sounds like you're arguing that sysvinit-core should no longer ship
/sbin/init, then, so systemd-sysv doesn't have to conflict with it.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are