Bug#748355: Upgrading from sysvinit/wheezy to systemd-sysv/sid impossible due to loop

Steve Langasek vorlon at debian.org
Mon May 19 05:10:46 BST 2014


On Fri, May 16, 2014 at 06:53:27PM +0200, Sven Joachim wrote:
> On 2014-05-16 17:33 +0200, Michael Biebl wrote:

> > Incidentally we also discussed dropping the Conflicts from systemd-sysv
> > and only keeping the Replaces (and this is also what sysvinit-core has
> > done).

> Which has its own problems, since nothing stops the admin from shooting
> themselves in the foot by installing sysvinit-core without upgrading
> sysvinit and then removing sysvinit-core.

Stopping admins from shooting themselves in the foot by running a stupid
sequence of apt commands without understanding what they're doing, should
not be given higher precedence than ensuring that the vast majority of our
users are able to cleanly upgrade by following our standard upgrade
instructions.

So yes, it's a downside that this is possible when using the Replaces
without Breaks or Conflicts, but it's definitely a lesser evil.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140518/dcaa1d9a/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list