Recent systemd stretch backport breaks sysvinit

[Ben Hutchings]

On Fri, 2018-10-12 at 23:47 -0400, Chris Ruvolo wrote:
> On Sat, Oct 13, 2018 at 03:38:18AM +0100, Ben Hutchings wrote:
> > While backporters must ensure that the dependencies of backported
> > packages can be met in stable+backports, there is no requirement that
> > they must be coinstallable with all the same packages as the version in
> > stable.
> 
> Hi Ben, thanks for the reply.
> 
> This seems odd to me.  It is changing requirements for a pretty fundamental
> part of the distribution.  It violates my expectations for what is allowed
> in backports.  Perhaps that expectation is not correct, however.
> 
> > systemd-shim is not present in testing and will probably not be in the
> > next release.  So you should either help to fix the RC bugs in systemd-
> > shim or prepare to use systemd as pid 1 wherever you need to run other
> > systemd daemons.
> 
> Has policy changed regarding support for multiple inits, or is it just that
> no one is maintaining the shim and sysvinit-core?

The latter.  systemd-shim has been orphaned for over 2 years, and has
RC bugs.   sysvinit currently has two maintainers, but they've only
ever made one upload (over a year ago).

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181013/4f7662a9/attachment-0002.sig>