Hello ! A maintenance release of OpenCPN (a Chartplotter and navigation software) as been published (May 8th 2013)... it could not be substituted to the previous version during Mageia3 Freeze!... It has been committed now (both in Cauldron and Mageia3/updates ) but is waiting to be submitted. I installed it, configured it, tested it ...OK (fresh install) I installed the previous version (fresh install), configured it, and then updated it (the configuration remains OK) Free but copyrighted charts may be downloaded from here http://opencpn.org/ocpn/chart_sources Suggested Advisory =================== This version is a maintenance release and update of OpenCPN Version 3.2. It corrects several non-critical operational faults and special case configurations. ( particularly : Correct crash when opening file with only one date) Updated packages in Core/updates_testing ======================================== opencpn-3.2.2-1 opencpn-debug-3.2.2-1 opencpn-logbook-plugin-3.2.2-1 Source RPM ----------- opencpn-3.2.2-1.mga3.src.rpm Reproducible: Steps to Reproduce:
NB : It is a little difficult to really totally test this software : you need to be on a boat with your computer connected to a GPS optionnally an AIS receiver and eventually to some navigation instruments... the QA may only verify that the update is easy and doesn't crash ;-)
please reassign when it's done
Philippe, I'm not sure that you should have committed a new version to /3. Updates to official releases should only be bug fixes/security fixes to the same version, however there are sometimes exceptions, where the new version is solely a bug fix/security release with no new features and it is impractical to patch the original. Do you think that the above applies in this case? If not, is there a patch to fix the earlier version that could be applied, rather than pushing the new version? If the new version is pushed to /3 then you will need to bump release on the Cauldron package to 2, as it needs to always be higher than the release in /3. Barry
CC: (none) => zen25000
Hi Barry ! As I wrote in the description, this is not a new version of opencpn, it's always 3.2 version, but they just published a maintenance release (3.2.2 instead of 3.2.0) fixing several minor bugs, not bringing any new feature (this would need nearly 25 patches ... and it's easier and riskless to change the tarball !) They already did it for the previous version (3.0.2 was a maintenance release for 3.0.0...) I think we are absolutely in the particular case that allows to update to a new release of the same version... So, I must commit to bump the cauldron release to 3.2.2-2 before you submit this update 3.2.2-1 to mga3 (I thought the mkrel mg4 was enough when there's the same version in mga3 ...) isn't it ?
(In reply to Philippe Didier from comment #4) > Hi Barry ! > As I wrote in the description, this is not a new version of opencpn, it's > always 3.2 version, but they just published a maintenance release (3.2.2 > instead of 3.2.0) fixing several minor bugs, not bringing any new feature > > (this would need nearly 25 patches ... and it's easier and riskless to > change the tarball !) > > They already did it for the previous version (3.0.2 was a maintenance > release for 3.0.0...) > > > I think we are absolutely in the particular case that allows to update to a > new release of the same version... OK that's fine. > > So, I must commit to bump the cauldron release to 3.2.2-2 before you submit > this update 3.2.2-1 to mga3 (I thought the mkrel mg4 was enough when there's > the same version in mga3 ...) > isn't it ? No - on reflection in this case I think that the Cauldron package is OK and we need a "%define subrel 1" in the Mga3 spec. Sorry for causing confusion ;)
The updates have been submitted and are in Mageia3/core/updates_testing Suggested Advisory =================== This version is a maintenance release and update of OpenCPN Version 3.2. It corrects several non-critical operational faults and special case configurations. ( particularly : Correct crash when opening file with only one date) Updated packages in Core/updates_testing ======================================== opencpn-3.2.2-1.1 opencpn-debug-3.2.2-1.1 opencpn-logbook-plugin-3.2.2-1.1 Source RPM ----------- opencpn-3.2.2-1.1.mga3.src.rpm It's a Chartplotter and navigation software... QA needs only to verify that the update is smooth and doesn't crash... (to really test it one must use marine charts, connected GPS, and a ship !) Nevertheless, anyone may try to display charts (panning, zooming ): Free but copyrighted charts may be downloaded from here http://opencpn.org/ocpn/chart_sources
Source RPM: opencpn-3.2.2-1 => opencpn-3.2.2-1.1
If it's ready please reassign to QA (qa-bugs at ml.mageia.org)
Assignee: bugsquad => qa-bugs
Ok Manuel ! reassigned to QA Team I didn't dare to do it directly Thanks
Upgrade successful on MGA3-32-OK Testing platform M3/VirtualBox So noted in the Whiteboard.
CC: (none) => wilcal.intWhiteboard: (none) => MGA3-32-OK
Upgrade successful on MGA3-64-OK Testing platform M3/VirtualBox So noted in the Whiteboard.
Whiteboard: MGA3-32-OK => MGA3-32-OK MGA3-64-OK
Update validated Advisory: ================================= This updates the opencpn application from opencpn-3.2.0-1 to opencpn-3.2.2-1.1 The application does not create an icon in the launch menu but a "opencpn" executed in a user terminal launches the application. A basic map is displayed. Updated packages in core/updates_testing: ======================== opencpn-3.2.2-1.1 opencpn-debug-3.2.2-1.1 opencpn-logbook-plugin-3.2.2-1.1 from SRPMS: opencpn-3.2.2-1.1.mga3.src.rpm Could sysadmin please push from core/updates_testing to core/updates. Thank you!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
advisory uploaded
http://advisories.mageia.org/MGAA-2013-0041.html
Status: NEW => RESOLVEDCC: (none) => boklmResolution: (none) => FIXED
CC: boklm => (none)