Hi, Thanks for your help!
As a bit of background the SONAME is the internal library version, whenever you make incompatible changes to a library you need to increase the version, so it sounds like your upstream has broken compatibility and updated the SONAME correctly but not changed there major version like they probably should have. So even though the version is 1.5 the correct package name is libhts2 but the package version should be 1.5 (Unfortunately upstreams sometimes do silly things and theres not so much we can do about it).
This is what I understood and changing the name of the package for libhts2 seems to have fixed the problem indeed. I didn't tried that because I was afraid there was 2 SONAME because of the following lines: [ 46s] install -p -m 644 libhts.so /home/abuild/rpmbuild/BUILDROOT/libhts1-1.5-15.1.x86_64/usr/lib64/libhts.so.1.5 [ 46s] ln -sf libhts.so.1.5 /home/abuild/rpmbuild/BUILDROOT/libhts1-1.5-15.1.x86_64/usr/lib64/libhts.so [ 46s] ln -sf libhts.so.1.5 /home/abuild/rpmbuild/BUILDROOT/libhts1-1.5-15.1.x86_64/usr/lib64/libhts.so.2 I guess I shouldn't extrapolate the SONAME from the filename? (It's a bit blurry for me right now) So, what is openSUSE policy in that kind of case (I'd like to resubmit to the science repo if possible)? Shall I change the specfile name to libhts2 as well? Thanks, Pierre. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org