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

← Release team

Where it stands

tests failed, ours is 2.3.3+dfsg-4.1+poy315.2, waiting on matplotlib, pyqt5, pyreadstat, rpy2, scipy, sqlalchemy, statsmodels.

Rebuilding it releases 17 packages waiting on it, as this stage last counted.

What was sent

aborted, 2.3.3+dfsg-4+py315.1, as work request 1273563, which ended in work request 1273565.

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

Sent before this one: 2.3.3+dfsg-3+py315.1. A version that was sent is spent, whatever came of it.

What is known

QuestionAnswerSaid byAs of
Why did the build fail? archive-dependency
Built against the archive's copy of a dependency we have rebuilt. The ordering has not reached it, so this is not the package's own fault.
python3-brotli 1.2.0-3.1+py315.2: we publish 1.2.0-4+py315.1
python3-pyqt5 5.15.11+dfsg-5: we publish 5.15.11+dfsg-6+py315.1
python3-zopfli 0.4.3-1+py315.1: we publish 0.4.3-2+py315.1
deps/11 not dated
Which known interpreter change does this failure show? module-not-importable
a dependency was not importable. Nothing here says the interpreter caused this. An import that failed usually means the testbed was assembled before the dependency had been rebuilt, which is ours to fix by running it again.
ModuleNotFoundError: No module named 'docutils'
could not import docutils
deps/11 not dated
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-09-10
ci.debian.net not dated
does the release team track this? dependency level 4
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
release.debian.org, from their ben tracker 2026-09-16 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
#1144864 pandas: FTBFS building against python 3.15
the BTS usertag not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
2.3.3+dfsg-4.1+poy315.2 arm64 test fail rebuilt named none 2026-09-15 12:30
2.3.3+dfsg-4.1+poy315.2 amd64 test fail rebuilt named none 2026-09-15 11:11
2.3.3+dfsg-4 arm64 test fail the archive's (reference arm) named none 2026-09-15 09:23
2.3.3+dfsg-4 amd64 test fail the archive's (reference arm) named none 2026-09-15 09:23
2.3.3+dfsg-4.1+poy315.2 arm64 build pass unknown not read yet 2026-09-15 11:21
2.3.3+dfsg-4.1+poy315.2 amd64 build pass unknown not read yet 2026-09-15 10:20
2.3.3+dfsg-4.1+poy315.2 all build pass unknown not read yet 2026-09-15 10:28
2.3.3+dfsg-4+py315.1 arm64 build fail unknown not read yet 2026-09-15 03:45
2.3.3+dfsg-4+py315.1 amd64 build fail unknown not read yet 2026-09-15 03:29
2.3.3+dfsg-4+py315.1 all build fail unknown not read yet 2026-09-15 03:48
2.3.3+dfsg-3.1+py315.7 arm64 test fail rebuilt named none 2026-08-18 18:55
2.3.3+dfsg-3.1+py315.7 amd64 test fail rebuilt named none 2026-08-18 18:05
2.3.3+dfsg-3.1+py315.7 arm64 build pass unknown not read yet 2026-08-18 17:17
2.3.3+dfsg-3.1+py315.7 amd64 build pass unknown not read yet 2026-08-18 16:56
2.3.3+dfsg-3.1+py315.7 all build pass unknown not read yet 2026-08-18 17:05
2.3.3+dfsg-3.1+py315.1 amd64 build fail unknown not read yet 2026-08-17 19:42
2.3.3+dfsg-3+py315.1 arm64 build fail unknown not read yet 2026-08-17 18:17
2.3.3+dfsg-3+py315.1 amd64 build fail unknown not read yet 2026-08-17 17:56
2.3.3+dfsg-3+py315.1 all build fail unknown not read yet 2026-08-17 17:59
2.3.3+dfsg-3 arm64 test fail the archive's (reference arm) named none 2026-08-16 03:08
2.3.3+dfsg-3 amd64 test fail the archive's (reference arm) named none 2026-08-16 03:08
2.3.3+dfsg-3+py315.1 all build fail unknown not read yet 2026-08-16 08:04