[Debian-astro-maintainers] Bug#1141423: casacore: libcasa-python3-9 and python3-casacore need to migrate together

[Graham Inggs]

Source: casacore
Version: 3.8.0-5
Severity: serious
X-Debbugs-Cc: debian-python at lists.debian.org
User: debian-python at lists.debian.org
Usertags: python3.14

Hi Maintainer

casacore is part of the 'Python 3.14 as default' transition [1].
casacore was rebuilt in dependency level 2, and python-casacore was
rebuilt in dependency level 3.  Both rebuilds were done by binNMU.

This is the first Python transition where autopkgtests are being run
for binNMUs.

Right now, the rebuilt casacore is attempting to migrate, but it is
blocked by a failing autopkgtest triggered in python-casacore [2].

casacore/amd64 (3.8.0-5 to 3.8.0-5)

Migration status for casacore/amd64 (3.8.0-5 to 3.8.0-5): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:

It is the same for other architectures, except armhf, where
autopkgtests are not currently blocking and the rebuild has already
migrated.

I think the reason for this is that python3-casacore has Depends:
python3 (<< 3.15), python3 (>= 3.14~), so britney knows that
python-casacore needs to migrate together with the updated
python3-defaults, while libcasa-python3-9 (from src:casacore) only has
Depends: libpython3.14 (>= 3.14.1), which is already in testing, so
migration is being attempted.

One could come up with a versioned Depends/Breaks scheme between
libcasa-python3-9 and python3-casacore, but I think that if
libcasa-python3-9 were to also Depends: python3 (<< 3.15), python3 (>=
3.14~), then britney would know that libcasa-python3-9,
python3-casacore and python3-defaults all need to migrate together.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.14-default.html
[2] https://release.debian.org/britney/update_excuses.html#casacore/amd64