Your message dated Wed, 28 Oct 2020 12:03:31 +0000 with message-id <e1kxkat-0008jp...@fasolo.debian.org> and subject line Bug#972758: fixed in liburing 0.7-2 has caused the Debian Bug report #972758, regarding ABI breakage without soname bump to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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 */
--- End Message ---
--- Begin Message ---Source: liburing Source-Version: 0.7-2 Done: Guillem Jover <guil...@debian.org> We believe that the bug you reported is fixed in the latest version of liburing, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover <guil...@debian.org> (supplier of updated liburing package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 28 Oct 2020 10:35:07 +0100 Source: liburing Architecture: source Version: 0.7-2 Distribution: unstable Urgency: medium Maintainer: Guillem Jover <guil...@debian.org> Changed-By: Guillem Jover <guil...@debian.org> Closes: 972758 Changes: liburing (0.7-2) unstable; urgency=medium . * Bump the minimum version for all symbols in the symbols file, to workaround that 0.7 upstream version unintentionally broke the ABI without bumping the SONAME. (Closes: #972758) Checksums-Sha1: b18ee71a6ff494a8eb39cc15afefc17c8d031862 2241 liburing_0.7-2.dsc 8cef947448b896787f209af5773aab30147b7a72 12880 liburing_0.7-2.debian.tar.xz d319bfe8aa15373e553e2b04c033ace4f52efbc0 6301 liburing_0.7-2_amd64.buildinfo Checksums-Sha256: ec6f95a09e7a791a2934f252edfc2d0730e0ac7b18a039022f75a80a81c3ab98 2241 liburing_0.7-2.dsc c99d3fa3fadaca57b6a35bbb3751b633632b6484361b4a0bbf3c52675dd8e597 12880 liburing_0.7-2.debian.tar.xz a066b974ef1a22d3fa30de1dd35633a7ea3957e4bfa23c67b68db84510a411d6 6301 liburing_0.7-2_amd64.buildinfo Files: 9af435b06cc76888c071b76dfb853e28 2241 libs optional liburing_0.7-2.dsc f60637717d246daa5b01786ad7567f05 12880 libs optional liburing_0.7-2.debian.tar.xz 63cf9614a8379828c3afd3fd019dec96 6301 libs optional liburing_0.7-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAl+ZPIUACgkQuXK/PqSu V6PJDg//fIat7qBBdORODG5Es5wIM3cN7dDh3Y8PLIHU/h6EjtyOhQ5cIdRlipb7 Vcm/nnUSDoWGaw5tccKFuf77wRJs1HRzoav5Ej8FykAfjpqrKVTCZ3Vqsh/eC5Wj lButjGd9hWHE3mP0qlaL8ng98Q4IqN0EudeXcIfZZnGdlMtVBW5mpwynqIEPWgG8 r7FQCmoLZR+1fARJ4ENXqgbKiNzc6+pXVZAGeOc2FyaGfBfl/bblcMDHRIdD7Oi8 L+fAe+IpFHPO6YLrN4M4oAZg1zHlpvnhou9yasGtclQGPCd6NUNSUTJ0UfmAUpr8 L1SpVkEkaeqcqicVus1mvOiEPkHeYWDcWBqnBJVH+7tO3+hTrV1VoYeA0y9W1sWM P1vhyxOkob+EGayzmI5fX8vXFWcZ5TXp7+/D5VesRRHw7CY7SmruvIwRLVjuyoid KmuplVqOVsiu5kKkfB0BEGF2nVQoh1YnwnoPyW5F7pBGH8EbNtuuLWav3aDv3kUt rSOkECjC0ImENs2IdINN5yYBonDZkY1UgcHUtzz7I40EEZoaCGz2Opix1YVCIdoR C2EFkBFVMea2WnHpRlT6913MxXZvvUW4d9u7bhBw9kJ0/EdbosQ92QhcuRPx+fKf xtvQXEO184SUqEVmd482AQN6k5gD2H7cs7ZAqV/ZTvZ7fcNbHaA= =hALR -----END PGP SIGNATURE-----
--- End Message ---
