On Mon, Jul 06, 2026 at 12:56:29PM +0300, Jussi Pakkanen wrote:
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 SIGSEGVThe 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.
-- WBR, wRAR
signature.asc
Description: PGP signature
