202603.4-2 in the archive, ships a compiled extension
pending,
ours is 202603.4-1.1+py315.6.
archive has moved on; rebuild before believing this
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Rebuilding it releases 2 packages waiting on it, as this stage last counted.
aborted,
202603.4-2+py315.1,
as work request 1243472,
which ended in work request 1243474.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1243474.
Sent before this one:
202603.4-1+py315.1, 202603.4-1+py315.2.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does the archive build this version? |
archive ftbfs
Debian's own rebuild of the version the archive carries fails too, so this failure is not the new interpreter's doing. It still blocks the transition: nobody can rebuild it until that is fixed. amd64 arm64 |
tests.reproducible-builds.org | not dated |
No run in this phase yet — it is pending.