Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]
Ondřej Surý, le Tue 09 Sep 2014 13:10:48 +0200, a écrit :
> On Tue, Sep 9, 2014, at 11:54, Samuel Thibault wrote:
> > Ondřej Surý, le Tue 09 Sep 2014 11:47:38 +0200, a écrit :
> > > And you are saying that you can do all those tweaks, but you cannot
> > > pin systemd-sysv to not install?
> >
> > No, I'm saying that if I hadn't noticed "systemd" among the upgrades, I
> > would have gotten all these changes all of a sudden without asking for
> > them. That can be pretty bad for the serial console access.
>
> Also broken libdb upgrade in hamm (I think) broke my system beyond
> repair... It's testing (and unstable), it's expected to have some
> undocumented breakages. That's the sole reason to have the testing
> and unstable in first place. To find the problems, fix them and if
> that's
> not possible (for various reasons[*]) then we should document that
> in the release notes.
Sure. But I don't ever see us discovering all problems and fix them with
just the freeze period.
> > And I'm saying that I don't think this is an isolated case,
>
> And I'm saying that all we have is anecdotal evidence and we all
> know what we step into when we run our systems on jessie or sid.
> So please fill a bug for every breakage you will encounter, so it
> can be either fixed or documented.
There will be dozens of them then. Will they really be fixed in time for
Jessie?
> > I believe most our users prefer to stay with sysvinit when upgrading from wheezy
>
> And I believe that most our users don't care.
I believe most of our users care about an upgrade to Jessie that doesn't
bring regressions.
When we upgraded from grub1 to grub2, we have let the users decide when
they actually do the switch, so they can handle it independently from
the system upgrade. Why not doing the same here?
Samuel
Reply to: