On 22 Sep 2013, at 22:06, Markus Wanner mar...@bluegap.ch wrote:
standard checking procedures on Debian revealed a spelling error:
compatability occurs a couple of times in the sources.
I'm a bit worried about the kt70-compatibility boolean flag, but
corrected its spelling for the Debian
On Sun, 22 Sep 2013, Markus Wanner wrote:
Hi,
standard checking procedures on Debian revealed a spelling error:
compatability occurs a couple of times in the sources.
I'm a bit worried about the kt70-compatibility boolean flag, but
corrected its spelling for the Debian release.
Attached
Anders,
On 09/23/2013 10:10 AM, Anders Gidenstam wrote:
Very good, except that one of the instances corrected is the name of a
property tree node. Hence, fgdata is a dependency that may be
affected too and needs to be checked.
Of course, I did a quick grep in the 2.12 fgdata, but didn't
On 23 Sep 2013, at 10:18, Markus Wanner mar...@bluegap.ch wrote:
Of course, I did a quick grep in the 2.12 fgdata, but didn't find
anything relevant. (Navaids/ReadMe.FG226.txt was the only hit.)
The affected aircraft isn't in the base package, but /is/ in fgdata Git. So
wearing the 'Debian
On 09/23/2013 11:27 AM, James Turner wrote:
The affected aircraft isn't in the base package, but /is/ in fgdata Git.
So wearing the 'Debian maintainer' hat you did the right thing, but from
the terms of flightgear patches, we check /all/ aircraft, not just those
included in the base package.
On 23 Sep 2013, at 10:46, Markus Wanner mar...@bluegap.ch wrote:
On 09/23/2013 11:27 AM, James Turner wrote:
The affected aircraft isn't in the base package, but /is/ in fgdata Git.
So wearing the 'Debian maintainer' hat you did the right thing, but from
the terms of flightgear patches, we
Any other aircraft that users might download which would fail if I patch
this one as well?
There may be aircraft outside official fgdata that need editing. Given that
we've
changed the property in-between releases, it would be good to mention it at
On 09/23/2013 11:58 AM, James Turner wrote:
Actually, I spoke too soon - the ZLT-NT /is/ in the base package. I just
check the official FLightGear-2.12.0 tar.bz and the ZLT-NT is there
(good) and the reference to kt70-compatability is also there. So I'd
suggest to check your files or workflow
On 23 Sep 2013, at 16:49, Markus Wanner mar...@bluegap.ch wrote:
Any other aircraft that users might download which would fail if I patch
this one as well?
Given that 2.12.0 was released with compatability, are you going to
change this for a potential 2.12.1 or for 3.0?
I'd prefer to
Markus,
It's now fixed in next branch ;-)
https://gitorious.org/fg/flightgear/commit/023c136d40cab24d994d29f2cd05e812ec3a8670
Thanks you
Regards,
Clément --
LIMITED TIME SALE -
10 matches
Mail list logo
