Re: Unannounced change of shlib-policy-name-error rpmlint strictness on TW
On Donnerstag, 14. Juli 2022 14:34:27 CEST Richard Biener wrote:
On Thu, 14 Jul 2022, Stefan Brüns wrote:
Hi,
a few days ago any violation of shlib-policy-name-error has become a fatal error.
This is especially problematic for many packages in the science repository, when packages are built as flavors for e.g. openmpi2/3/4, and the library packages carry a corresponding suffix. E.g.:
libhdf5-103-openmpi4.x86_64: E: shlib-policy-name-error (Badness: 10000) SONAME: libhdf5.so.103 (/usr/lib64/mpi/gcc/openmpi4/lib64/libhdf5.so.103.3.1), expected package suffix: 103
This is a case not covered by https://en.opensuse.org/ openSUSE:Shared_library_packaging_policy
Can this please be reverted until the policy has been extended to cover these cases? Preferably, rpmlint learns to understand this pattern.
The policy wasn't originally supposed to apply to shared libraries that do not reside in the default runpath which means /usr/lib*/$package/... should have been excempted. Possibly the implementation doesn't reflect that or the implementation is too narrow?
IIRC there's also a whitelist(?) - the GCC package excempts itself via rpmlintrc filtering the check ...
Richard.
In the current code I can not find such a generic exemption. Of course one can add an exemption via rpmlintrc. I would prefer not do so: 1. There are probably about 50 source packages in science alone affected by this. 2. Each rpmlintrc entry bears the risk of hiding actual packaging errors. Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019
participants (1)
-
Stefan Brüns