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

Bug#706798: where is OpenSceneGraph 3.2 status?



Hi,

[not part of Release Team but hopefully I can answer your question]

On 04/10/13 09:32, Rebecca N. Palmer wrote:
> Is there a tracker for the OpenSceneGraph 3.2 transition (tied to this
> one by #720816)?  Status as far as I can find:

It doesn't look to me that a transition was coordinated for openscenegraph?

Status of openscenegraph's migration to testing is best shown by:
http://packages.qa.debian.org/o/openscenegraph.html
http://qa.debian.org/excuses.php?package=openscenegraph
http://release.debian.org/migration/testing.pl?package=openscenegraph

Blocking issues are #720816 which you already submitted a patch for, a
(possibly temporary) build issue on mips, and the fact openscenegraph
must be rebuilt anyway as part of the libav9 transition.

And then the rest of the libav9 transition needs to complete:
http://release.debian.org/transitions/html/libav9.html

The 'hurd' column can be ignored, as well as rows marked 'sid only'.
AIUI the packages at higher dependency levels (such as openscenegraph at
level 3) tend to sometimes need packages at lower levels (higher in the
list) to be rebuilt first.

AFAIK blockers are dvswitch, opencv, spek [on s390x], yorick-av, and vxl
[on ia64].  The BTS entry for #706798 notes these and some other things
as blocking bugs.

I don't see that #725071 in xine-lib-1.2 really blocks this as the
kfreebsd binaries are already built against newer libav9;  I submitted a
patch for that anyway.


> * #719402 fgrun (sid only) has patch
> * #719376 osgearth fixed in 2.4, but this is held in unstable because an
> unrelated upstream fix makes it non-kFreeBSD
> (https://github.com/gwaldron/osgearth/commit/a270f5f0e2c3d56f5d528db17873dc37c52a6655
> ; SYS_gettid doesn't exist there)

That's definitely not portable code, I'll look into that one.

> * #718381 / #719388 openwalnut badly broken by 3.2, being worked on
> upstream (latest upstream reported to build but not work properly,
> http://www.openwalnut.org/issues/298)

So these are all broken by openscenegraph going into sid?  I don't think
that will actually prevent openscenegraph from migrating to testing
automatically.  But perhaps a transition should have been requested for
it and a tracker set up.

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org


Reply to: