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

← Failures

Where it stands

build failed, ours is 1.35.0-4+py315.d.1.

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

What was sent

aborted, 1.35.0-4+py315.d.1, as work request 1309602, which ended in work request 1309604.

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

What is known

QuestionAnswerSaid byAs of
Why did the build fail? dependencies-unsatisfied
apt could not assemble the build chroot, so the build never started. Nothing about the package was tried, and retrying it changes nothing.
deps/11 not dated
does the release team track this? dependency level 9
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-10-11 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
#1146573 (done) pyresample: FTBFS due to test failures
the BTS usertag not dated

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
1.35.0-4 arm64 test fail the archive's (reference arm) named none — 2026-09-19 21:44
1.35.0-4 amd64 test fail the archive's (reference arm) named none — 2026-09-19 21:44
1.35.0-4+py315.d.1 arm64 build fail unknown not read yet — 2026-09-20 01:51
1.35.0-4+py315.d.1 amd64 build fail unknown not read yet — 2026-09-20 01:51
1.35.0-4+py315.d.1 all build fail unknown not read yet — 2026-09-20 01:50