Bug#727708: systemd jessie -> jessie+1 upgrade problems
Hi Uorti,
Le mercredi 18 décembre 2013 à 15:10 +0200, Uoti Urpala a écrit :
> I don't think anyone said that. Nobody talked about long release cycles
> not being supported, and nobody said that upgrades would not be
> supported either. However, "supporting upgrade from the old release"
> does not equal things like being able to run the new userland on the 3+
> year old kernel from the previous release.
>
> A development model where you have to wait 3+ years before you can have
> hard dependencies on the new features you write now is obviously very
> problematic. IMO such restraints should never be taken for granted;
> upgrade schemes should always be planned to at least make it possible to
> have newer dependencies without too much trouble.
Such stances are untenable whenever the kernel is concerned. We need to
be able to use a kernel from the previous stable distribution, or from
the next one, to support proper chroots. This part of the support for
upgrades is needed for our own infrastructure as well as for many of our
users.
It is possible to handle the situation with udev or with systemd,
because they do not make sense in a chroot environment, but they are the
exception, not the rule. And unless things go hectic, we *will* be able
to treat them normally and provide an upgrade path that doesn’t force
users to do locked upgrades.
All of this looks very far away from the init system discussion,
though.
--
.''`. Josselin Mouette
: :' :
`. `'
`-
Reply to: