bumpversion

1.0.1-1.2 in the archive

Where it stands

built, ours is 1.0.1-1.3~+py315.3.
ahead of the archive (built from a source sid does not have)

Nothing recorded is waiting on this one.

published, 1.0.1-1.2+py315.1, as work request 1169217, which ended in work request 1169231.

Which turned out to be build-failed: the build failed: work request 1169231.

Sent before this one: 1.0.1-1.2+py315.2. A version that was sent is spent, whatever came of it.

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
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. E ModuleNotFoundError: No module named 'sre_constants' could not import sre_constants	deps/11	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 #1148922 bumpversion: FTBFS against python 3.15rc2	the BTS usertag	not dated

Version	Arch	Kind	Result	Binaries	Interpreters	Closure	Finished
`1.0.1-1.3~+py315.3`	amd64	test	pass	rebuilt	named none	—	2026-09-23 16:47
`1.0.1-1.3~+py315.3`	all	build	pass	unknown	not read yet	—	2026-09-23 16:45
`1.0.1-1.2+py315.2`	all	build	fail	unknown	not read yet	—	2026-08-27 20:27
`1.0.1-1.2`	amd64	test	pass	the archive's (reference arm)	named none	—	2026-08-27 03:06