[pkg-fgfs-crew] flightgear 3.2 packaging...or not?

[Rebecca Palmer]

Upstream have fixed the SGPropertyNode::fireValueChanged crash, but are 
now seeing several other crashes: one looks like a known openscenegraph 
bug (fixed in upstream openscenegraph but not Debian openscenegraph), 
another looks like potentially hard-to-trace memory corruption.

Furthermore, it now appears that the "no transitions at this time" rule 
applies even to transitions within a single maintainer's packages 
(https://lists.debian.org/debian-release/2014/10/msg00086.html), so we 
may not now be allowed to upload 3.2 even if it does get into a state 
where we'd want to.

Hence, I suggest another upload *of 3.0* with the following (already 
existing) patches:

simgear (do this first):
#761203 fix endianness on mipsel, add arm64
#763493 change build dependency to libjpeg-dev (libjpeg-turbo transition)

flightgear:
#763470 change build dependency to libjpeg-dev (libjpeg-turbo transition)
change simgear dependency to >=3.0.0-5~ (as the fix for #761203 is in 
the headers; the ~ is to allow backports)

fgrun:
#757178 fix environment variable export

I hope to look at #750939 (hang) and LP#1301492 (crash) before the 
freeze, but given that we need to upload something soon for the 
libjpeg-turbo transition anyway, we may as well fix everything we 
currently can in that upload.