pyqt5

5.15.11+dfsg-6 in the archive, ships a compiled extension

Where it stands

built, ours is 5.15.11+dfsg-7+py315.d.2.
ahead of the archive (built from a source sid does not have)

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

published, 5.15.11+dfsg-6+py315.d.1, as work request 1298585.

Question	Answer	Said by	As of
does the release team track this?	dependency level 3 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 unknown, arm64 unknown, armhf unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown	release.debian.org, from their ben tracker	2026-09-17 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 #1144994 (done) pyqt5: FTBFS building against python 3.15	the BTS usertag	not dated

Version	Arch	Kind	Result	Binaries	Interpreters	Closure	Finished
`5.15.11+dfsg-6`	arm64	test	pass	the archive's (reference arm)	named none	—	2026-09-17 03:37
`5.15.11+dfsg-6`	amd64	test	pass	the archive's (reference arm)	named none	—	2026-09-17 03:37
`5.15.11+dfsg-6+py315.d.1`	arm64	build	fail	unknown	not read yet	—	2026-09-17 07:38
`5.15.11+dfsg-6+py315.d.1`	amd64	build	fail	unknown	not read yet	—	2026-09-17 07:22
`5.15.11+dfsg-6+py315.d.1`	all	build	fail	unknown	not read yet	—	2026-09-17 07:08