Package: liburing1 Version: 0.7-1 Severity: grave Tags: upstream Hi,
I've had a number of reports from people who are having problems with plocate, that can be traced to differing versions of liburing1. Specifically, plocate is built in sid against liburing1 0.7-1 (which gets a versioned dependency only on liburing1 >= 0.4), but if people instead have liburing1 0.6-3 on their systems, they crash: kos:~> plocate plocate md5sums /home/sesse/nmu/plocate-1.0.2/debian/.debhelper/plocate/dbgsym-root/DEBIAN/md5sums /home/sesse/nmu/plocate-1.0.2/debian/plocate/DEBIAN/md5sums /var/lib/dpkg/info/plocate-dbgsym.md5sums /var/lib/dpkg/info/plocate.md5sums kos:~> sudo dpkg -i liburing1_0.6-3_amd64.deb [...] kos:~> plocate plocate md5sums zsh: segmentation fault plocate plocate md5sums If this were somehow only about newer functionality or critical fixes, it could be fixed by bumping the versioned dependency, but rhis goes both ways; if you build plocate against liburing 0.6-3, and then upgrade liburing1 to 0.7-1, you get a similar crash. So it would seem there's hidden ABI breakage here that needs a soname bump. /* Steinar */
