[pkg-fgfs-crew] Preparing for flightgear 3.6

[Rebecca N. Palmer]

> Thanks for the heads up. I recently uploaded simgear-3.6 and it passed
> NEW pretty quickly.
>
> However, I'm AFK until Aug 13th, and pretty busy afterward. So it's
> going to be pretty tight, again.

We're also caught in the huge gcc5/libstdc++ transition, so are not 
allowed to upload to unstable, but can upload to experimental and have 
Ubuntu sync from there.  (Ubuntu freeze works on upload date, not 
build/migration-from-proposed date, so it doesn't matter that we're 
currently BD-Uninstallable.)

I'll have a look at #793517 and fgdata's new dependencies.

> I'd really like to split at least the NASAL code - preferably the other
> aircrafts as well - so a bug- or security fix wouldn't consume that much
> bandwidth, anymore. To be effective, that means splitting fg-data into
> multiple source packages, I think. Which in turn would require going
> through NEW, again...
Yes, and source-NEW is often slower than binary-NEW.

(From 3.6, security is meant to be done entirely C++ side, but other 
bugs are still possible.

This would cease to be an issue if the source-only upload infrastructure 
is ever finished (new Debian revisions don't require a new .orig.*, the 
big part is the arch:all binaries), but I don't know if/when that's 
expected.)