Bug 32742 - TRACKER for a large number of openCPN plugin updates
Summary: TRACKER for a large number of openCPN plugin updates
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 32690 32726 32727 32728 32729 32730 32731 32732 32733 32734 32735 32736 32737 32738 32739 32740
Blocks:
  Show dependency treegraph
 
Reported: 2024-01-17 20:19 CET by Lewis Smith
Modified: 2024-01-21 17:38 CET (History)
2 users (show)

See Also:
Source RPM: opencpn-*-plugin
CVE:
Status comment:


Attachments
Log of install current opencpn-*-plugin versions and update to testing versions (19.44 KB, text/plain)
2024-01-17 21:53 CET, katnatek
Details

Description Lewis Smith 2024-01-17 20:19:48 CET
The bugs to be listed are all of a kind re updated plugins for opencpn version from core/updates (opencpn-5.8.4-2)
Comment 1 Lewis Smith 2024-01-17 20:24:12 CET
Entering subordinate bugs.

Depends on: (none) => 32726, 32727, 32728, 32729, 32730, 32731, 32732, 32733, 32734, 32735, 32736, 32737, 32738, 32739, 32740

Comment 2 Lewis Smith 2024-01-17 20:26:07 CET
Assigning to QA like the subsidiary bugs.

Assignee: bugsquad => qa-bugs

Comment 3 katnatek 2024-01-17 21:53:55 CET
Created attachment 14267 [details]
Log of install current opencpn-*-plugin versions and update to testing versions

Any issue detected when the current packages were updated to testing packages.
Sorry if this is not the right testing method, but are a lot of reports and the only suggested test is checking the right update over the current packages
Comment 4 katnatek 2024-01-17 21:55:21 CET
Test done in real hardware Mageia 9 x86_64 lxqt
Comment 5 Philippe Didier 2024-01-18 15:20:44 CET
(In reply to katnatek from comment #4)
> Test done in real hardware Mageia 9 x86_64 lxqt

Thanks
1) This shows that the update is correctly done from the point of view of the package manager

2) The other part of the job would be to test each updated plugin inside OpenCPN when you use OpenCPN for the first time

I explain the process to test each plugin in its bug report

3) The last part would be to test the updated plugins inside OpenCPN when you have already used and configured OpenCPN, having installed free charts, having installed
paid encrypted charts (with opencpn-o-charts-plugin), having previous climatology data, having already written a logbook

being the maintainer and a long time user of OpenCPN I did all the tests for these plugins on my own system before proposing these updates to updates_testing
(I have had to ask some developers to modify some sources, or I have had to patch them)

I can say that everything is OK for MGA9 64bits

But that's probably not enough...

CC: (none) => philippedidier

Comment 6 Lewis Smith 2024-01-18 19:29:43 CET
(In reply to katnatek from comment #3)
> Any issue detected when the current packages were updated to testing
> packages.
> Sorry if this is not the right testing method, but are a lot of reports and
> the only suggested test is checking the right update over the current
> packages
This was a perfectly sensible test: clean updates; and thank you for doing that.
"Any issue detected"; from what follows, I take to mean "No issue detected".

(In reply to Philippe Didier from comment #5)
> 3) The last part would be to test the updated plugins inside OpenCPN when
> you have already used and configured OpenCPN, having installed free charts,
> having installed
> paid encrypted charts (with opencpn-o-charts-plugin), having previous
> climatology data, having already written a logbook
> being the maintainer and a long time user of OpenCPN I did all the tests for
> these plugins on my own system before proposing these updates to
> updates_testing
> (I have had to ask some developers to modify some sources, or I have had to
> patch them)
> I can say that everything is OK for MGA9 64bits
This is very important, Philippe. You have been very thorough, and done a huge amount of work.

CC'ing TJ so that he can clear the path for QA: clean update, give it the OK.

CC: (none) => andrewsfarm

Philippe Didier 2024-01-19 12:37:26 CET

Depends on: (none) => 32690

Comment 7 Philippe Didier 2024-01-19 18:20:34 CET
Hi Lewis
Since katnatek could do a clean update

Since I have fully tested all these updated plugins on my computer
- 1) simulating a first use of OpenCPN (rename my existing .opencpn/ to .opencpnbak/
so that a new .opencpn/ is created

- 2) using the already configurated OpenCPN (delete the .opencpn/ created in 1) rename the previously backed up .opencpnbak/ to .opencpn/

May I say OK for MGA9 64bits for each plugin or must I wait that somebody else tests them one by one ?
Comment 8 Thomas Andrews 2024-01-21 17:38:58 CET
They have all been checked, and validated. Closing as fixed.

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


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