Suggested Advisory :
======================
This update brings the last commits of this C++ library for MARitime NAVigation purposes. 
It may be needed to build or use programs for maritime navigation

RPMS:
lib(64)marnav-devel-0.14.0-6.git20230504.mga9
lib(64)marnav0.14.0-0.14.0-6.git20230504.mga9

SRPM:
marnav-0.14.0-6.git20230504.mga9.src.rpm

# QA
you only have to verify the update is smoothly done

Source RPM: marnav-0.14.0-6.git20230504.mga9.src.rpm => marnav-0.14.0-6.git20230504.mga9

RH x86_64

marnav is replaced by lib64marnav0.14.0

installing opencpn-nsk-plugin-0.2.4.1-1.mga9.x86_64.rpm lib64marnav0.14.0-0.14.0-6.git20230504.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ###################################################################################################
      1/2: lib64marnav0.14.0     ###################################################################################################
      2/2: opencpn-nsk-plugin    ###################################################################################################
      1/2: removing opencpn-nsk-plugin-0.2.2-3.mga9.x86_64
                                 ###################################################################################################
removing package marnav-0.14.0-3.mga9.x86_64
      2/2: removing marnav-0.14.0-3.mga9.x86_64
                                 ###################################################################################################

But I wonder if is the right naming schema

CC: (none) => pkg-bugs

Hi Jose
Indeed that's right for marnav srpm

I have libified marnav since it doesn't contain any binaries
building this new git version creates 
lib64marnav rpm
and 
lib64marnav-devel rpm

That's why marnav is removed

About the naming
"lib64marnav0.14.0" gives the version of the libs that the rpm installs in /usr/lib64/ 
-libmarnav-io.so.0.14.0 and 
-libmarnav.so.0.14.0 

and the whole name of the rpm contains twice 0.14.0 :
- once for the library version 0.14.0
- once for the rpm version and release 0.14.0-6.git20230504
that gives
lib64marnav0.14.0-0.14.0-6.git20230504.mga9

Nota Bene 
for the devel rpm 0.14.0 appears only once
lib64marnav-devel-0.14.0-6.git20230504.mga9

My point and "complain" come from the inclusion of 0.14.0 in the name
Usually I just see a major (this case 0) or major_minor in the name of the libs
Not remember see the full mayor.minor.patch schema in the naming of a lib

Hi Jose

The error comes from my spec file !!!

it begins with :

%define major     %{version}
%define libname   %mklibname %name %{major}

This should be

%define major     0
%define libname   %mklibname %name %{major}

Maybe I need to correct this spec file and submit it again as
marnav-0.14.0-7.git20230504.mga9

(In reply to katnatek from comment #4)
> My point and "complain" come from the inclusion of 0.14.0 in the name
> Usually I just see a major (this case 0) or major_minor in the name of the
> libs
> Not remember see the full mayor.minor.patch schema in the naming of a lib

Hi Jose

I have just submitted marnav-0.14.0-7.git20230504.mga9 to 
Mageia9/core/updates_testing with a corrected %define major

May I simply modify the title of this Update Request or may I close this and open an other one ?

Hi Jose
From what Jani said about Mageia10 :
Apparently modifying %define major in the spec was a bad idea :
Inside Mageia10 the already existing marnav-0.14.0-6.git20230504.mga10 was OK for him

but my Push request for marnav-0.14.0-7.git20230504.mga10 doesn't satisfy the Mageia policy

Unfortunately I have already modified the spec files of marnav for Mageia10 and Mageia9
And I have already submitted marnav-0.14.0-7.git20230504.mga9 inside Mageia9/core/updates_testing which replaced there marnav-0.14.0-6.git20230504.mga9 that was previously OK


I am searching how to revert the commit from marnav-0.14.0-6.git20230504.mga9 to marnav-0.14.0-7.git20230504.mga9 
and 
from marnav-0.14.0-6.git20230504.mga10 to marnav-0.14.0-7.git20230504.mga10

Hi

I have reverted the bad modification that was brought inside the spec of marnav-0.14.0-7.git20230504   (concerning the %define major part of this spec)

Now there's marnav-0.14.0-8.git20230504 inside Mageia9/core/updates_testing 

It is similar to the previous correct marnav-0.14.0-6.git20230504 that was first proposed in this request and correct regarding the advice of Jani for Mageia10

Source RPM: marnav-0.14.0-6.git20230504.mga9 => marnav-0.14.0-8.git20230504.mga9

installing lib64marnav0.14.0-0.14.0-8.git20230504.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ###################################################################################################
      1/1: lib64marnav0.14.0     ###################################################################################################
removing package marnav-0.14.0-3.mga9.x86_64
      1/1: removing marnav-0.14.0-3.mga9.x86_64
                                 ###################################################################################################

LC_ALL=C urpmi lib64marnav-devel 


installing lib64marnav-devel-0.14.0-8.git20230504.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ###################################################################################################
      1/1: lib64marnav-devel     ###################################################################################################


This looks good for me , sorry for make you work twice
You know what they say about good intentions and that hot place ;)

CC: (none) => andrewsfarm
Whiteboard: (none) => MGA9-64-OK

Validating.

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

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2026-0017.html

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