Debian Release Management

Transitions → libieee1284 (auto)

Parameters:

Affected: .depends ~ /\b(libieee1284\-3\-dev|libieee1284\-3t64|libieee1284\-3)\b/
Good: .depends ~ /\b(libieee1284\-3\-dev|libieee1284\-3t64)\b/
Bad: .depends ~ /\b(libieee1284\-3)\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
libieee1284	[build logs] (0.2.11-14.1) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔
Dependency level 2 (build logs RC bugs)		amd64	arm64	armel	armhf	i386	mips64el	ppc64el	riscv64	s390x
libsigrok	[build logs] (0.5.2-5.1) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔
sane-backends	[build logs] (1.2.1-7) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔
scummvm	[build logs] (2.8.1+dfsg-1)	✔	✔	✔	✔	✔	✔	✔	✔	✔

Collisions:

auto-alsa-lib through scummvm
auto-curl through sane-backends, scummvm
auto-flac through scummvm
auto-glib2.0 through libsigrok, sane-backends, scummvm
auto-glibmm2.4 through libsigrok
auto-gtk+3.0 through scummvm
auto-libgphoto2 through sane-backends
auto-libpng1.6 through sane-backends, scummvm
auto-libsigrok through libsigrok
auto-libzip through libsigrok
auto-net-snmp through sane-backends
auto-poppler through sane-backends
auto-zlib through scummvm
libglib2.0-0t64 through libsigrok, sane-backends, scummvm