soversion is weird, possibly broken

[eli-schwartz]

$ bsdtar -tvf xapp-2.0.0-1-x86_64.pkg.tar.zst
[...]
lrwxrwxrwx  0 root   root        0 Nov 26 15:48 usr/lib/libxapp.so -> libxapp.so.1
lrwxrwxrwx  0 root   root        0 Nov 26 15:48 usr/lib/libxapp.so.1 -> libxapp.so.2.0.0
-rwxr-xr-x  0 root   root   214712 Nov 26 15:48 usr/lib/libxapp.so.2.0.0
[...]

This occurs due to https://github.com/linuxmint/xapp/blob/dc2d288144870f89e2001cc9180655d03b11229e/libxapp/meson.build#L97-L101

version: '2.0.0'
soversion: '1'

What's the intention here? To use soname versioning tracking the project version? To manually maintain an ABI of "1"?

[ItzSwirlz]

@clefebvre This can be confirmed with dependencies when building libxapp on Debian/Ubuntu, when dh_shlibdeps fails.

I'm trying to package xfce4-xapp-status-plugin and I'm getting this

dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/aarch64-linux-gnu/libxapp.so.1 (used by debian/xfce4-xapp-status-plugin/usr/lib/aarch64-linux-gnu/xfce4/panel/plugins/libxapp-status-plugin.so.0.2.2)
Hint: check if the library actually comes from a package.
dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/xfce4-xapp-status-plugin.substvars debian/xfce4-xapp-status-plugin/usr/lib/aarch64-linux-gnu/xfce4/panel/plugins/libxapp-status-plugin.so.0.2.2 returned exit code 255
dh_shlibdeps: error: Aborting due to earlier error
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

In debian/rules to fix you need to pass a --ignore-missing-info flag to dpkg-shlibdeps