Shortcuts

/
focus the search box
Escape
leave the search, or close a menu or this
r
cycle the refresh interval
t
cycle the theme
?
this list

← In progress

Where it stands

build failed, ours is 7.4.1-1.2+py315.d.1.
python3-dev-only
build-depend on python3-all-dev instead of python3-dev

Nothing recorded is waiting on this one.

What was sent

aborted, 7.4.1-1.2+py315.d.1, as work request 1288011, which ended in work request 1288015.

Which turned out to be build-failed: the workflow ended: build-failed, work request 1288015.

What is known

QuestionAnswerSaid byAs 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
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
#1133619 regina-normal: ftbfs with GCC-16
the BTS usertag not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
7.4.1-1.2 arm64 test fail the archive's (reference arm) named none 2026-09-16 09:19
7.4.1-1.2 amd64 test fail the archive's (reference arm) named none 2026-09-16 09:19
7.4.1-1.2+py315.d.1 arm64 build fail unknown not read yet 2026-09-16 15:07
7.4.1-1.2+py315.d.1 amd64 build fail unknown not read yet 2026-09-16 15:06
7.4.1-1.2+py315.d.1 all build fail unknown not read yet 2026-09-16 15:06