Bug 18327 - Backport Candidate : flightgear 2016.1.2
Summary: Backport Candidate : flightgear 2016.1.2
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure MGA5-64-OK
Keywords: Backport, validated_backport
Depends on:
Blocks:
 
Reported: 2016-05-02 17:49 CEST by José Jorge
Modified: 2016-07-14 22:23 CEST (History)
4 users (show)

See Also:
Source RPM: flightgear simgear flightgear-data
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description José Jorge 2016-05-02 17:49:00 CEST 
As it was done with version 3.4 for MGA4, it would be nice to backport the latest flightgear to MGA5.
José Jorge 2016-05-02 17:49:13 CEST

Keywords: (none) => Backport

José Jorge 2016-05-02 17:50:53 CEST

Assignee: lists.jjorge => qa-bugs
Summary: Backport request : flightgear 2016.1 => Backport Candidate : flightgear 2016.1

Comment 1 José Jorge 2016-05-02 18:01:44 CEST 
How to test : install the 3 RPMS  flightgear flightgear-data and simgear.

RPMS:
flightgear-2016.1.1-1.mga5.x86_64.rpm
flightgear-data-2016.1.1-1.mga5.noarch.rpm
simgear-devel-2016.1.1-1.mga5.x86_64.rpm
simgear-2016.1.1-1.mga5.x86_64.rpm

SRPMS:
flightgear-2016.1.1-1.mga5.srpm
flightgear-data-2016.1.1-1.srpm
simgear-2016.1.1-1.mga5.srpm
José Jorge 2016-05-02 18:03:15 CEST

CC: (none) => lists.jjorge
Whiteboard: (none) => has_procedure

Comment 2 José Jorge 2016-05-07 18:43:11 CEST 
The new feature : download new aircrafts from GUI failed. Upstream said it was fixed in 2016.1.2 release, so I have submitted this new version, and also added a desktop file to launch this GUI : fgfs --launcher .

Please remove all 2016.1.1 RPMS and SRPMS.

RPMS:
flightgear-2016.1.2-1.mga5.x86_64.rpm
flightgear-data-2016.1.2-1.mga5.noarch.rpm
simgear-devel-2016.1.2-1.mga5.x86_64.rpm
simgear-2016.1.2-1.mga5.x86_64.rpm

SRPMS:
flightgear-2016.1.2-1.mga5.srpm
flightgear-data-2016.1.2-1.srpm
simgear-2016.1.2-1.mga5.srpm
José Jorge 2016-05-07 18:43:20 CEST

Summary: Backport Candidate : flightgear 2016.1 => Backport Candidate : flightgear 2016.1.2

José Jorge 2016-05-07 18:43:34 CEST

Source RPM: flightgear => flightgear simgear flightgear-data

Comment 3 nexus nexus 2016-05-09 22:49:29 CEST 
Hi

From where i can get the rpm files?

Regards

CC: (none) => nexus9

Comment 4 José Jorge 2016-05-10 13:34:56 CEST 
(In reply to nexus nexus from comment #3)
> Hi
> 
> From where i can get the rpm files?
> 
As for any update to validate :

urpmi.update ''
urpmi --searchmedia testing flightgear
José Jorge 2016-05-10 13:35:10 CEST

Status: NEW => ASSIGNED

Comment 5 José Jorge 2016-05-26 12:28:22 CEST 
No one else tested? I did, on x86_64. All is Ok.
Comment 6 Rémi Verschelde 2016-05-26 12:59:58 CEST 
There's version 2016.2.1 upstream, so maybe better to put the backport request on hold and to push the new version instead? (Note: I'm currently uploading the huge 1.5 GB of data with mgarepo, so no need for you to do it too)
Comment 7 José Jorge 2016-05-26 21:40:17 CEST 
(In reply to Rémi Verschelde from comment #6)
> There's version 2016.2.1 upstream, so maybe better to put the backport
> request on hold and to push the new version instead? (Note: I'm currently
> uploading the huge 1.5 GB of data with mgarepo, so no need for you to do it
> too)

Agreed, done. A few hours are needed for this huge -1.5GB- software to hit the mirrors...
Comment 8 Brian Rockwell 2016-06-13 22:27:05 CEST 
I'm downloading it now.  I'll let you know if it will work on my equipment.

CC: (none) => brtians1

Comment 9 Brian Rockwell 2016-06-14 00:10:27 CEST 
I was able to load the game and crash a cessna 172 off the side of the runway.

Working as designed.

Whiteboard: has_procedure => has_procedure MGA5-64-OK

Brian Rockwell 2016-06-17 11:09:31 CEST

Keywords: (none) => validated_backport

Comment 10 Thomas Backlund 2016-07-14 22:23:58 CEST 
Pushed to backports

CC: (none) => tmb
Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.