Debian Release Management

Transitions → gtkmm2.4 (auto)

Parameters:
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:
Dependency level 1 (build logs RC bugs)amd64arm64armelarmhfi386mips64elppc64elriscv64s390x
gtkmm2.4[build logs] (1:2.24.5-5.2) [ma:same]✔✔✔✔✔✔✔✔✔
Dependency level 2 (build logs RC bugs)amd64arm64armelarmhfi386mips64elppc64elriscv64s390x
gbgoffice[build logs] (1.4-12)✔✔✔✔✔✔✔✔✔
gelemental[build logs] (2.0.2-1.1) [ma:same]✔✔✔✔✔✔✔✔✔
granule[build logs] (1.4.0-7-10)✔✔✔✔✔✔✔✔✔
mangler (sid only)[build logs] (1.2.5-5.1) [ma:same]✔✔✔✔✔✔✔✔✔
nitrogen[build logs] (1.6.1-2)✔✔✔✔✔✔✔✔✔
opencfu[build logs] (4.0.0+dfsg-2)✔✔✔✔✔✔✔✔✔
pavumeter[build logs] (0.9.3-4)✔✔✔✔✔✔✔✔✔
Collisions:
  • auto-alsa-lib through mangler
  • auto-glib2.0 through gbgoffice, gelemental, granule, gtkmm2.4, mangler, nitrogen, opencfu, pavumeter
  • auto-glibmm2.4 through gbgoffice, gelemental, granule, gtkmm2.4, mangler, nitrogen, opencfu, pavumeter
  • auto-gtk+2.0 through gbgoffice, gelemental, granule, gtkmm2.4, mangler, nitrogen, opencfu, pavumeter
  • auto-libassa through granule
  • auto-libtirpc through granule
  • auto-opencv through opencfu
  • libglib2.0-0t64 through gbgoffice, gelemental, granule, gtkmm2.4, mangler, nitrogen, opencfu, pavumeter