1.23.2+dfsg-6 in the archive, ships a compiled extension
build failed,
ours is 1.23.2+dfsg-6+py315.1,
waiting on re2.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev
Nothing recorded is waiting on this one.
build_failed,
1.23.2+dfsg-6+py315.1.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
unknown
The log was read and says nothing this tool recognises. These are the failures somebody has to look at. |
deps/11 | not dated |
| was the interpreter under test installed? |
no
its chroot had a different Python installed instead, so its failure is about whatever that one is: these take their interpreter from the default rather than from pybuild python3.14_3.14.7-1 |
the build log's installed set | not dated |
| 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 |
tests.reproducible-builds.org | not dated |
| 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 #1133592 onnxruntime: ftbfs with GCC-16 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.23.2+dfsg-6
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-12 09:28 |
1.23.2+dfsg-6
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-12 09:28 |
1.23.2+dfsg-6+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-12 11:21 |