10.10-1 in the archive, ships a compiled extension
pending,
ours is 10.9-2+py315.1.
archive has moved on; rebuild before believing this
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Nothing recorded is waiting on this one.
aborted,
10.9-3+py315.1,
as work request 1431291,
which ended in work request 1431293.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1431293.
Sent before this one:
9.5-6+py315.1, 9.5-6+py315.2, 9.5-6+py315.3, 9.5-6+py315.4, 10.9-1+py315.1, 10.9-2+py315.1.
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. arm64 |
tests.reproducible-builds.org | not dated |
| does Debian's own test suite pass? |
neutral
Debian runs no autopkgtest for this, so we have no independent baseline: nothing here distinguishes a failure this interpreter caused from one the package always had |
ci.debian.net | not dated |
No run in this phase yet — it is pending.