[Pkg-xen-devel] Bug#710650: Bug#718767: transition: ocaml 4.00.1

Stéphane Glondu glondu at debian.org
Tue Sep 10 07:17:42 UTC 2013


Le 06/09/2013 10:14, Thomas Goirand a écrit :
> I wrote it many time to many people. Please don't just read 1.6 as "new
> upstream release" for XCP. That's unfortunately not the way it works.
> Upstream version for Debian and the one they do for CentOS are
> different, and just using upstream 1.6 doesn't cut it. It needs to be
> ported to Debian, and that's far from a trivial work (as Michael Tokarev
> wrote, it's not "just replacing /usr/libexec/ into /usr/lib/ and the like").

That is not the way it should work. Upstream version should not be
specific to either Debian or CentOS. There should be only one version,
and it is the job of each distribution (yours, here) to do the
specialization work. If you can't, then arrange for its removal from
testing.

> However, as I wrote it, it's going to happen, so please be patient about
> it. IMO, this shouldn't block any transition though. If the release team
> is reading: just let everything transition to testing, and remove the
> old version of XCP 1.3.2 in testing if that helps, plus add some
> blocking bugs so that the rest of Debian isn't affected by the (not
> finished) work on XCP 1.6 for Debian.

There are reverse-dependencies so it cannot be easily removed from
testing. And this situation IS blocking other people's work. And has
been for (at least) one month.

> No, the package isn't neglected. It's simply more complicated than it
> seems. I'm currently dealing with upstream about it.

While doing so, please make sure future versions are trivial to port to
Debian. It should have been done during the initial packaging.

> I by the way don't mind if 1.3.2 is removed from testing, as we will
> need to package the next version anyway.

Then, could you give the list of packages that should be removed from
testing? Remember, testing should be self-contained, so it means remove
all reverse dependencies as well.

>> There are a few reverse-dependencies, but they all look somehow
>> connected: nova, guest-templates, xcp-*... My take would be to remove
>> (from testing) all of them.
> 
> The problem for Nova is different. It's depending on sqlalchemy-migrate
> (python-migrate in Debian), which is blocked by Alembic, AFAIK. As for
> guest-templates, I don't see why it is affected.

guest-templates build-depends on libxenapi-ocaml-dev, which is built by
xen-api.

> I hope the above helps,

And nothing has changed since...


Cheers,

-- 
Stéphane



More information about the Pkg-xen-devel mailing list