Debian Release Management

Transitions → wireshark (auto)

Parameters:

Affected: .depends ~ /\b(libwireshark17t64|libwiretap14t64|libwsutil15t64|libwireshark17|libwiretap14|libwsutil15)\b/
Good: .depends ~ /\b(libwireshark17t64|libwiretap14t64|libwsutil15t64)\b/
Bad: .depends ~ /\b(libwireshark17|libwiretap14|libwsutil15)\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
wireshark	[build logs] (4.2.2-1.1) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔
Dependency level 2 (build logs RC bugs)		amd64	arm64	armel	armhf	i386	mips64el	ppc64el	riscv64	s390x
libvirt	[build logs] (10.2.0-1) [ma:same]	✔	✔	✔	✔	✔	✔	✔	✔	✔

Collisions:

auto-c-ares through wireshark
auto-curl through libvirt
auto-glib2.0 through libvirt, wireshark
auto-gnutls28 through libvirt, wireshark
auto-libpcap through libvirt, wireshark
auto-libselinux through libvirt
auto-libsmi through wireshark
auto-libssh2 through libvirt
auto-libtirpc through libvirt
auto-lxc through libvirt
auto-nghttp3 through wireshark
auto-parted through libvirt
auto-qt6-base through wireshark
auto-readline through libvirt
auto-spandsp through wireshark
auto-xen through libvirt
auto-zlib through wireshark
fuse-to-fuse3 through libvirt
libglib2.0-0t64 through libvirt, wireshark