Bug#765803: Status of prompting / notification on upgrade for init system switch?
On Mon, 20 Oct 2014 10:06:31 -0400 Martin Pitt <mpitt@debian.org> wrote:
> I'll leave this to the Debian maintainers, as I'm mostly responsible
> for the Ubuntu side, haven't really discussed this with the two
> Michaels/Tollef/Marco, and I don't feel qualified to speak for the
> Debian systemd team.
>
> My personal opinion: Given how close we are to the release and how
> many regression reports we still get, it seems prudent to not change
> the currently running init systems for upgrades for Jessie yet, but
> only set up systemd for new installs. I know this is not really in the
> spirit of the TC decision to make systemd the default init system, but
> at this point in time it might be the pragmatic compromise.
>
> The systemd package gets literally swamped with bug reports (of all
> kinds of usefulness/quality), and there's simply not enough
> maintainers to keep up with the flood. Many of those are indeed not
> actual bugs in systemd, but bugs in other packages, local
That "swamped with bug reports" does not match my impression of reading
the systemd packaging list. As far as I can tell, this is not the view
of the Debian maintainers either.
My impression from the bug reports is that systemd-shim does not work
particularly reliably. So automatically installing systemd-shim does not
seem any safer than automatically installing systemd from the view of
avoiding breaking old systems.
> The other direction (running sysvinit or upstart with -shim) has not
> been so unproblematic though, as systemd-shim's bug list shows. This
> definitively needs some love, but then again we've run this for a fair
> while in Ubuntu (even in our 14.04 LTS) without too many problems. So
> my feeling is that we can certainly stabilize -shim by the jessie
> release. (We need to do that anyway, as we need to support sysvinit
> regardless of what we do on upgrades/new installs.)
Is there some reason to believe that there would be _more_ success with
this than with resolving the remaining integration issues with systemd?
And shouldn't work on the latter be higher priority?
Reply to: