2.1-2 in the archive, ships a compiled extension
pending,
ours is 2.1-1.1+py315.2.
archive has moved on; rebuild before believing this
Nothing recorded is waiting on this one.
aborted,
2.1-2+py315.1,
as work request 1300321,
which ended in work request 1300351.
Which turned out to be publish-refused: the workflow ended: publish-refused, work request 1300351.
Sent before this one:
2.1-1+py315.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| do Debian's own tests pass? |
archive tests fail
Debian's own tests for this package fail in unstable, so this failure is not the new interpreter's doing. debci answers about the source rather than about the version we rebuilt, which is why the date its run happened is shown. amd64, arm64, last run 2026-08-21 |
ci.debian.net | not dated |
| does the release team track this? |
dependency level 10
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong. amd64 bad, arm64 bad, armhf bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-17 04:49 UTC |
| has anybody reported this under the usertag? |
1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks #1143310 gammapy: FTBFS: E ImportError: cannot import name 'pixel_scale_angle_at_skycoord' from 'regions._utils.wcs_helpers' (/usr/lib/python3/dist-packages/regions/_utils/wcs_helpers.py) |
the BTS usertag | not dated |
No run in this phase yet — it is pending.