Debian Release Management

Transitions → source-highlight (auto)

Parameters:

Affected: .depends ~ /\b(libsource\-highlight\-common|libsource\-highlight\-dev|libsource\-highlight4t64|source\-highlight|libsource\-highlight4v5)\b/
Good: .depends ~ /\b(libsource\-highlight\-common|libsource\-highlight\-dev|libsource\-highlight4t64|source\-highlight)\b/
Bad: .depends ~ /\b(libsource\-highlight4v5)\b/

Notes:

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

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
biosyntax	[build logs] (1.0.0b-6) [arch:all]	✔	✔	✔	✔	✔	✔	✔	✔	✔
ruby-mizuho	[build logs] (0.9.20+dfsg-1.1) [arch:all]	✔	✔	✔	✔	✔	✔	✔	✔	✔
source-highlight	[build logs] (3.1.9-4.3) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔
Dependency level 2 (build logs RC bugs)		amd64	arm64	armel	armhf	i386	mips64el	ppc64el	riscv64	s390x
gdb	[build logs] (13.2-1)	✔	✔	✔	✔	✔	✔	✔	✔	✔
licenseutils	[build logs] (0.0.9-7)	✔	✔	✔	✔	✔	✔	✔	✔	✔
nvidia-cuda-toolkit	[build logs] (12.0.1-5) [ma:same]	✔	✔					✔

Collisions:

auto-alsa-lib through nvidia-cuda-toolkit
auto-curl through licenseutils
auto-e2fsprogs through nvidia-cuda-toolkit
auto-elfutils through gdb, nvidia-cuda-toolkit
auto-glib2.0 through licenseutils, nvidia-cuda-toolkit
auto-gtk+2.0 through nvidia-cuda-toolkit
auto-libpng1.6 through licenseutils, nvidia-cuda-toolkit
auto-python3.11 through gdb, nvidia-cuda-toolkit
auto-rdma-core through nvidia-cuda-toolkit
auto-readline through gdb, nvidia-cuda-toolkit
auto-zlib through gdb, nvidia-cuda-toolkit
libglib2.0-0t64 through licenseutils, nvidia-cuda-toolkit
python3.12-default through gdb, nvidia-cuda-toolkit