Bug#1091620: src:python-xarray: fails to migrate to testing for too long: Build-Depends on numba which is RC buggy

[Paul Gevers]

Source: python-xarray
Version: 2024.09.0-1
Severity: serious
Control: close -1 2024.11.0-1
Tags: sid trixie
User: release.debian.org at packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-xarray has been trying to migrate 
for 34 days [2], hence this bug report. The current output of the 
migration software for this package is copied to the bottom of this 
report and should list the reason why the package is blocked. It's 
blocked by src:numba which has been removed from testing because of its 
RC bugs. Because the Build-Depends on packages from src:numba are only 
listed as either !nocheck or !nodoc, the autoremoval of numba from 
testing was allowed. Please either help the maintainer of numba to fix 
the RC issues, or drop the dependencies for now.

If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or its 
(reverse-)dependencies. We expect maintainers to fix issues that hamper 
the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.

This bug submission immediately closes the bug with the version in 
unstable, so if that version or a later version migrates, this bug will 
no longer affect testing. This bug is also tagged to only affect sid and 
trixie, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated and has only been sent 
manually. If you have any comments with regards to the content or the 
process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=python-xarray

Current text from [2]:
Migration status for python-xarray (2024.09.0-1 to 2024.11.0-1): 
BLOCKED: Cannot migrate due to another item, which is blocked (please 
check which dependencies are stuck)
Issues preventing migration:
∙ ∙ Build-Depends(-Arch): python-xarray numba (not considered)
∙ ∙ Invalidated by build-dependency
Additional info:
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/p/python-xarray.html
∙ ∙ autopkgtest for python-xarray/2024.11.0-1: amd64: No tests, 
superficial or marked flaky ♻ (reference ♻), arm64: No tests, 
superficial or marked flaky ♻ (reference ♻), armel: No tests, 
superficial or marked flaky ♻ (reference ♻), armhf: No tests, 
superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial 
or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or 
marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked 
flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ 
(reference ♻)
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙ 
∙ 34 days old (needed 5 days)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20241228/f513ad13/attachment.sig>