Bug#929187: libbpf soversion does not match the package name
Package: src:linux
Version: 4.19.37-3
Severity: serious
We currently use $(make kernelversion) to generate the soversion,
resulting in 3 components of the upstream version (currently 4.19.37),
whereas the package name only uses 2 components (currently 4.19). We
really want the latter as we don't expect the ABI to change in a
stable update.
There is an additional bug that building perf also rebuilds libbpf.
This seems to set some environment variables such that the soversion
changes again, duplicating the second component and resulting in
4.19.19.37!
This is a violation of Debian policy: the binary package name must
change if the soname changes.
Ben.
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: