Debian Release Management

Transitions → benchmark (auto)

Parameters:

Affected: .depends ~ /\b(libbenchmark1\.9\.1|libbenchmark1\.8\.3)\b/
Good: .depends ~ /\b(libbenchmark1\.9\.1)\b/
Bad: .depends ~ /\b(libbenchmark1\.8\.3)\b/

Notes:

This tracker was setup by a very simple automated tool.  The tool may not be very smart...

Extra information (collected entirely from testing!):
 * can-smooth-update: maybe

Filter by status: good partial bad unknown

ignore packages that are not in testing

Dependency level 1 (build logs RC bugs)		amd64	arm64	armel	armhf	i386	mips64el	ppc64el	riscv64	s390x
benchmark	[build logs] (1.9.1-1) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔
Dependency level 2 (build logs RC bugs)		amd64	arm64	armel	armhf	i386	mips64el	ppc64el	riscv64	s390x
pytorch	[build logs] (2.5.1+dfsg-4) [ma:same]	✘	✘					✘	✘	✘
pytorch-cuda (sid only)	[build logs] (2.5.1+dfsg-4) [ma:same]	✘	✘					✘
ros2-performance-test-fixture	[build logs] (0.3.1-1) [ma:same]	✘	✘	✘	✘	✘	✘	✘	✘	✘

Collisions:

auto-cpp-httplib through pytorch, pytorch-cuda
auto-fmtlib through pytorch, pytorch-cuda
auto-protobuf through pytorch, pytorch-cuda
auto-upperlimit-python3 through pytorch, pytorch-cuda
numpy2 through pytorch, pytorch-cuda
python3.13-default through pytorch, pytorch-cuda