| Summary: | libdvdnav version seen with CCM is 4.2.0 but the files are 4.1.2 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Paul Éric Despretz <paul-eric.despretz> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | jani.valimaa |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | lib64dvdnav4 | CVE: | |
| Status comment: | |||
|
Description
Paul Éric Despretz
2013-06-25 21:23:40 CEST
This 4.1.2 in library file name isn't the version of the package. It tells some information about the library API and doesn't always follow the package versioning scheme (or vice versa). Snip from libdvdnav's configure.ac: dnl If you want to know more about what you are doing, here are some details: dnl * DVDNAV_LT_CURRENT is the current API version dnl * DVDNAV_LT_REVISION is an internal revision number which is increased when the API dnl itself did not change dnl * DVDNAV_LT_AGE is the number of previous API versions still supported by this library dnl * libtool has its own numbering scheme, because local library numbering schemes dnl are platform dependent dnl * in Linux, the library will be named dnl libname.so.(DVDNAV_LT_CURRENT - DVDNAV_LT_AGE).DVDNAV_LT_AGE.DVDNAV_LT_REVISION So, in this case just trust the version you see in rpm. I'm closing this as INVALID. Status:
NEW =>
RESOLVED |