Sync simgear 3.4.0-0~exp1 from Debian git, flightgear 3.4.0-0~exp1, flightgear-data 3.4.0+dfsg-0~exp1, fgrun 3.4.0-0~exp1 (universe) from Debian experimental (main)

Preparing to unpack .../libsimgearscene3.2.0-dbg_3.2.0-1~exp1_amd64.deb ...
Unpacking libsimgearscene3.2.0-dbg:amd64 (3.2.0-1~exp1) over (3.2.0-1~exp1) ...
dpkg: dependency problems prevent configuration of libsimgearscene3.2.0:amd64:
 libsimgearscene3.2.0:amd64 depends on libopenscenegraph100; however:
  Package libopenscenegraph100 is not installed.
 libsimgearscene3.2.0:amd64 depends on libopenthreads20; however:
  Package libopenthreads20 is not installed.

dpkg: error processing package libsimgearscene3.2.0:amd64 (--install):
 dependency problems - leaving unconfigured
Setting up libsimgearscene3.2.0-dbg:amd64 (3.2.0-1~exp1) ...
Errors were encountered while processing:
 libsimgearscene3.2.0:amd64

That's not the version of simgear I asked for: we're skipping over 3.2 and going straight to 3.4, but due to NEW queue delays this is only in Debian git, not Debian main archive.

The install failure looks like you built it on a system with -proposed enabled then tried to install it with -proposed disabled, which failed because openscenegraph is currently changing soname (https://launchpad.net/ubuntu/+source/openscenegraph). When we did that transition in Debian it was a straightforward rebuild, but on Ubuntu it appears to be blocked by libcitygml being broken ( http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html https://launchpad.net/ubuntu/+source/libcitygml/0.14+svn134-1+3p2p0ubuntu1 ).

Ok, thanks.

The libcitygml breakage has already been fixed in Debian (as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763047 ), so syncing that package and rebuilding openscenegraph's other dependencies should fix that problem.

Discussion of fixing this in bug 1368801.

Looks like syncing it is not enough.

simgear is in Debian NEW queue, but I built from the git and found out there's an armhf build failure at least:

https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta1/+packages
https://launchpadlibrarian.net/198121382/buildlog_ubuntu-vivid-armhf.simgear_3.4.0-0ubuntu1_FAILEDTOBUILD.txt.gz
---
/build/buildd/simgear-3.4.0/simgear/canvas/ODGauge.cxx: In member function 'void simgear::canvas::ODGauge::allocRT(osg::NodeCallback*)':
/build/buildd/simgear-3.4.0/simgear/canvas/ODGauge.cxx:239:23: error: 'GL_FOG' was not declared in this scope
     stateSet->setMode(GL_FOG, osg::StateAttribute::OFF);
---

This would need a fix. I (Mirv on IRC) can help with test builds of the fix if not otherwise possible. When fixed, please follow the FFE process (https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_Exceptions) since obviously this all probably won't be resolved during today before Feature Freeze.

It's known that simgear won't build on Ubuntu armhf because simgear makes direct OpenGL calls, whereas OpenGL ES is used instead on armhf. I was able to make OpenSceneGraph build on Ubuntu armhf, but because of the direct OpenGL calls here, more work would need to be done here.

Oh, actually, it's _not_ a regression https://launchpad.net/ubuntu/+source/simgear/3.0.0-6 + https://launchpad.net/ubuntu/+source/flightgear/3.0.0-4 - so not necessarily a problem.

I upgraded to the PPA 3.4.0 packages without problems on vivid, and Flight Gear also works fine. I'm not sure how the libcitygml is related now to the Flight Gear 3.4, but I can't see any problems on my computer.

I've now uploaded simgear and synced the rest:
https://launchpad.net/ubuntu/+source/simgear/3.4.0-0ubuntu1
https://launchpad.net/ubuntu/+source/flightgear/3.4.0-0~exp1
https://launchpad.net/ubuntu/+source/flightgear-data/3.4.0+dfsg-0~exp1
https://launchpad.net/ubuntu/+source/fgrun/3.4.0-0~exp1

Thanks.

The connection to libcitygml is that libopenscenegraph100 and all its dependencies (including ones that are themselves OK, such as these packages) can't leave -proposed yet, because doing so would break the old libcitygml: https://wiki.ubuntu.com/ProposedMigration

I have posted some suggestions in bug 1368801, but can't reproduce the bug to test them.

All of the openscenegraph 3.2.1 transition is now complete. Thank you to everyone working on it!