Bug 30095

Summary:	assimp: version mismatch between package version and filename of contained shared library
Product:	Mageia	Reporter:	Conrad Vielson <conrad.vielson.nhb4>
Component:	RPM Packages	Assignee:	Rémi Verschelde <rverschelde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	assimp-5.1.5-1.mga9.src.rpm	CVE:
Status comment:

Description Conrad Vielson 2022-02-26 00:05:33 CET

Description of problem:
the lib version according to the rpm package does not match the lib version number of the shared object filename contained therein.

Version-Release number of selected component (if applicable):
lib64assimp5-5.1.5-1.mga9

How reproducible:
always

Steps to Reproduce:
1. if the package is installed: 
  rpm -ql lib64assimp5-5.1.5-1.mga9 |grep so.5.1
  otherwise
  urpmq -l lib64assimp5-5.1.5-1.mga9 |grep so.5.1

2. notice that the version of the package doesn't match the version according to the shared library file name

Conrad Vielson 2022-02-26 00:07:13 CET

Summary: version mismatch between package version and filename of contained shared library => assimp: version mismatch between package version and filename of contained shared library

Comment 1 Conrad Vielson 2022-02-26 00:10:06 CET

the file contained is /usr/lib64/libassimp.so.5.1.4 and not /usr/lib64/libassimp.so.5.1.5 as I would expect from the version of the rpm

Comment 2 Lewis Smith 2022-02-26 09:37:48 CET

Thank you for the report.

Note this is Cauldron. On Mageia 8 I see:
 $ urpmq -l lib64assimp3 |grep so
/usr/lib64/libassimp.so.3
/usr/lib64/libassimp.so.3.3.1

Assigning to Rémi who looks after this package.

Assignee: bugsquad => rverschelde

Comment 3 Thomas Backlund 2022-02-26 09:47:37 CET

Looks like an upstream bug forgetting to bump some bits during 5.1.5 release as the 5.1.6 release bumps 2 micro steps:
https://github.com/assimp/assimp/commit/1d8667bfdc140df93b6255c926a6d9e21877482c

Rémi Verschelde 2022-02-26 12:03:21 CET

Status: NEW => ASSIGNED

Comment 4 Rémi Verschelde 2022-02-26 12:46:22 CET

I don't know if that's really a bug per se, it's upstream negligence but after years of trying to patch it up, I'm tending towards giving up on it. It doesn't really matter.

Anyway, I packaged 5.2.2 to fix it, and...

/usr/lib64/libassimp.so.5.2.0

Yay. I'll patch it up I guess.

Comment 5 Rémi Verschelde 2022-02-26 12:55:50 CET

> after years of trying to patch it up, I'm tending towards giving up on it.

I mean years of patching it up in various packages which can't figure out how to tag a new release without missing a version bump. Assimp is one of them but there's plenty others.

Anyway, fixed in assimp-5.2.2-1.mga9.

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

Comment 6 Thomas Backlund 2022-02-26 14:56:17 CET

(In reply to Rémi Verschelde from comment #4)
> I don't know if that's really a bug per se, it's upstream negligence but
> after years of trying to patch it up, I'm tending towards giving up on it.
> It doesn't really matter.
> 
> Anyway, I packaged 5.2.2 to fix it, and...
> 
> /usr/lib64/libassimp.so.5.2.0
> 

Yeah, come to think of it... it could be intentional too...
If nothing in the lib changes during version bump, it can basically stay the same ...

otoh, I dont know if anything else depends on this lib, at which point this becomes mostly bike schedding :)

Comment 7 Lewis Smith 2022-02-26 20:41:59 CET

Thank you Rémi for a quick fix.

@Conrad
Please report back that this update fixes the issue for you.