Description of problem: this openCPN plugin has been improved since opencpn-8.2.4 was packaged it brings an improvement of the Layouts management this new version is updates_testing Updated package in /core/updates_testings ========================================= opencpn-logbookkonni-plugin-1.4.31.0-2.mga9 for each arch from SRPM opencpn-logbookkonni-plugin-1.4.31.0-2.mga9.src.rpm This package needs to be tested on the opencpn version from core/updates (opencpn-5.8.4-2)
(In reply to Philippe Didier from comment #0) > Description of problem: > > this openCPN plugin has been improved since opencpn-8.2.4 was packaged > it brings an improvement of the Layouts management Current version is opencpn-5.8.4-2.mga9, so I guess the above is a typo? This is against stable Mageia 9 so unless this is a major bug fix or security fix then it would surely be against our updates policy to push an 'improvement'. If this was not the case then I would also be pushing updates with 'improvements' and we would not have so many 'out-of-date' packages in Mageia 9. https://wiki.mageia.org/en/Updates_policy
CC: (none) => zen25000
Hi Barry You are right There's a typo in all this bug list (I used the same skeleton for all of them) : I should have written This package needs to be tested on the opencpn version from core/release (opencpn-5.8.4-2) and not This package needs to be tested on the opencpn version from core/updates !!! (opencpn-5.8.4-2) Besides this, about enhancement versus bugfix Indeed there's a security fix for weatherfax since audiofile which is a BuildRequire has been updated for security vulnerability besides this it's now built in different way upon opencpn-libs and brings an improved list of meteo stations and internet meteo providers This one is not proposed as an enhancement but as a normal bug correction. All the other plugins are now built upon opencpn-libs (I already built them this way for Cauldron) Some of these updates bring some improvements for navigation security (sar, watchdog, radar, ais-radar, climatology, weatherfax) I thought it was necessary to provide them as updates If it's against Updates_policy maybe should they be proposed as backports
This application really does need to work, so updates may not just be a luxury. As for new versions of things, we nearly always react where possible to specific update requests. If you, Philippe, could give a pointer to testing it... But thanks yet again for your sterling work on this application.
Assignee: bugsquad => qa-bugs
Blocks: (none) => 32742
to test it you simply have to verify that the update is done without any problem First in the tool menu choose plugins then choose logbook and click on its settings then in the bottom of this window click on install Layouts it will direct you to the place where to find the file Layouts.zip choose it the Layouts will be installed to be used by you Then click on the logbook icon inside the icons bar You can then add some lines to your logbook And choose a kind of layout to display, and display this as a libreoffice file or an html file
Advisory from comment 0 added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"
CC: (none) => marja11Keywords: (none) => advisory
Mageia9, x86_64 Clean installation of the plugin. Enabled logbook plugin via options and installed a layout without any idea what to expect. Opened up the logbook and filled in a few details like fuel and water supply and a start position. Displayed the equipment manifest in a browser, which at this stage was empty. Backed out at that point but had the impression that the plugin was working. Giving this an OK.
CC: (none) => tarazed25Whiteboard: (none) => MGA9-64-OK
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0015.html
Status: NEW => RESOLVEDResolution: (none) => FIXED