To be honest I have no idea what in the test run output are actual failures and what aren't but the last error is: 62/6 boosttest:Boost linktest OK 0.05s 63/6 boosttest:Boost nomod OK 0.04s 64/6 boosttest:Boost extralib test OK 0.03s 65/6 boosttest:Boost UTF test OK 0.05s 66/6 boosttest:External Dependency OK 0.02s 67/6 boosttest:Boost Python3 FAIL 0.20s killed by signal 11 SIGSEGV 125f976e40/:/usr/lib/libeatmydata' ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MESON_TEST_ITERATION=1 MALLOC_PERTURB_=123 /usr/bin/python3 ./test_python_module.py '/build/reproducible-path/meson-1.11.1/b 125f976e40' Ok: 5 Fail: 1 Full log written to /build/reproducible-path/meson-1.11.1/b 125f976e40/meson- logs/testlog.txt No tests defined. Total passed tests: 752 Total failed tests: 2 Total skipped tests: 50
The underlying reason this fails is that when looking up the deps, Meson finds Boost Python compiled against 313 rather than 314. Both of them are present on the file system and I'd need to debug why it is not picking up the correct one. OTOH should Boost even be providing libraries for 3.13 any more?
3.13 is a "supported" version but no longer (in sid) the "default" one, see /usr/share/python3/debian_defaults. We try to have everything in Debian support all supported versions, so libboost-python1.90.0 shipping both libboost_python313.so.1.90.0 and libboost_python314.so.1.90.0 is the desired outcome. If meson or some parts of it (including parts of tests) can only support a single Python version they should support the default one, and if they instead look for a random one that is what should be fixed. Hopefully this makes sense.
We believe that the bug you reported is fixed in the latest version of meson, 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 1141440@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jussi Pakkanen <jussi.pakkanen@mailbox.org> (supplier of updated meson 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 ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Tue, 07 Jul 2026 16:09:00 +0300 Source: meson Architecture: source Version: 1.12.0~rc1-1 Distribution: experimental Urgency: medium Maintainer: Jussi Pakkanen <jussi.pakkanen@mailbox.org> Changed-By: Jussi Pakkanen <jussi.pakkanen@mailbox.org> Closes: 1129857 1134724 1141440 Changes: meson (1.12.0~rc1-1) experimental; urgency=medium . * New upstream release. Closes: #1134724, #1141440, #1129857. Checksums-Sha1: 9776c8d43f43b116ae1af1f4fb2b3446765587b4 3558 meson_1.12.0~rc1-1.dsc 041198968d2ea3cd314aa650de5ff600fc4a4222 2516312 meson_1.12.0~rc1.orig.tar.gz a9bbb6ace7fadf1297954338e4cfd00fcce16ff9 16652 meson_1.12.0~rc1-1.debian.tar.xz a7486ffec8deefa90219631e17c79298dd0b3768 29573 meson_1.12.0~rc1-1_source.buildinfo Checksums-Sha256: 9a1787c46c690d17d22bcb06fa06c193b3688308f0c691e1719289e5c47d8439 3558 meson_1.12.0~rc1-1.dsc 23834584d070c020da7ab3ce816ec1f172999f62e83ba1ae9dab565859671c2e 2516312 meson_1.12.0~rc1.orig.tar.gz 5ac543bae4af43aaad59da9a817d07112e9dd911765de72d1bb6e8d1b3f11c58 16652 meson_1.12.0~rc1-1.debian.tar.xz ce39f56553807e8b4040c2196024051feb7f5ce8e195d375e3f16e2e71d49565 29573 meson_1.12.0~rc1-1_source.buildinfo Files: b56fe8c0ebed79c2bd673787371dfbc6 3558 devel optional meson_1.12.0~rc1-1.dsc e93dee74abc4a9641fcdda7e865e5138 2516312 devel optional meson_1.12.0~rc1.orig.tar.gz 2123a6efb40e18e8638bd642ef5e1b58 16652 devel optional meson_1.12.0~rc1-1.debian.tar.xz 75f698daa92f72f50897111dea8c6166 29573 devel optional meson_1.12.0~rc1-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJPBAEBCgA5FiEEGeLW2bRtjapiiPh3wk5jG6ux/nAFAmpM+vobHGp1c3NpLnBh a2thbmVuQG1haWxib3gub3JnAAoJEMJOYxursf5w7moQAJt++hDUI2VHGa1c2fZE 1/hGXy5AbhsJi7AdEAH7LIYBsg1zBi7NwDl6uXgO3u93svmS50atprzigmgrJ5kl v/2g4Bumx6bpEP/AuS9mD+5e8N0k8yIiunKVwXEUTV5fzV3ArB9NWJRST3igB68A RXDHi9qQPJV5BjhIREdhiIahKg7UKeb9tIfJxQr6P7XkMhNItwtbio16Dn5TUZ9f LdRIGG0ozMAJSt/Y+4E4iJMyQuWKPiYHSGWGqk7+h50viGbDbcHzNhdyy9H0SF75 QPVsFgROR6cDbPyW9bihZQLnyyR+lsKeYsqyYM0+7RpjsMyAZ7puiwLss1l4hEtx DofsLQsb66TyGEF3cCyoDfiSsM5k6sdkIQwe0BSOANlKHvTrWg2/9z6o66TOVy+N t3FWF00RstumB22vTRETUZOahaW14zJz/gpANlkfJbBtd1gP7OQhm7M27UtT6+Av /ch0X3qdjTnCzJcYy97B95ccHnKQPy1VRttGcukhl4RzQotSVR3wKW/e0alS3XgG bD4d7oVFYTTOWCee8Xh32n0hh1HXrFQ5zNFCn1megLvG7LbuILdqJSU9RitFCpyx 4jbD4q4WOuS2vpXzRNqv1v0FHI8nlLVV715qJfkAIicWDzAHgXj1MA0rqmM8ZfMX Z6qnBb0qJXRgjUYaQDxasLAB =vyxQ -----END PGP SIGNATURE-----
Hi Jussi, Could you cherry-pick [1] into 1.11 in sid? That would help the ongoing python3.14 transition, and a minimum fix would be preferred since the 1.12 release may have regressions and have some trouble transitioning to testing, see e.g. [2]. Cheers, Emilio [1] https://github.com/mesonbuild/meson/commit/f2d0d089b5c6084f9b0aa2c51166f90efc6d357d [2] https://qa.debian.org/excuses.php?experimental=1&package=meson
Dch will not allow me to create 1.11.1-3 because there is already a newer version in experimental. It says that -b is possible, but it will not tell you what it would actually do (only "e.g. when backporting") and this issue is not properly documented from what I can tell. Or at least search engines don't find it.
You should do it on top of 1.11.1-2, not on top of 1.12.0~rc1-1. If you're using git, you can make a branch at that point, otherwise you can just unpack 1.11.1-2 and work on top of it. Cheers, Emilio
1682s 30/6 boosttest:Boost Python3 FAIL 0.06s killed by signal 11 SIGSEGV See e.g.: https://ci.debian.net/data/autopkgtest/testing/arm64/m/meson/72968629/log.gz https://tracker.debian.org/pkg/meson Cheers, Emilio
I tried to replicate this on an aarch64 container and could not make it fail. It's using sid, though, but it should not matter. No idea what could be causing this.