Bug 18247

Summary:	update version flightgear 2016.1
Product:	Mageia	Reporter:	Ami age <kourki>
Component:	New RPM package request	Assignee:	José Jorge <lists.jjorge>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Ami age 2016-04-23 12:21:43 CEST

Description of problem:

Hello, I see the list of packages mageia 6
is retained version 3.4 flightgear
http://madb.mageia.org/package/show/release/cauldron/name/flightgear


Since February 2016, was released a new version with important improvements,
(Add planes, ...)

is it possible you integrate the 2016.1 version is available here
http://www.flightgear.org/download/main-program/

thanks in advance

(texte ci dessus en anglais avec la traduction google
voici le texte original en franÃ§ais
Bonjour,   je vois que dans la liste des paquets de mageia 6
est retenue la version 3.4 de flightgear
http://madb.mageia.org/package/show/release/cauldron/name/flightgear


Depuis février 2016, est sortie une nouvelle version avec des améliorations importantes,
(ajouter des avions, â¦)

est t'il possible d'intégrer la version 2016.1  disponible ici pour
http://www.flightgear.org/download/main-program/

merci par avance)






Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Rémi Verschelde 2016-04-23 12:38:36 CEST

Thanks for the notice, assigning to the flightgear maintainer.

@zezinho: As the versions freeze is nearing, please notify me if you can't work on this update soon, so that I have a look (but if you can, that's best, as I have quite a few other packages to work on ;)).

Assignee: bugsquad => lists.jjorge

Comment 2 José Jorge 2016-05-04 08:37:55 CEST

Flightgear 2016.1 is now in Cauldron (and also in MGA5 backports testing).

For cauldron, I enabled CURL in SimGear for the new feature to download new aircraft (fgfs --launcher).

It starts but segfaults, I will have to investigate it. But as all else works, I'm closing this bug.

Status: NEW => RESOLVED
Resolution: (none) => FIXED