Bug 6160 - There is now yaflight-0.1.10 in core/updates_testing to validate
Summary: There is now yaflight-0.1.10 in core/updates_testing to validate
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: mga2-64-OK, mag2-i586 OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2012-05-29 22:32 CEST by Matteo Pasotti
Modified: 2012-06-20 21:06 CEST (History)
5 users (show)

See Also:
Source RPM: yaflight-0.1.10-3.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Matteo Pasotti 2012-05-29 22:32:37 CEST
This new package release provides new sources that includes a patch previously integrated at rpm build time (yaflight-menvironment-verifyupdates.patch) plus a minor feature allowing people to change the flightgear root path from which the simulation starts. No other improvements, no other bugfixes.

It's a minor release provided by the upstream with no version change.

Steps to reproduce
------------------

- opening the about box pressing the correspondent button into the main interface, with no internet connection available, doesn't generate an unhandled exception;
- choosing advanced features allows the user to change the flightgear root path used by fgfs to start the simulation.

Regards,
Matteo
Matteo Pasotti 2012-05-29 22:33:32 CEST

Assignee: bugsquad => qa-bugs

Comment 1 Zvonimir Fras 2012-05-30 12:46:58 CEST
Checked both steps on x86_64

1st step didn't generate unhandled exception in the release nor the update candidate.

2nd step reproducable in the update candidate via the added option




No regressions but found a bug on both versions:

"FMain.Form_Close.479: #11: Unknown symbol 'Close' in class 'Control'
1: FMain.Form_Close.479" on close the app

steps to reproduce:
run yaflight.gambas
click the "Advanced" button
Click any option there (i.e. Features)
Try close the application (alt+f4 or otherwise)
'Yes' on 'Are you sure to end the simulation session?'
***

If none of the advanced suboptions isn't open (i.e. Advanced->Features), error does not occur (be it not opened at all or opened and then closed)


Cheers, Zvonimir

CC: (none) => zvonimir

Comment 2 Matteo Pasotti 2012-05-31 18:05:43 CEST
The bug should be fixed in package yaflight-0.1.10-3.1.mga2
It was related to the new gambas3-3.1.1 behavior.

Can you check once again, please?

Regards,
Matteo
Comment 3 Zvonimir Fras 2012-06-01 15:58:27 CEST
Sorry I haven't been able to test any sooner, had some issues and was away.

Tested the yaflight-0.1.10-3.1.mga2, bug I described is gone, no regressions found.

Good job! :)


Zvonimir
Comment 4 Zvonimir Fras 2012-06-01 16:00:23 CEST
(In reply to comment #3)
> Sorry I haven't been able to test any sooner, had some issues and was away.
> 
> Tested the yaflight-0.1.10-3.1.mga2, bug I described is gone, no regressions
> found.
> 
> Good job! :)
> 
> 
> Zvonimir

Tested on x86_64 only, though, someone should probably check on i586, I don't have the environment for now.
claire robinson 2012-06-09 13:18:44 CEST

Hardware: i586 => All
Whiteboard: (none) => mga2-64-OK

Comment 5 Luan Pham 2012-06-10 18:02:03 CEST
I just test on i586 so far so good no other problem report.

CC: (none) => pham182b
Whiteboard: mga2-64-OK => mga2-64-OK, mag2-i586 OK

Comment 6 Dave Hodgins 2012-06-10 19:02:45 CEST
Validating the update.

Could someone from the sysadmin team push the srpm
yaflight-0.1.10-3.1.mga2.src.rpm
from Mageia 2 Core Updates Testing to Core Updates.

Advisory:  This update to yaflight corrects an unhandled exception
when no internet connection is available, and adds the option to
change the flightgear root path used by fgfs to start the simulation.

https://bugs.mageia.org/show_bug.cgi?id=6160

Keywords: (none) => validated_update
CC: (none) => davidwhodgins, sysadmin-bugs

Comment 7 Thomas Backlund 2012-06-20 21:06:36 CEST
Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0080

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


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