On 1/23/22 21:43, Bernd Zeimetz wrote:
On Thu, 2022-01-20 at 00:12 +0100, Thorsten Glaser wrote:
Try to talk to upstream. Perhaps it’s possible to (at least locally
to the Debian packaging) support the extended upgrade path.
I think that was tried, just not sure what the outcome was.
I tried talking with Sage (who's kind of the lead in Ceph) during
FOSDEM in 2019, after his talk, and he seemed supportive, but said he
should raised the concern in the Ceph community. Perhaps it's worth
trying to raise the topic again in the Ceph devel list again.
(And incidentally, the Derivate-that-must-not-be-named
since their LTS releases also don’t permit skipping, come out at about
the same frequency as stable Debian releases, [....]
U* is one question, the other one is how RedHat is supporting Ceph
and how
their upgrade path looks. Although they are a bit more flexible I
guess as
they have their own ceph repositories and support ceph over different
releases.
Maybe Debian (finally) needs to add support for per-package
repositories,
too. Ceph is not the only part of Debian where something like that
would make
sense, although that discussion is not for this list.
Correct. And that's probably the path I will choose as well: yet
another unofficial Debian repository in the debian.net namespace, for
people to use as upgrade path. I'm doing this for OpenStack, maybe
there's no other choice for Ceph for the moment. It's IMO less nice
than using stable-backports, but no choice, if that's not allowed...
If not an idea solution, that's IMO a better choice than leaving
Debian users using a bitrotted version that's 2 releases behind.
Cheers,
Thomas Goirand (zigo)