[Pkg-systemd-maintainers] Bug#726763: Bug#727708: systemd-shim uploaded to NEW

[Steve Langasek]

On Mon, Dec 30, 2013 at 09:52:37PM +0100, Tollef Fog Heen wrote:
> ]] Ian Jackson 

> > Steve Langasek writes ("Bug#727708: systemd-shim uploaded to NEW"):
> > > So I repeat here my request that the systemd maintainers make a suitable
> > > split of the systemd binary package, so that systemd-shim will be
> > > coinstallable with the systemd-provided implementations of the other dbus
> > > services.

> > Is there a summary of the systemd maintainers' response to this
> > request ?  I glanced #726763 and #729576 but they were very long and
> > if the answer is in there I probably wouldn't have found it.

> I see no point in doing that, in particular not in the middle of when
> the ctte is choosing a new default init system.  If anything, I think
> it's pretty rude of Steve to upload systemd-shim and asking the systemd
> maintainers to solve the problem for him.

Conversely, I think it's rude of everyone involved in having created this
bug to be pointing fingers at each other and disclaiming all responsibility
for fixing it, while in the meantime users of unstable are being left with
silently broken desktops on upgrades.  Even if Debian ultimately decides for
systemd, that doesn't do the least bit of good for users who suddenly find
suspend not working on their systems right now.

> > >  The only alternative I see is for systemd-shim to declare a
> > > Replaces: against systemd without a Conflicts,

> > This would be quite wrong; Replaces is not supposed to be used like
> > that (but you apparently know that).

> > How do the systemd maintainers think this problem should be solved ?

> Initially, by waiting for the ctte to come to a conclusion.  If that is
> that systemd should be the default init system I think we should solve
> the problem by not solving it.  If the decision is that another init
> system should be solved, I'm probably going to solve it by removing the
> init functionality from the systemd package at which point the bug
> solves itself, AIUI.

> If the systemd-shim maintainers want to solve it in the meantime, going
> with Raphael's suggestion seems reasonable enough.

So given that dpkg-divert can't be used for the conffile, is this still your
position?  This means that divert+Replaces is the only other option, which
will result in the conffile being removed if systemd-shim is installed and
then purged.

-- 
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: 853 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20131231/e23e6a80/attachment-0008.sig>