[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#718767: Bug#710650: Bug#718767: transition: ocaml 4.00.1



06.09.2013 10:42, Stéphane Glondu write:
[]
Now, xen-api FTBFS because of what looks like an API change in some (C)
dependency:
[]
On the other hand, there is a new upstream release (upstream version is
1.6 and unstable version is 1.3.2). It doesn't make sense to me to
invest time in this without updating the package, which goes beyond the
scope of an NMU. Fixing #713349 was already borderline since there is
also a new upstream release there... but it was easy.

The FTBFS bug has been reported in June. I told some of the maintainers
(in-person, in CC) to update this package during debconf. No activity
since them. IMHO, this package is neglected and should be removed from
testing.

The situation with xen-api, as far as I can see from my non-maintainer
not xen-related view - is quite a bit difficult.

The upstream is very much redhat-specific, and they "ported" the previous
version "to debian", which required quite some work.  I don't know the
details there, but I looked briefly at the git diff between "redhat"
and "deboan" versions - it was quite large and didn't end up just
replacing /usr/libexec/ into /usr/lib/ and the like.

Now, it looks like similar "porting" effort is needed to "port" the
new upstream version.  Which no one want to do, apparently... ;)

That's the reason - again, as far as I can see - why the inactivity
is happening.

I tried to do something with it because xen-api stops qemu migration
and users are asking about it quite often.  But I don't know anything
about either xen or ocaml or other related stuff, and especially
with this "porting" stuff, it looks like I'm not the right candidate
to sort it out.

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.

I'd vote for the same, but again, I'm not a user of any of these,
so it's easy for me... ;)

Thanks,

/mjt


Reply to: