Bug 26053 - Bring flightgear 2019.1.2 to mageia 7
Summary: Bring flightgear 2019.1.2 to mageia 7
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Reported: 2020-01-11 16:26 CET by José Jorge
Modified: 2020-01-19 11:12 CET (History)
5 users (show)

See Also:
Source RPM: flightgear
Status comment:


Description José Jorge 2020-01-11 16:26:27 CET
Flightgear has released version 2019.1.2. We provide it as an update as this is an online played simulation.
Comment 1 José Jorge 2020-01-11 17:05:48 CET
Suggested advisory :

Flightgear project tries to provide quarterly updates. This 2019.1.2 version brings as usual lots of fixes and improvements. Note that this is an x86_64 only application.




Assignee: lists.jjorge => qa-bugs
CC: (none) => lists.jjorge

Comment 2 Barry Jackson 2020-01-11 23:43:53 CET
Mga6 is EOL

CC: (none) => zen25000

Comment 3 José Jorge 2020-01-12 14:26:44 CET
(In reply to Barry Jackson from comment #2)
> Mga6 is EOL

Sorry, I forgot to change mga6 to mga7 when copying RPMS list from a previous bug report. It is of course mageia 7 versions.

I tested it in my family system, all seems ok.

Whiteboard: (none) => MGA7-64-OK

Comment 4 José Jorge 2020-01-12 14:27:19 CET
Marking 32 bits test as done, as there is no 32 bits version of this package.

Whiteboard: MGA7-64-OK => MGA7-64-OK MGA7-32-OK

Comment 5 Thomas Backlund 2020-01-13 17:24:41 CET
(In reply to José Jorge from comment #3)
> (In reply to Barry Jackson from comment #2)
> > Mga6 is EOL
> Sorry, I forgot to change mga6 to mga7 when copying RPMS list from a
> previous bug report. It is of course mageia 7 versions.

and got it wrong .... the real Srpms are:

So what's up with the "0" as release?

(In reply to José Jorge from comment #4)
> Marking 32 bits test as done, as there is no 32 bits version of this package.

If its only 64bit, it cant be ok on 32bit, now can it :)

Keywords: (none) => advisory, validated_update
CC: (none) => tmb, sysadmin-bugs
Whiteboard: MGA7-64-OK MGA7-32-OK => MGA7-64-OK

Thomas Backlund 2020-01-13 17:25:45 CET

Keywords: advisory, validated_update => (none)

Comment 6 Thomas Andrews 2020-01-17 03:08:12 CET
AMD Phenom II X4 910, 8GB RAM, Radeon HD 8490 graphics, 64-bit Plasma system.

After using gparted to make my / partition big enough to hold it, I installed the current version of Flightgear (plus dependencies) and played with it a little. I don't have a joystick, so my experience was limited, but I was able to move some cockpit buttons and switches around.

Then I used the QA Repo tool with "*gear*" as the rpm list. This brought in flightgear, flightgear-data, and simgear, as described in Comment 5, plus two more library dependencies. I then ran Flightgear again. It told me it was migrating the old settings, and then took me back to the Cessna. Once again I played with the controls, then ran a beginner's tutorial.

Everything looks like it works OK. However, like tmb, I'm holding back on validating because of the package numbering mismatch. If we could get that discrepancy cleared up, I'd be happy to validate.

CC: (none) => andrewsfarm

Comment 7 José Jorge 2020-01-17 14:51:54 CET
(In reply to Thomas Backlund from comment #5)
> So what's up with the "0" as release?

Sorry, my brain must have gone somewhere, I've just pushed again simgear and flightgear-data with 1 as release.
Comment 8 Thomas Andrews 2020-01-17 15:35:16 CET
Will give my mirror a chance to catch up, and check it out later today.

I may have to look into buying a usb joystick for this. My brother would really love it if there was an option for flying a hot air balloon. After being part of the crews for nearly 30 years, he wants to be a balloon pilot so bad he can taste it.
Comment 9 José Jorge 2020-01-17 15:41:19 CET
(In reply to Thomas Andrews from comment #8)
> I may have to look into buying a usb joystick for this.

No need of an USB joystick. Just click on the menu Cessna->autostart to fire up the engine. After 3 seconds, it will be running, just keep pressed PAGEUP key till maximum rpm. Then the numpad of the keyboard gives everything you need to control the plane (you'll have to compensate the propeller torque).

For hot air balloon it is even easier :
Comment 10 Thomas Andrews 2020-01-17 19:55:44 CET
Sorry for the delay. Seems that my wireless keyboard broke inside when I dropped it yesterday, and I had to hunt up my PS/2 backup.

The newest packages installed cleanly. It seems to run OK, but with my inexperience, coupled with a badly-worn keyboard, I couldn't get far. I shall have to try again when I get the replacement keyboard. I didn't see anything that I thought was wrong, though.

Going by the link Jose gave, the hot air balloon simulation isn't exactly realistic. That link describes dropping ballast for altitude control. Federal Aviation Administration rules don't allow that. Modern-day balloons, in the US at least, use the burner to go up, and either let the envelope cool to go down, or open a valve at the top to let hot air out. 

Validating. I'll let you guys sort out what to use for the correct advisory.

Keywords: (none) => validated_update

Comment 11 Thomas Andrews 2020-01-17 20:29:58 CET
Seems I jumped to conclusions twice today.

I didn't watch all of it, but https://www.youtube.com/watch?v=N2bHKyV1F3g shows more or less the controls of a modern-day balloon in Flightgear.

And, it looks like my wireless keyboard isn't broken after all. One of the batteries had dislodged. Apparently, one battery runs some of the keys, while the other runs others. Weird, but it means I just bought a replacement keyboard on ebay for no good reason...
Thomas Backlund 2020-01-19 09:51:33 CET

Keywords: (none) => advisory

Comment 12 Mageia Robot 2020-01-19 11:12:08 CET
An update for this issue has been pushed to the Mageia Updates repository.


Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.