On Thursday 2019-01-24 14:44, Richard Biener wrote:
On Thu, 24 Jan 2019, John Paul Adrian Glaubitz wrote:
On 1/24/19 2:35 PM, Andreas Schwab wrote:
On Jan 24 2019, John Paul Adrian Glaubitz <adrian.glaubitz@suse.com> wrote:
The thing is that the actual packages don't contain the symbolic link in question:
But it has a library with that soname, and that is what counts.
You mean the SONAME is part of the shared libary file?
i.e., running objcopy on libaws-c-common.so.1.0.0 would still dump that SONAME?
readelf -d would, yes. Somehow their setup is broken.
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!). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org