Package: dh-python Version: 7.20260623 Severity: serious Control: affects -1 python3-bornagain src:bornagain
Unstable: Package: python3-bornagain Version: 24.1+ds3-1 Depends: ..., libpython3.14 (>= 3.14.1), ... Testing: Package: python3-bornagain Version: 23.0-7 Depends: ..., libpython3.13 (>= 3.13.0~rc3), ... This results in test failures both when testing for python3-defaults migration and for bornagain migration, since using libpython in a different version of the python interpreter segfaults. The problem is not limited to autopkgtests, the lack of package dependencies also means the packages can migrate at different times to testing once no blocker remains for one package. It's even worse when not caught by the autopkgtest: kicad would be an example for a package with a libpython dependency that does not seem to be tested by the autopkgtest. In addition to testing migration, such a missing dependency could also cause problems when upgrading to a new stable release. A libpython3.14 dependency like in python3-bornagain or kicad should additionally result in dependencies python3 (>= 3.14~), python3 (<< 3.15)
