On Thu, 24 Jan 2019, John Paul Adrian Glaubitz wrote:
On 1/24/19 4:03 PM, Jan Engelhardt wrote:
Unusual, but not necessarily broken -- as far as the packaging guidelines are concerned.
[ 18s] libaws-c-common1.0.0.x86_64: W: shlib-unversioned-lib libaws-c-common.so.0unstable
If the SONAME is libaws-c-common.so.0unstable, then the package must be named libaws-c-common0unstable, not libaws-c-common1_0_0 (and not libaws-c-common1.0.0 either!).
Yes, I'm aware that the library package name has to match the SONAME.
I don't think though that we having "0unstable" as SOVERSION is desirable.
Yeah, if that suggests the ABI isn't stable we don't want to ship
this kind of state.
Richard.
--
Richard Biener