Transition: libpappsomspp (auto)

Transitions → libpappsomspp (auto)

Parameters:

Affected: .depends ~ /\b(libpappsomspp\-core\-dev|libpappsomspp\-core0|libpappsomspp\-gui\-dev|libpappsomspp\-gui0|libpappsomspp\-dev|libpappsomspp\-widget\-dev|libpappsomspp\-widget0|libpappsomspp0)\b/
Good: .depends ~ /\b(libpappsomspp\-core\-dev|libpappsomspp\-core0|libpappsomspp\-gui\-dev|libpappsomspp\-gui0)\b/
Bad: .depends ~ /\b(libpappsomspp\-dev|libpappsomspp\-widget\-dev|libpappsomspp\-widget0|libpappsomspp0)\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: no - libpappsomspp-dev is not in libs or oldlibs

Filter by status: good partial bad unknown

ignore packages that are not in testing

Dependency level 1 (build logs RC bugs)		amd64	arm64	armhf	i386	ppc64el	riscv64	s390x
libpappsomspp	[build logs] (0.11.0-1) [ma:same]	⁈	⁈	⁈	⁈	⁈	⁈	⁈
Dependency level 2 (build logs RC bugs)		amd64	arm64	armhf	i386	ppc64el	riscv64	s390x
libxpertmass	[build logs] (1.3.0-1) [ma:same]	⁈	⁈	⁈	⁈	⁈	⁈	⁈
Dependency level 3 (build logs RC bugs)		amd64	arm64	armhf	i386	ppc64el	riscv64	s390x
massxpert2	[build logs] (8.5.0-2)	✘	✘	✘	✘	✘	✘	✘
minexpert2	[build logs] (9.6.0-1)	✘	✘	✘	✘	✘	✘	✘

Collisions:

auto-libxpertmass through libxpertmass, massxpert2, minexpert2

Debian Release Management

Transitions → libpappsomspp (auto)