Generated: 2024.01.06 19:04:18 +0000

• -antic (0.2.5+ds-1 to -)
  • Migration status for -antic (0.2.5+ds-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• -firmware-microbit-micropython (1.0.1-4 to -)
  • Migration status for -firmware-microbit-micropython (1.0.1-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -haskell-diagrams (1.4.0.1-1 to -)
  • Migration status for -haskell-diagrams (1.4.0.1-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -mu-editor (1.0.3+dfsg-6 to -)
  • Migration status for -mu-editor (1.0.3+dfsg-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ndcube (2.0.3-1 to -)
  • Migration status for -ndcube (2.0.3-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -openstack-trove (1:20.0.0-2 to -)
  • Migration status for -openstack-trove (1:20.0.0-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -python-cassandra-driver (3.28.0-1 to -)
  • Migration status for -python-cassandra-driver (3.28.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -python-uflash (1.2.4+dfsg-10 to -)
  • Migration status for -python-uflash (1.2.4+dfsg-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -specutils (1.12.0-1 to -)
  • Migration status for -specutils (1.12.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• aardvark-dns/s390x (1.4.0-5 to 1.4.0-5)
  • Migration status for aardvark-dns/s390x (1.4.0-5 to 1.4.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aardvark-dns/s390x has unsatisfiable dependency
• abiword/armel (3.0.5~dfsg-3.2 to 3.0.5~dfsg-3.2)
  • Migration status for abiword/armel (3.0.5~dfsg-3.2 to 3.0.5~dfsg-3.2): Will attempt migration (Any information below is purely informational)
• abiword/armhf (3.0.5~dfsg-3.2 to 3.0.5~dfsg-3.2)
  • Migration status for abiword/armhf (3.0.5~dfsg-3.2 to 3.0.5~dfsg-3.2): Will attempt migration (Any information below is purely informational)
• abiword/mips64el (3.0.5~dfsg-3.2 to 3.0.5~dfsg-3.2)
  • Migration status for abiword/mips64el (3.0.5~dfsg-3.2 to 3.0.5~dfsg-3.2): Will attempt migration (Any information below is purely informational)
• adolc/armel (2.7.2-6 to 2.7.2-6)
  • Migration status for adolc/armel (2.7.2-6 to 2.7.2-6): Will attempt migration (Any information below is purely informational)
• akonadi-mime/s390x (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-mime/s390x (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-notes/s390x (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-notes/s390x (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-search/s390x (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-search/s390x (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• alglib/armel (4.0.0-1 to 4.0.0-1)
  • Migration status for alglib/armel (4.0.0-1 to 4.0.0-1): Will attempt migration (Any information below is purely informational)
• alglib/s390x (4.0.0-1 to 4.0.0-1)
  • Migration status for alglib/s390x (4.0.0-1 to 4.0.0-1): Will attempt migration (Any information below is purely informational)
• alkimia/s390x (8.1.2-2 to 8.1.2-2)
  • Migration status for alkimia/s390x (8.1.2-2 to 8.1.2-2): Will attempt migration (Any information below is purely informational)
• allegro4.4/s390x (2:4.4.3.1-4 to 2:4.4.3.1-4)
  • Migration status for allegro4.4/s390x (2:4.4.3.1-4 to 2:4.4.3.1-4): Will attempt migration (Any information below is purely informational)
• allegro5/s390x (2:5.2.9.0+dfsg-1 to 2:5.2.9.0+dfsg-1)
  • Migration status for allegro5/s390x (2:5.2.9.0+dfsg-1 to 2:5.2.9.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• alsaequal/s390x (0.6-8 to 0.6-8)
  • Migration status for alsaequal/s390x (0.6-8 to 0.6-8): Will attempt migration (Any information below is purely informational)
• aml/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for aml/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• anthy/s390x (1:0.4-2 to 1:0.4-2)
  • Migration status for anthy/s390x (1:0.4-2 to 1:0.4-2): Will attempt migration (Any information below is purely informational)
• antlr4-cpp-runtime/s390x (4.9+dfsg-3 to 4.9+dfsg-3)
  • Migration status for antlr4-cpp-runtime/s390x (4.9+dfsg-3 to 4.9+dfsg-3): Will attempt migration (Any information below is purely informational)
• aoflagger/s390x (3.4.0-2 to 3.4.0-2)
  • Migration status for aoflagger/s390x (3.4.0-2 to 3.4.0-2): Will attempt migration (Any information below is purely informational)
• aom/mips64el (3.7.1-1 to 3.7.1-1)
  • Migration status for aom/mips64el (3.7.1-1 to 3.7.1-1): Will attempt migration (Any information below is purely informational)
• aom/s390x (3.7.1-1 to 3.7.1-1)
  • Migration status for aom/s390x (3.7.1-1 to 3.7.1-1): Will attempt migration (Any information below is purely informational)
• apache2/armel (2.4.58-1 to 2.4.58-1)
  • Migration status for apache2/armel (2.4.58-1 to 2.4.58-1): Will attempt migration (Any information below is purely informational)
• apache2/i386 (2.4.58-1 to 2.4.58-1)
  • Migration status for apache2/i386 (2.4.58-1 to 2.4.58-1): Will attempt migration (Any information below is purely informational)
• apache2/s390x (2.4.58-1 to 2.4.58-1)
  • Migration status for apache2/s390x (2.4.58-1 to 2.4.58-1): Will attempt migration (Any information below is purely informational)
• apertium-lex-tools/s390x (0.4.2-2 to 0.4.2-2)
  • Migration status for apertium-lex-tools/s390x (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• apitrace/armel (11.1+repack-1.2 to 11.1+repack-1.2)
  • Migration status for apitrace/armel (11.1+repack-1.2 to 11.1+repack-1.2): Will attempt migration (Any information below is purely informational)
• apitrace/mips64el (11.1+repack-1.2 to 11.1+repack-1.2)
  • Migration status for apitrace/mips64el (11.1+repack-1.2 to 11.1+repack-1.2): Will attempt migration (Any information below is purely informational)
• apitrace/s390x (11.1+repack-1.2 to 11.1+repack-1.2)
  • Migration status for apitrace/s390x (11.1+repack-1.2 to 11.1+repack-1.2): Will attempt migration (Any information below is purely informational)
• apparmor/mips64el (3.0.12-1 to 3.0.12-1)
  • Migration status for apparmor/mips64el (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
• apparmor/s390x (3.0.12-1 to 3.0.12-1)
  • Migration status for apparmor/s390x (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
• appmenu-gtk-module/mips64el (0.7.6-2.1 to 0.7.6-2.1)
  • Migration status for appmenu-gtk-module/mips64el (0.7.6-2.1 to 0.7.6-2.1): Will attempt migration (Any information below is purely informational)
• appmenu-gtk-module/s390x (0.7.6-2.1 to 0.7.6-2.1)
  • Migration status for appmenu-gtk-module/s390x (0.7.6-2.1 to 0.7.6-2.1): Will attempt migration (Any information below is purely informational)
• apr-util/mips64el (1.6.3-1 to 1.6.3-1)
  • Migration status for apr-util/mips64el (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
• apr-util/s390x (1.6.3-1 to 1.6.3-1)
  • Migration status for apr-util/s390x (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
• apr/mips64el (1.7.2-3 to 1.7.2-3)
  • Migration status for apr/mips64el (1.7.2-3 to 1.7.2-3): Will attempt migration (Any information below is purely informational)
• apr/s390x (1.7.2-3 to 1.7.2-3)
  • Migration status for apr/s390x (1.7.2-3 to 1.7.2-3): Will attempt migration (Any information below is purely informational)
• apriltag/mips64el (3.3.0-2 to 3.3.0-2)
  • Migration status for apriltag/mips64el (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
• apriltag/s390x (3.3.0-2 to 3.3.0-2)
  • Migration status for apriltag/s390x (3.3.0-2 to 3.3.0-2): Will attempt migration (Any information below is purely informational)
• apulse/mips64el (0.1.13-2 to 0.1.13-2)
  • Migration status for apulse/mips64el (0.1.13-2 to 0.1.13-2): Will attempt migration (Any information below is purely informational)
• apulse/s390x (0.1.13-2 to 0.1.13-2)
  • Migration status for apulse/s390x (0.1.13-2 to 0.1.13-2): Will attempt migration (Any information below is purely informational)
• aravis/mips64el (0.8.28-1 to 0.8.28-1)
  • Migration status for aravis/mips64el (0.8.28-1 to 0.8.28-1): Will attempt migration (Any information below is purely informational)
• aravis/s390x (0.8.28-1 to 0.8.28-1)
  • Migration status for aravis/s390x (0.8.28-1 to 0.8.28-1): Will attempt migration (Any information below is purely informational)
• argon2/mips64el (0~20190702+dfsg-4 to 0~20190702+dfsg-4)
  • Migration status for argon2/mips64el (0~20190702+dfsg-4 to 0~20190702+dfsg-4): Will attempt migration (Any information below is purely informational)
• argon2/s390x (0~20190702+dfsg-4 to 0~20190702+dfsg-4)
  • Migration status for argon2/s390x (0~20190702+dfsg-4 to 0~20190702+dfsg-4): Will attempt migration (Any information below is purely informational)
• aria2/armel (1.37.0+debian-1 to 1.37.0+debian-1)
  • Migration status for aria2/armel (1.37.0+debian-1 to 1.37.0+debian-1): Will attempt migration (Any information below is purely informational)
• aria2/mips64el (1.37.0+debian-1 to 1.37.0+debian-1)
  • Migration status for aria2/mips64el (1.37.0+debian-1 to 1.37.0+debian-1): Will attempt migration (Any information below is purely informational)
• aria2/s390x (1.37.0+debian-1 to 1.37.0+debian-1)
  • Migration status for aria2/s390x (1.37.0+debian-1 to 1.37.0+debian-1): Will attempt migration (Any information below is purely informational)
• aribb24/mips64el (1.0.3-2 to 1.0.3-2)
  • Migration status for aribb24/mips64el (1.0.3-2 to 1.0.3-2): Will attempt migration (Any information below is purely informational)
• aribb24/s390x (1.0.3-2 to 1.0.3-2)
  • Migration status for aribb24/s390x (1.0.3-2 to 1.0.3-2): Will attempt migration (Any information below is purely informational)
• armci-mpi/s390x (0.3.1~beta-7 to 0.3.1~beta-7)
  • Migration status for armci-mpi/s390x (0.3.1~beta-7 to 0.3.1~beta-7): Will attempt migration (Any information below is purely informational)
• arpack++/mips64el (2.3-10 to 2.3-10)
  • Migration status for arpack++/mips64el (2.3-10 to 2.3-10): Will attempt migration (Any information below is purely informational)
• arpack++/s390x (2.3-10 to 2.3-10)
  • Migration status for arpack++/s390x (2.3-10 to 2.3-10): Will attempt migration (Any information below is purely informational)
• arpack/mips64el (3.9.1-1 to 3.9.1-1)
  • Migration status for arpack/mips64el (3.9.1-1 to 3.9.1-1): Will attempt migration (Any information below is purely informational)
• arpack/s390x (3.9.1-1 to 3.9.1-1)
  • Migration status for arpack/s390x (3.9.1-1 to 3.9.1-1): Will attempt migration (Any information below is purely informational)
• asmjit/mips64el (0.0~git20231115.1da9e4d-1 to 0.0~git20231115.1da9e4d-1)
  • Migration status for asmjit/mips64el (0.0~git20231115.1da9e4d-1 to 0.0~git20231115.1da9e4d-1): Will attempt migration (Any information below is purely informational)
• asmjit/s390x (0.0~git20231115.1da9e4d-1 to 0.0~git20231115.1da9e4d-1)
  • Migration status for asmjit/s390x (0.0~git20231115.1da9e4d-1 to 0.0~git20231115.1da9e4d-1): Will attempt migration (Any information below is purely informational)
• aspell/mips64el (0.60.8.1-1 to 0.60.8.1-1)
  • Migration status for aspell/mips64el (0.60.8.1-1 to 0.60.8.1-1): Will attempt migration (Any information below is purely informational)
• aspell/s390x (0.60.8.1-1 to 0.60.8.1-1)
  • Migration status for aspell/s390x (0.60.8.1-1 to 0.60.8.1-1): Will attempt migration (Any information below is purely informational)
• assimp/armel (5.3.1+ds-1 to 5.3.1+ds-1)
  • Migration status for assimp/armel (5.3.1+ds-1 to 5.3.1+ds-1): Will attempt migration (Any information below is purely informational)
• assimp/mips64el (5.3.1+ds-1 to 5.3.1+ds-1)
  • Migration status for assimp/mips64el (5.3.1+ds-1 to 5.3.1+ds-1): Will attempt migration (Any information below is purely informational)
• assimp/s390x (5.3.1+ds-1 to 5.3.1+ds-1)
  • Migration status for assimp/s390x (5.3.1+ds-1 to 5.3.1+ds-1): Will attempt migration (Any information below is purely informational)
• astc-encoder/mips64el (4.5.0+ds-2 to 4.5.0+ds-2)
  • Migration status for astc-encoder/mips64el (4.5.0+ds-2 to 4.5.0+ds-2): Will attempt migration (Any information below is purely informational)
• astc-encoder/s390x (4.5.0+ds-2 to 4.5.0+ds-2)
  • Migration status for astc-encoder/s390x (4.5.0+ds-2 to 4.5.0+ds-2): Will attempt migration (Any information below is purely informational)
• at-spi2-core/mips64el (2.50.0-1 to 2.50.0-1)
  • Migration status for at-spi2-core/mips64el (2.50.0-1 to 2.50.0-1): Will attempt migration (Any information below is purely informational)
• at-spi2-core/s390x (2.50.0-1 to 2.50.0-1)
  • Migration status for at-spi2-core/s390x (2.50.0-1 to 2.50.0-1): Will attempt migration (Any information below is purely informational)
• atkmm1.6/mips64el (2.28.3-2 to 2.28.3-2)
  • Migration status for atkmm1.6/mips64el (2.28.3-2 to 2.28.3-2): Will attempt migration (Any information below is purely informational)
• atkmm1.6/s390x (2.28.3-2 to 2.28.3-2)
  • Migration status for atkmm1.6/s390x (2.28.3-2 to 2.28.3-2): Will attempt migration (Any information below is purely informational)
• atlas/arm64 (3.10.3-13 to 3.10.3-13)
  • Migration status for atlas/arm64 (3.10.3-13 to 3.10.3-13): Will attempt migration (Any information below is purely informational)
• atlas/armel (3.10.3-13 to 3.10.3-13)
  • Migration status for atlas/armel (3.10.3-13 to 3.10.3-13): Will attempt migration (Any information below is purely informational)
• atlas/armhf (3.10.3-13 to 3.10.3-13)
  • Migration status for atlas/armhf (3.10.3-13 to 3.10.3-13): Will attempt migration (Any information below is purely informational)
• atlas/i386 (3.10.3-13 to 3.10.3-13)
  • Migration status for atlas/i386 (3.10.3-13 to 3.10.3-13): Will attempt migration (Any information below is purely informational)
• atlas/mips64el (3.10.3-13 to 3.10.3-13)
  • Migration status for atlas/mips64el (3.10.3-13 to 3.10.3-13): Will attempt migration (Any information below is purely informational)
• atlas/s390x (3.10.3-13 to 3.10.3-13)
  • Migration status for atlas/s390x (3.10.3-13 to 3.10.3-13): Will attempt migration (Any information below is purely informational)
• attica-kf5/mips64el (5.107.0-1 to 5.107.0-1)
  • Migration status for attica-kf5/mips64el (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• attica-kf5/s390x (5.107.0-1 to 5.107.0-1)
  • Migration status for attica-kf5/s390x (5.107.0-1 to 5.107.0-1): Will attempt migration (Any information below is purely informational)
• audacious-plugins/amd64 (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/amd64 (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/amd64 lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/arm64 (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/arm64 (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/arm64 lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/armel (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/armel (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/armel lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/armhf (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/armhf (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/armhf lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/i386 (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/i386 (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/i386 lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/mips64el (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/mips64el (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/mips64el lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/ppc64el (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/ppc64el (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/ppc64el lirc (not considered)
    • Invalidated by dependency
• audacious-plugins/s390x (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious-plugins/s390x (4.3.1-2 to 4.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: audacious-plugins/s390x lirc (not considered)
    • Invalidated by dependency
• audacious/mips64el (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious/mips64el (4.3.1-2 to 4.3.1-2): Will attempt migration (Any information below is purely informational)
• audacious/s390x (4.3.1-2 to 4.3.1-2)
  • Migration status for audacious/s390x (4.3.1-2 to 4.3.1-2): Will attempt migration (Any information below is purely informational)
• audiofile/mips64el (0.3.6-6 to 0.3.6-6)
  • Migration status for audiofile/mips64el (0.3.6-6 to 0.3.6-6): Will attempt migration (Any information below is purely informational)
• audiofile/s390x (0.3.6-6 to 0.3.6-6)
  • Migration status for audiofile/s390x (0.3.6-6 to 0.3.6-6): Will attempt migration (Any information below is purely informational)
• augeas/mips64el (1.14.1-1 to 1.14.1-1)
  • Migration status for augeas/mips64el (1.14.1-1 to 1.14.1-1): Will attempt migration (Any information below is purely informational)
• augeas/s390x (1.14.1-1 to 1.14.1-1)
  • Migration status for augeas/s390x (1.14.1-1 to 1.14.1-1): Will attempt migration (Any information below is purely informational)
• autogen/mips64el (1:5.18.16-5 to 1:5.18.16-5)
  • Migration status for autogen/mips64el (1:5.18.16-5 to 1:5.18.16-5): Will attempt migration (Any information below is purely informational)
• autogen/s390x (1:5.18.16-5 to 1:5.18.16-5)
  • Migration status for autogen/s390x (1:5.18.16-5 to 1:5.18.16-5): Will attempt migration (Any information below is purely informational)
• avahi/armel (0.8-13 to 0.8-13)
  • Migration status for avahi/armel (0.8-13 to 0.8-13): Will attempt migration (Any information below is purely informational)
• avahi/mips64el (0.8-13 to 0.8-13)
  • Migration status for avahi/mips64el (0.8-13 to 0.8-13): Will attempt migration (Any information below is purely informational)
• avahi/s390x (0.8-13 to 0.8-13)
  • Migration status for avahi/s390x (0.8-13 to 0.8-13): Will attempt migration (Any information below is purely informational)
• avifile/mips64el (1:0.7.48~20090503.ds-26 to 1:0.7.48~20090503.ds-26)
  • Migration status for avifile/mips64el (1:0.7.48~20090503.ds-26 to 1:0.7.48~20090503.ds-26): Will attempt migration (Any information below is purely informational)
• avifile/s390x (1:0.7.48~20090503.ds-26 to 1:0.7.48~20090503.ds-26)
  • Migration status for avifile/s390x (1:0.7.48~20090503.ds-26 to 1:0.7.48~20090503.ds-26): Will attempt migration (Any information below is purely informational)
• avogadrolibs/armel (1.98.1-2 to 1.98.1-2)
  • Migration status for avogadrolibs/armel (1.98.1-2 to 1.98.1-2): Will attempt migration (Any information below is purely informational)
• avogadrolibs/mips64el (1.98.1-2 to 1.98.1-2)
  • Migration status for avogadrolibs/mips64el (1.98.1-2 to 1.98.1-2): Will attempt migration (Any information below is purely informational)
• avogadrolibs/s390x (1.98.1-2 to 1.98.1-2)
  • Migration status for avogadrolibs/s390x (1.98.1-2 to 1.98.1-2): Will attempt migration (Any information below is purely informational)
• avro-c/mips64el (1.11.1-1 to 1.11.1-1)
  • Migration status for avro-c/mips64el (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
• avro-c/s390x (1.11.1-1 to 1.11.1-1)
  • Migration status for avro-c/s390x (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
• ayatana-ido/mips64el (0.10.1-1 to 0.10.1-1)
  • Migration status for ayatana-ido/mips64el (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• ayatana-ido/s390x (0.10.1-1 to 0.10.1-1)
  • Migration status for ayatana-ido/s390x (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• babeltrace/mips64el (1.5.11-3 to 1.5.11-3)
  • Migration status for babeltrace/mips64el (1.5.11-3 to 1.5.11-3): Will attempt migration (Any information below is purely informational)
• babeltrace/s390x (1.5.11-3 to 1.5.11-3)
  • Migration status for babeltrace/s390x (1.5.11-3 to 1.5.11-3): Will attempt migration (Any information below is purely informational)
• babeltrace2/i386 (2.0.5-2 to 2.0.5-2)
  • Migration status for babeltrace2/i386 (2.0.5-2 to 2.0.5-2): Will attempt migration (Any information below is purely informational)
• babeltrace2/mips64el (2.0.5-2 to 2.0.5-2)
  • Migration status for babeltrace2/mips64el (2.0.5-2 to 2.0.5-2): Will attempt migration (Any information below is purely informational)
• babeltrace2/s390x (2.0.5-2 to 2.0.5-2)
  • Migration status for babeltrace2/s390x (2.0.5-2 to 2.0.5-2): Will attempt migration (Any information below is purely informational)
• babl/i386 (1:0.1.106-3 to 1:0.1.106-3)
  • Migration status for babl/i386 (1:0.1.106-3 to 1:0.1.106-3): Will attempt migration (Any information below is purely informational)
• babl/mips64el (1:0.1.106-3 to 1:0.1.106-3)
  • Migration status for babl/mips64el (1:0.1.106-3 to 1:0.1.106-3): Will attempt migration (Any information below is purely informational)
• babl/s390x (1:0.1.106-3 to 1:0.1.106-3)
  • Migration status for babl/s390x (1:0.1.106-3 to 1:0.1.106-3): Will attempt migration (Any information below is purely informational)
• ball/amd64 (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11)
  • Migration status for ball/amd64 (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11): Will attempt migration (Any information below is purely informational)
• ball/arm64 (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11)
  • Migration status for ball/arm64 (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11): Will attempt migration (Any information below is purely informational)
• ball/i386 (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11)
  • Migration status for ball/i386 (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11): Will attempt migration (Any information below is purely informational)
• ball/ppc64el (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11)
  • Migration status for ball/ppc64el (1.5.0+git20180813.37fc53c-11 to 1.5.0+git20180813.37fc53c-11): Will attempt migration (Any information below is purely informational)
• baloo-widgets/i386 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for baloo-widgets/i386 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• baloo-widgets/mips64el (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for baloo-widgets/mips64el (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• baloo-widgets/s390x (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for baloo-widgets/s390x (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• bamf/i386 (0.5.6+repack-1 to 0.5.6+repack-1)
  • Migration status for bamf/i386 (0.5.6+repack-1 to 0.5.6+repack-1): Will attempt migration (Any information below is purely informational)
• bamf/mips64el (0.5.6+repack-1 to 0.5.6+repack-1)
  • Migration status for bamf/mips64el (0.5.6+repack-1 to 0.5.6+repack-1): Will attempt migration (Any information below is purely informational)
• bamf/s390x (0.5.6+repack-1 to 0.5.6+repack-1)
  • Migration status for bamf/s390x (0.5.6+repack-1 to 0.5.6+repack-1): Will attempt migration (Any information below is purely informational)
• bbhash/mips64el (1.0.0-6 to 1.0.0-6)
  • Migration status for bbhash/mips64el (1.0.0-6 to 1.0.0-6): Will attempt migration (Any information below is purely informational)
• bbhash/s390x (1.0.0-6 to 1.0.0-6)
  • Migration status for bbhash/s390x (1.0.0-6 to 1.0.0-6): Will attempt migration (Any information below is purely informational)
• bcg729/i386 (1.1.1-2 to 1.1.1-2)
  • Migration status for bcg729/i386 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• bcg729/mips64el (1.1.1-2 to 1.1.1-2)
  • Migration status for bcg729/mips64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• bcg729/s390x (1.1.1-2 to 1.1.1-2)
  • Migration status for bcg729/s390x (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• bcmatroska2/i386 (5.2.0-2 to 5.2.0-2)
  • Migration status for bcmatroska2/i386 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bcmatroska2/mips64el (5.2.0-2 to 5.2.0-2)
  • Migration status for bcmatroska2/mips64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bcmatroska2/s390x (5.2.0-2 to 5.2.0-2)
  • Migration status for bcmatroska2/s390x (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bctoolbox/i386 (5.2.0-2 to 5.2.0-2)
  • Migration status for bctoolbox/i386 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bctoolbox/mips64el (5.2.0-2 to 5.2.0-2)
  • Migration status for bctoolbox/mips64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bctoolbox/s390x (5.2.0-2 to 5.2.0-2)
  • Migration status for bctoolbox/s390x (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bear/armel (3.1.3-1 to 3.1.3-1)
  • Migration status for bear/armel (3.1.3-1 to 3.1.3-1): Will attempt migration (Any information below is purely informational)
• bear/i386 (3.1.3-1 to 3.1.3-1)
  • Migration status for bear/i386 (3.1.3-1 to 3.1.3-1): Will attempt migration (Any information below is purely informational)
• bear/mips64el (3.1.3-1 to 3.1.3-1)
  • Migration status for bear/mips64el (3.1.3-1 to 3.1.3-1): Will attempt migration (Any information below is purely informational)
• bear/s390x (3.1.3-1 to 3.1.3-1)
  • Migration status for bear/s390x (3.1.3-1 to 3.1.3-1): Will attempt migration (Any information below is purely informational)
• bearssl/i386 (0.6+dfsg.1-3 to 0.6+dfsg.1-3)
  • Migration status for bearssl/i386 (0.6+dfsg.1-3 to 0.6+dfsg.1-3): Will attempt migration (Any information below is purely informational)
• bearssl/mips64el (0.6+dfsg.1-3 to 0.6+dfsg.1-3)
  • Migration status for bearssl/mips64el (0.6+dfsg.1-3 to 0.6+dfsg.1-3): Will attempt migration (Any information below is purely informational)
• bearssl/s390x (0.6+dfsg.1-3 to 0.6+dfsg.1-3)
  • Migration status for bearssl/s390x (0.6+dfsg.1-3 to 0.6+dfsg.1-3): Will attempt migration (Any information below is purely informational)
• belcard/i386 (5.2.0-2 to 5.2.0-2)
  • Migration status for belcard/i386 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belcard/mips64el (5.2.0-2 to 5.2.0-2)
  • Migration status for belcard/mips64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belcard/s390x (5.2.0-2 to 5.2.0-2)
  • Migration status for belcard/s390x (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belle-sip/armel (5.2.0+dfsg-3 to 5.2.0+dfsg-3)
  • Migration status for belle-sip/armel (5.2.0+dfsg-3 to 5.2.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• belle-sip/i386 (5.2.0+dfsg-3 to 5.2.0+dfsg-3)
  • Migration status for belle-sip/i386 (5.2.0+dfsg-3 to 5.2.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• belle-sip/mips64el (5.2.0+dfsg-3 to 5.2.0+dfsg-3)
  • Migration status for belle-sip/mips64el (5.2.0+dfsg-3 to 5.2.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• belle-sip/s390x (5.2.0+dfsg-3 to 5.2.0+dfsg-3)
  • Migration status for belle-sip/s390x (5.2.0+dfsg-3 to 5.2.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• belr/armel (5.2.0-2 to 5.2.0-2)
  • Migration status for belr/armel (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belr/i386 (5.2.0-2 to 5.2.0-2)
  • Migration status for belr/i386 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belr/mips64el (5.2.0-2 to 5.2.0-2)
  • Migration status for belr/mips64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belr/s390x (5.2.0-2 to 5.2.0-2)
  • Migration status for belr/s390x (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bemenu/armel (0.6.15+dfsg-1 to 0.6.15+dfsg-1)
  • Migration status for bemenu/armel (0.6.15+dfsg-1 to 0.6.15+dfsg-1): Will attempt migration (Any information below is purely informational)
• bemenu/i386 (0.6.15+dfsg-1 to 0.6.15+dfsg-1)
  • Migration status for bemenu/i386 (0.6.15+dfsg-1 to 0.6.15+dfsg-1): Will attempt migration (Any information below is purely informational)
• bemenu/mips64el (0.6.15+dfsg-1 to 0.6.15+dfsg-1)
  • Migration status for bemenu/mips64el (0.6.15+dfsg-1 to 0.6.15+dfsg-1): Will attempt migration (Any information below is purely informational)
• bemenu/s390x (0.6.15+dfsg-1 to 0.6.15+dfsg-1)
  • Migration status for bemenu/s390x (0.6.15+dfsg-1 to 0.6.15+dfsg-1): Will attempt migration (Any information below is purely informational)
• biblesync/armel (2.1.0-2 to 2.1.0-2)
  • Migration status for biblesync/armel (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• biblesync/i386 (2.1.0-2 to 2.1.0-2)
  • Migration status for biblesync/i386 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• biblesync/mips64el (2.1.0-2 to 2.1.0-2)
  • Migration status for biblesync/mips64el (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• biblesync/s390x (2.1.0-2 to 2.1.0-2)
  • Migration status for biblesync/s390x (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• bibutils/armel (7.2-2 to 7.2-2)
  • Migration status for bibutils/armel (7.2-2 to 7.2-2): Will attempt migration (Any information below is purely informational)
• bibutils/i386 (7.2-2 to 7.2-2)
  • Migration status for bibutils/i386 (7.2-2 to 7.2-2): Will attempt migration (Any information below is purely informational)
• bibutils/mips64el (7.2-2 to 7.2-2)
  • Migration status for bibutils/mips64el (7.2-2 to 7.2-2): Will attempt migration (Any information below is purely informational)
• bibutils/s390x (7.2-2 to 7.2-2)
  • Migration status for bibutils/s390x (7.2-2 to 7.2-2): Will attempt migration (Any information below is purely informational)
• biometryd/armel (0.3.0-4 to 0.3.0-4)
  • Migration status for biometryd/armel (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• biometryd/armhf (0.3.0-4 to 0.3.0-4)
  • Migration status for biometryd/armhf (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• biometryd/i386 (0.3.0-4 to 0.3.0-4)
  • Migration status for biometryd/i386 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• biometryd/mips64el (0.3.0-4 to 0.3.0-4)
  • Migration status for biometryd/mips64el (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• biometryd/s390x (0.3.0-4 to 0.3.0-4)
  • Migration status for biometryd/s390x (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• blackbox/armel (0.70.1-39 to 0.70.1-39)
  • Migration status for blackbox/armel (0.70.1-39 to 0.70.1-39): Will attempt migration (Any information below is purely informational)
• blackbox/i386 (0.70.1-39 to 0.70.1-39)
  • Migration status for blackbox/i386 (0.70.1-39 to 0.70.1-39): Will attempt migration (Any information below is purely informational)
• blackbox/mips64el (0.70.1-39 to 0.70.1-39)
  • Migration status for blackbox/mips64el (0.70.1-39 to 0.70.1-39): Will attempt migration (Any information below is purely informational)
• blackbox/s390x (0.70.1-39 to 0.70.1-39)
  • Migration status for blackbox/s390x (0.70.1-39 to 0.70.1-39): Will attempt migration (Any information below is purely informational)
• blis/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• blis/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• blis/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• blis/armhf (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/armhf (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• blis/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• blis/mips64el (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/mips64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• blis/s390x (0.9.0-1 to 0.9.0-1)
  • Migration status for blis/s390x (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• bliss/armel (0.77-3 to 0.77-3)
  • Migration status for bliss/armel (0.77-3 to 0.77-3): Will attempt migration (Any information below is purely informational)
• bliss/i386 (0.77-3 to 0.77-3)
  • Migration status for bliss/i386 (0.77-3 to 0.77-3): Will attempt migration (Any information below is purely informational)
• bliss/mips64el (0.77-3 to 0.77-3)
  • Migration status for bliss/mips64el (0.77-3 to 0.77-3): Will attempt migration (Any information below is purely informational)
• bliss/s390x (0.77-3 to 0.77-3)
  • Migration status for bliss/s390x (0.77-3 to 0.77-3): Will attempt migration (Any information below is purely informational)
• blitz++/armel (1:1.0.2+ds-4 to 1:1.0.2+ds-4)
  • Migration status for blitz++/armel (1:1.0.2+ds-4 to 1:1.0.2+ds-4): Will attempt migration (Any information below is purely informational)
• blitz++/armhf (1:1.0.2+ds-4 to 1:1.0.2+ds-4)
  • Migration status for blitz++/armhf (1:1.0.2+ds-4 to 1:1.0.2+ds-4): Will attempt migration (Any information below is purely informational)
• blitz++/i386 (1:1.0.2+ds-4 to 1:1.0.2+ds-4)
  • Migration status for blitz++/i386 (1:1.0.2+ds-4 to 1:1.0.2+ds-4): Will attempt migration (Any information below is purely informational)
• blitz++/mips64el (1:1.0.2+ds-4 to 1:1.0.2+ds-4)
  • Migration status for blitz++/mips64el (1:1.0.2+ds-4 to 1:1.0.2+ds-4): Will attempt migration (Any information below is purely informational)
• blitz++/s390x (1:1.0.2+ds-4 to 1:1.0.2+ds-4)
  • Migration status for blitz++/s390x (1:1.0.2+ds-4 to 1:1.0.2+ds-4): Will attempt migration (Any information below is purely informational)
• bluefish/armel (2.2.14-1 to 2.2.14-1)
  • Migration status for bluefish/armel (2.2.14-1 to 2.2.14-1): Will attempt migration (Any information below is purely informational)
• bluefish/armhf (2.2.14-1 to 2.2.14-1)
  • Migration status for bluefish/armhf (2.2.14-1 to 2.2.14-1): Will attempt migration (Any information below is purely informational)
• bluefish/i386 (2.2.14-1 to 2.2.14-1)
  • Migration status for bluefish/i386 (2.2.14-1 to 2.2.14-1): Will attempt migration (Any information below is purely informational)
• bluefish/mips64el (2.2.14-1 to 2.2.14-1)
  • Migration status for bluefish/mips64el (2.2.14-1 to 2.2.14-1): Will attempt migration (Any information below is purely informational)
• bluefish/s390x (2.2.14-1 to 2.2.14-1)
  • Migration status for bluefish/s390x (2.2.14-1 to 2.2.14-1): Will attempt migration (Any information below is purely informational)
• bluez-alsa/armel (4.1.1-1 to 4.1.1-1)
  • Migration status for bluez-alsa/armel (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• bluez-alsa/armhf (4.1.1-1 to 4.1.1-1)
  • Migration status for bluez-alsa/armhf (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• bluez-alsa/i386 (4.1.1-1 to 4.1.1-1)
  • Migration status for bluez-alsa/i386 (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• bluez-alsa/mips64el (4.1.1-1 to 4.1.1-1)
  • Migration status for bluez-alsa/mips64el (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• bluez_pu (5.70-1.1 to 5.66-1+deb12u1)
  • Migration status for bluez_pu (5.70-1.1 to 5.66-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: bluez is newer in the target suite (5.70-1.1 5.66-1+deb12u1)
• bogl/armel (0.1.18-20 to 0.1.18-20)
  • Migration status for bogl/armel (0.1.18-20 to 0.1.18-20): Will attempt migration (Any information below is purely informational)
• bogl/armhf (0.1.18-20 to 0.1.18-20)
  • Migration status for bogl/armhf (0.1.18-20 to 0.1.18-20): Will attempt migration (Any information below is purely informational)
• bogl/i386 (0.1.18-20 to 0.1.18-20)
  • Migration status for bogl/i386 (0.1.18-20 to 0.1.18-20): Will attempt migration (Any information below is purely informational)
• bogl/mips64el (0.1.18-20 to 0.1.18-20)
  • Migration status for bogl/mips64el (0.1.18-20 to 0.1.18-20): Will attempt migration (Any information below is purely informational)
• bogl/s390x (0.1.18-20 to 0.1.18-20)
  • Migration status for bogl/s390x (0.1.18-20 to 0.1.18-20): Will attempt migration (Any information below is purely informational)
• boinc/amd64 (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/amd64 (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boinc/arm64 (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/arm64 (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boinc/armel (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/armel (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boinc/armhf (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/armhf (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boinc/i386 (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/i386 (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boinc/mips64el (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/mips64el (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boinc/s390x (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1)
  • Migration status for boinc/s390x (7.20.5+dfsg-1.1 to 7.20.5+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• boost1.83/amd64 (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/amd64 (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• boost1.83/arm64 (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/arm64 (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• boost1.83/armel (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/armel (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• boost1.83/armhf (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/armhf (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• boost1.83/i386 (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/i386 (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• boost1.83/mips64el (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/mips64el (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• boost1.83/s390x (1.83.0-2 to 1.83.0-2)
  • Migration status for boost1.83/s390x (1.83.0-2 to 1.83.0-2): Will attempt migration (Any information below is purely informational)
• botan/amd64 (2.19.3+dfsg-1 to 2.19.3+dfsg-1)
  • Migration status for botan/amd64 (2.19.3+dfsg-1 to 2.19.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• botan/armel (2.19.3+dfsg-1 to 2.19.3+dfsg-1)
  • Migration status for botan/armel (2.19.3+dfsg-1 to 2.19.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• botan/armhf (2.19.3+dfsg-1 to 2.19.3+dfsg-1)
  • Migration status for botan/armhf (2.19.3+dfsg-1 to 2.19.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• botan/i386 (2.19.3+dfsg-1 to 2.19.3+dfsg-1)
  • Migration status for botan/i386 (2.19.3+dfsg-1 to 2.19.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• botan/mips64el (2.19.3+dfsg-1 to 2.19.3+dfsg-1)
  • Migration status for botan/mips64el (2.19.3+dfsg-1 to 2.19.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• botan/s390x (2.19.3+dfsg-1 to 2.19.3+dfsg-1)
  • Migration status for botan/s390x (2.19.3+dfsg-1 to 2.19.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• box2d/amd64 (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/amd64 (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• box2d/armel (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/armel (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• box2d/armhf (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/armhf (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• box2d/i386 (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/i386 (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• box2d/mips64el (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/mips64el (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• box2d/s390x (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/s390x (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• brasero/amd64 (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/amd64 (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brasero/armel (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/armel (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brasero/armhf (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/armhf (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brasero/i386 (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/i386 (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brasero/mips64el (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/mips64el (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brasero/s390x (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/s390x (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brltty/amd64 (6.6-4 to 6.6-4)
  • Migration status for brltty/amd64 (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/amd64 liblouis (not considered)
    • Invalidated by dependency
• brltty/arm64 (6.6-4 to 6.6-4)
  • Migration status for brltty/arm64 (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/arm64 liblouis (not considered)
    • Invalidated by dependency
• brltty/armel (6.6-4 to 6.6-4)
  • Migration status for brltty/armel (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/armel liblouis (not considered)
    • Invalidated by dependency
• brltty/armhf (6.6-4 to 6.6-4)
  • Migration status for brltty/armhf (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/armhf liblouis (not considered)
    • Invalidated by dependency
• brltty/i386 (6.6-4 to 6.6-4)
  • Migration status for brltty/i386 (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/i386 liblouis (not considered)
    • Invalidated by dependency
• brltty/mips64el (6.6-4 to 6.6-4)
  • Migration status for brltty/mips64el (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/mips64el liblouis (not considered)
    • Invalidated by dependency
• brltty/ppc64el (6.6-4 to 6.6-4)
  • Migration status for brltty/ppc64el (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/ppc64el liblouis (not considered)
    • Invalidated by dependency
• brltty/s390x (6.6-4 to 6.6-4)
  • Migration status for brltty/s390x (6.6-4 to 6.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: brltty/s390x liblouis (not considered)
    • Invalidated by dependency
• brotli/amd64 (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/amd64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• brotli/armel (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/armel (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• brotli/armhf (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/armhf (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• brotli/i386 (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/i386 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• brotli/mips64el (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/mips64el (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• brotli/ppc64el (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/ppc64el (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• brotli/s390x (1.1.0-2 to 1.1.0-2)
  • Migration status for brotli/s390x (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• bullet/amd64 (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/amd64 (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bullet/armel (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/armel (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bullet/armhf (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/armhf (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bullet/i386 (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/i386 (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bullet/mips64el (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/mips64el (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bullet/ppc64el (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/ppc64el (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bullet/s390x (3.24+dfsg-2 to 3.24+dfsg-2)
  • Migration status for bullet/s390x (3.24+dfsg-2 to 3.24+dfsg-2): Will attempt migration (Any information below is purely informational)
• bulletml/amd64 (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/amd64 (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bulletml/armel (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/armel (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bulletml/armhf (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/armhf (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bulletml/i386 (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/i386 (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bulletml/mips64el (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/mips64el (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bulletml/ppc64el (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/ppc64el (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bulletml/s390x (0.0.6-7 to 0.0.6-7)
  • Migration status for bulletml/s390x (0.0.6-7 to 0.0.6-7): Will attempt migration (Any information below is purely informational)
• bzip2/amd64 (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/amd64 (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzip2/armel (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/armel (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzip2/armhf (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/armhf (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzip2/i386 (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/i386 (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzip2/mips64el (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/mips64el (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzip2/ppc64el (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/ppc64el (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzip2/s390x (1.0.8-5 to 1.0.8-5)
  • Migration status for bzip2/s390x (1.0.8-5 to 1.0.8-5): Will attempt migration (Any information below is purely informational)
• bzrtp/amd64 (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/amd64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bzrtp/armel (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/armel (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bzrtp/armhf (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/armhf (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bzrtp/i386 (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/i386 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bzrtp/mips64el (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/mips64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bzrtp/ppc64el (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/ppc64el (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bzrtp/s390x (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/s390x (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• c-blosc/amd64 (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/amd64 (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-blosc/armel (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/armel (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-blosc/armhf (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/armhf (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-blosc/i386 (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/i386 (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-blosc/mips64el (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/mips64el (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-blosc/ppc64el (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/ppc64el (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-blosc/s390x (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/s390x (1.21.5+ds-1 to 1.21.5+ds-1): Will attempt migration (Any information below is purely informational)
• c-icap/amd64 (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/amd64 (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-icap/armel (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/armel (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-icap/armhf (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/armhf (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-icap/i386 (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/i386 (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-icap/mips64el (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/mips64el (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-icap/ppc64el (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/ppc64el (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-icap/s390x (1:0.5.10-6 to 1:0.5.10-6)
  • Migration status for c-icap/s390x (1:0.5.10-6 to 1:0.5.10-6): Will attempt migration (Any information below is purely informational)
• c-vtapi/amd64 (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/amd64 (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• c-vtapi/armel (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/armel (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• c-vtapi/armhf (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/armhf (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• c-vtapi/i386 (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/i386 (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• c-vtapi/mips64el (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/mips64el (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• c-vtapi/ppc64el (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/ppc64el (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• c-vtapi/s390x (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1)
  • Migration status for c-vtapi/s390x (0.0~git20230329.226eda8-1 to 0.0~git20230329.226eda8-1): Will attempt migration (Any information below is purely informational)
• cairo/amd64 (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/amd64 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairo/armel (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/armel (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairo/armhf (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/armhf (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairo/i386 (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/i386 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairo/mips64el (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/mips64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairo/ppc64el (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/ppc64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairo/s390x (1.18.0-1 to 1.18.0-1)
  • Migration status for cairo/s390x (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/amd64 (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/amd64 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/armel (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/armel (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/armhf (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/armhf (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/i386 (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/i386 (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/mips64el (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/mips64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/ppc64el (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/ppc64el (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• cairomm1.16/s390x (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/s390x (1.18.0-1 to 1.18.0-1): Will attempt migration (Any information below is purely informational)
• callaudiod/amd64 (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/amd64 (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• callaudiod/armel (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/armel (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• callaudiod/armhf (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/armhf (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• callaudiod/i386 (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/i386 (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• callaudiod/mips64el (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/mips64el (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• callaudiod/ppc64el (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/ppc64el (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• callaudiod/s390x (0.1.9-1 to 0.1.9-1)
  • Migration status for callaudiod/s390x (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• canl-c/amd64 (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/amd64 (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canl-c/armel (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/armel (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canl-c/armhf (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/armhf (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canl-c/i386 (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/i386 (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canl-c/mips64el (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/mips64el (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canl-c/ppc64el (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/ppc64el (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canl-c/s390x (3.0.0-4 to 3.0.0-4)
  • Migration status for canl-c/s390x (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• canlock/amd64 (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/amd64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• canlock/armel (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/armel (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• canlock/armhf (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/armhf (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• canlock/i386 (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/i386 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• canlock/mips64el (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/mips64el (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• canlock/ppc64el (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/ppc64el (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• canlock/s390x (3.3.0-1 to 3.3.0-1)
  • Migration status for canlock/s390x (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• capnproto/amd64 (1.0.1-3 to 1.0.1-3)
  • Migration status for capnproto/amd64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• capnproto/armel (1.0.1-3 to 1.0.1-3)
  • Migration status for capnproto/armel (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• capnproto/armhf (1.0.1-3 to 1.0.1-3)
  • Migration status for capnproto/armhf (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• capnproto/i386 (1.0.1-3 to 1.0.1-3)
  • Migration status for capnproto/i386 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• capnproto/ppc64el (1.0.1-3 to 1.0.1-3)
  • Migration status for capnproto/ppc64el (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• capnproto/s390x (1.0.1-3 to 1.0.1-3)
  • Migration status for capnproto/s390x (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• capstone/amd64 (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/amd64 (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• capstone/armel (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/armel (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• capstone/armhf (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/armhf (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• capstone/i386 (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/i386 (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• capstone/mips64el (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/mips64el (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• capstone/ppc64el (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/ppc64el (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• capstone/s390x (4.0.2-5 to 4.0.2-5)
  • Migration status for capstone/s390x (4.0.2-5 to 4.0.2-5): Will attempt migration (Any information below is purely informational)
• caribou/amd64 (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/amd64 (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• caribou/armel (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/armel (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• caribou/armhf (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/armhf (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• caribou/i386 (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/i386 (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• caribou/mips64el (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/mips64el (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• caribou/ppc64el (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/ppc64el (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• caribou/s390x (0.4.21-8 to 0.4.21-8)
  • Migration status for caribou/s390x (0.4.21-8 to 0.4.21-8): Will attempt migration (Any information below is purely informational)
• casacore/amd64 (3.5.0-4 to 3.5.0-4)
  • Migration status for casacore/amd64 (3.5.0-4 to 3.5.0-4): Will attempt migration (Any information below is purely informational)
• casacore/armel (3.5.0-4 to 3.5.0-4)
  • Migration status for casacore/armel (3.5.0-4 to 3.5.0-4): Will attempt migration (Any information below is purely informational)
• casacore/armhf (3.5.0-4 to 3.5.0-4)
  • Migration status for casacore/armhf (3.5.0-4 to 3.5.0-4): Will attempt migration (Any information below is purely informational)
• casacore/i386 (3.5.0-4 to 3.5.0-4)
  • Migration status for casacore/i386 (3.5.0-4 to 3.5.0-4): Will attempt migration (Any information below is purely informational)
• casacore/s390x (3.5.0-4 to 3.5.0-4)
  • Migration status for casacore/s390x (3.5.0-4 to 3.5.0-4): Will attempt migration (Any information below is purely informational)
• cattle-1.0/amd64 (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/amd64 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cattle-1.0/armel (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/armel (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cattle-1.0/armhf (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/armhf (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cattle-1.0/i386 (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/i386 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cattle-1.0/mips64el (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/mips64el (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cattle-1.0/ppc64el (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/ppc64el (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cattle-1.0/s390x (1.4.0-2 to 1.4.0-2)
  • Migration status for cattle-1.0/s390x (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• cbflib/amd64 (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/amd64 (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cbflib/armel (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/armel (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cbflib/armhf (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/armhf (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cbflib/i386 (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/i386 (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cbflib/mips64el (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/mips64el (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cbflib/ppc64el (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/ppc64el (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cbflib/s390x (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3)
  • Migration status for cbflib/s390x (0.9.7+dfsg1-3 to 0.9.7+dfsg1-3): Will attempt migration (Any information below is purely informational)
• cctz/amd64 (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/amd64 (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cctz/armel (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/armel (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cctz/armhf (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/armhf (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cctz/i386 (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/i386 (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cctz/mips64el (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/mips64el (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cctz/ppc64el (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/ppc64el (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cctz/s390x (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/s390x (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cddlib/amd64 (094m-1 to 094m-1)
  • Migration status for cddlib/amd64 (094m-1 to 094m-1): Will attempt migration (Any information below is purely informational)
• cddlib/armel (094m-1 to 094m-1)
  • Migration status for cddlib/armel (094m-1 to 094m-1): Will attempt migration (Any information below is purely informational)
• cddlib/i386 (094m-1 to 094m-1)
  • Migration status for cddlib/i386 (094m-1 to 094m-1): Will attempt migration (Any information below is purely informational)
• cddlib/mips64el (094m-1 to 094m-1)
  • Migration status for cddlib/mips64el (094m-1 to 094m-1): Will attempt migration (Any information below is purely informational)
• cddlib/ppc64el (094m-1 to 094m-1)
  • Migration status for cddlib/ppc64el (094m-1 to 094m-1): Will attempt migration (Any information below is purely informational)
• cddlib/s390x (094m-1 to 094m-1)
  • Migration status for cddlib/s390x (094m-1 to 094m-1): Will attempt migration (Any information below is purely informational)
• cdparanoia/amd64 (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/amd64 (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cdparanoia/armel (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/armel (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cdparanoia/armhf (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/armhf (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cdparanoia/i386 (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/i386 (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cdparanoia/mips64el (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/mips64el (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cdparanoia/ppc64el (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/ppc64el (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cdparanoia/s390x (3.10.2+debian-14 to 3.10.2+debian-14)
  • Migration status for cdparanoia/s390x (3.10.2+debian-14 to 3.10.2+debian-14): Will attempt migration (Any information below is purely informational)
• cegui-mk2/amd64 (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/amd64 (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/arm64 (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/arm64 (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/armel (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/armel (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/armhf (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/armhf (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/i386 (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/i386 (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/mips64el (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/mips64el (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/ppc64el (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/ppc64el (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• cegui-mk2/s390x (0.8.7+git20220615-5 to 0.8.7+git20220615-5)
  • Migration status for cegui-mk2/s390x (0.8.7+git20220615-5 to 0.8.7+git20220615-5): Will attempt migration (Any information below is purely informational)
• ceres-solver/amd64 (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/amd64 (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• ceres-solver/arm64 (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/arm64 (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• ceres-solver/armel (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/armel (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• ceres-solver/armhf (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/armhf (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• ceres-solver/i386 (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/i386 (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• ceres-solver/ppc64el (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/ppc64el (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• ceres-solver/s390x (2.2.0+dfsg-4 to 2.2.0+dfsg-4)
  • Migration status for ceres-solver/s390x (2.2.0+dfsg-4 to 2.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• cfitsio/amd64 (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/amd64 (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cfitsio/armel (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/armel (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cfitsio/armhf (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/armhf (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cfitsio/i386 (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/i386 (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cfitsio/mips64el (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/mips64el (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cfitsio/ppc64el (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/ppc64el (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cfitsio/s390x (4.3.0-2 to 4.3.0-2)
  • Migration status for cfitsio/s390x (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
• cg3/amd64 (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/amd64 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cg3/armel (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/armel (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cg3/armhf (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/armhf (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cg3/i386 (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/i386 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cg3/mips64el (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/mips64el (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cg3/ppc64el (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/ppc64el (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cg3/s390x (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/s390x (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• cgal/amd64 (5.6-1 to 5.6-1)
  • Migration status for cgal/amd64 (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgal/arm64 (5.6-1 to 5.6-1)
  • Migration status for cgal/arm64 (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgal/armhf (5.6-1 to 5.6-1)
  • Migration status for cgal/armhf (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgal/i386 (5.6-1 to 5.6-1)
  • Migration status for cgal/i386 (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgal/mips64el (5.6-1 to 5.6-1)
  • Migration status for cgal/mips64el (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgal/ppc64el (5.6-1 to 5.6-1)
  • Migration status for cgal/ppc64el (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgal/s390x (5.6-1 to 5.6-1)
  • Migration status for cgal/s390x (5.6-1 to 5.6-1): Will attempt migration (Any information below is purely informational)
• cgif/amd64 (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/amd64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cgif/armel (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/armel (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cgif/armhf (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/armhf (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cgif/i386 (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/i386 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cgif/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cgif/ppc64el (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/ppc64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cgif/s390x (0.3.2-1 to 0.3.2-1)
  • Migration status for cgif/s390x (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• cglm/amd64 (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/amd64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cglm/armel (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/armel (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cglm/armhf (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/armhf (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cglm/i386 (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/i386 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cglm/mips64el (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/mips64el (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cglm/ppc64el (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/ppc64el (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cglm/s390x (0.9.1-1 to 0.9.1-1)
  • Migration status for cglm/s390x (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• cgsi-gsoap/armel (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/armel (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
• cgsi-gsoap/armhf (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/armhf (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
• cgsi-gsoap/i386 (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/i386 (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
• cgsi-gsoap/mips64el (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/mips64el (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
• cgsi-gsoap/ppc64el (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/ppc64el (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
• cgsi-gsoap/s390x (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/s390x (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
• chafa/amd64 (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/amd64 (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/arm64 (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/arm64 (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/armel (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/armel (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/armhf (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/armhf (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/i386 (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/i386 (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/mips64el (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/mips64el (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/ppc64el (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/ppc64el (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• chafa/s390x (1.12.5-3 to 1.12.5-3)
  • Migration status for chafa/s390x (1.12.5-3 to 1.12.5-3): Will attempt migration (Any information below is purely informational)
• charls/amd64 (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/amd64 (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/arm64 (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/arm64 (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/armel (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/armel (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/armhf (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/armhf (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/i386 (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/i386 (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/mips64el (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/mips64el (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/ppc64el (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/ppc64el (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• charls/s390x (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/s390x (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• cheese/amd64 (44.1-1 to 44.1-1)
  • Migration status for cheese/amd64 (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/arm64 (44.1-1 to 44.1-1)
  • Migration status for cheese/arm64 (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/armel (44.1-1 to 44.1-1)
  • Migration status for cheese/armel (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/armhf (44.1-1 to 44.1-1)
  • Migration status for cheese/armhf (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/i386 (44.1-1 to 44.1-1)
  • Migration status for cheese/i386 (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/mips64el (44.1-1 to 44.1-1)
  • Migration status for cheese/mips64el (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/ppc64el (44.1-1 to 44.1-1)
  • Migration status for cheese/ppc64el (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheese/s390x (44.1-1 to 44.1-1)
  • Migration status for cheese/s390x (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• chipmunk/amd64 (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/amd64 (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/arm64 (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/arm64 (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/armel (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/armel (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/armhf (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/armhf (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/i386 (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/i386 (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/mips64el (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/mips64el (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/ppc64el (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/ppc64el (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chipmunk/s390x (7.0.3-5 to 7.0.3-5)
  • Migration status for chipmunk/s390x (7.0.3-5 to 7.0.3-5): Will attempt migration (Any information below is purely informational)
• chmlib/amd64 (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/amd64 (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/arm64 (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/arm64 (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/armel (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/armel (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/armhf (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/armhf (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/i386 (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/i386 (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/mips64el (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/mips64el (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/ppc64el (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/ppc64el (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chmlib/s390x (2:0.40a-8 to 2:0.40a-8)
  • Migration status for chmlib/s390x (2:0.40a-8 to 2:0.40a-8): Will attempt migration (Any information below is purely informational)
• chromaprint/amd64 (1.5.1-4 to 1.5.1-4)
  • Migration status for chromaprint/amd64 (1.5.1-4 to 1.5.1-4): Will attempt migration (Any information below is purely informational)
• chromaprint/arm64 (1.5.1-4 to 1.5.1-4)
  • Migration status for chromaprint/arm64 (1.5.1-4 to 1.5.1-4): Will attempt migration (Any information below is purely informational)
• chromaprint/i386 (1.5.1-4 to 1.5.1-4)
  • Migration status for chromaprint/i386 (1.5.1-4 to 1.5.1-4): Will attempt migration (Any information below is purely informational)
• chromaprint/mips64el (1.5.1-4 to 1.5.1-4)
  • Migration status for chromaprint/mips64el (1.5.1-4 to 1.5.1-4): Will attempt migration (Any information below is purely informational)
• chromaprint/ppc64el (1.5.1-4 to 1.5.1-4)
  • Migration status for chromaprint/ppc64el (1.5.1-4 to 1.5.1-4): Will attempt migration (Any information below is purely informational)
• chromaprint/s390x (1.5.1-4 to 1.5.1-4)
  • Migration status for chromaprint/s390x (1.5.1-4 to 1.5.1-4): Will attempt migration (Any information below is purely informational)
• chromium_pu (120.0.6099.129-1 to 120.0.6099.129-1~deb12u1)
  • Migration status for chromium_pu (120.0.6099.129-1 to 120.0.6099.129-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: chromium is newer in the target suite (120.0.6099.129-1 120.0.6099.129-1~deb12u1)
• cif-api/amd64 (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/amd64 (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/arm64 (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/arm64 (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/armel (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/armel (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/armhf (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/armhf (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/i386 (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/i386 (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/mips64el (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/mips64el (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/ppc64el (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/ppc64el (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-api/s390x (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/s390x (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cimfomfa/amd64 (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/amd64 (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/arm64 (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/arm64 (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/armel (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/armel (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/armhf (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/armhf (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/i386 (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/i386 (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/mips64el (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/mips64el (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/ppc64el (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/ppc64el (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cimfomfa/s390x (21-361-2 to 21-361-2)
  • Migration status for cimfomfa/s390x (21-361-2 to 21-361-2): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/amd64 (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/amd64 (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/arm64 (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/arm64 (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/armel (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/armel (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/armhf (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/armhf (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/i386 (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/i386 (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/mips64el (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/mips64el (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/ppc64el (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/ppc64el (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-control-center/s390x (5.8.2-1 to 5.8.2-1)
  • Migration status for cinnamon-control-center/s390x (5.8.2-1 to 5.8.2-1): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/amd64 (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/amd64 (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/arm64 (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/arm64 (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/armel (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/armel (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/armhf (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/armhf (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/i386 (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/i386 (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/mips64el (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/mips64el (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/ppc64el (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/ppc64el (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/s390x (5.8.0-2 to 5.8.0-2)
  • Migration status for cinnamon-desktop/s390x (5.8.0-2 to 5.8.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/amd64 (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/amd64 (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/arm64 (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/arm64 (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/armel (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/armel (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/armhf (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/armhf (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/i386 (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/i386 (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/mips64el (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/mips64el (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/ppc64el (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/ppc64el (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-menus/s390x (6.0.0-1 to 6.0.0-1)
  • Migration status for cinnamon-menus/s390x (6.0.0-1 to 6.0.0-1): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/amd64 (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/amd64 (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/arm64 (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/arm64 (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/armel (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/armel (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/armhf (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/armhf (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/i386 (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/i386 (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/mips64el (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/mips64el (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/ppc64el (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/ppc64el (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-screensaver/s390x (5.8.1-2 to 5.8.1-2)
  • Migration status for cinnamon-screensaver/s390x (5.8.1-2 to 5.8.1-2): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/amd64 (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/amd64 (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/arm64 (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/arm64 (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/armel (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/armel (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/armhf (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/armhf (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/i386 (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/i386 (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/mips64el (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/mips64el (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/ppc64el (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/ppc64el (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-settings-daemon/s390x (5.8.1-3 to 5.8.1-3)
  • Migration status for cinnamon-settings-daemon/s390x (5.8.1-3 to 5.8.1-3): Will attempt migration (Any information below is purely informational)
• civetweb/amd64 (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/amd64 (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/arm64 (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/arm64 (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/armel (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/armel (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/armhf (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/armhf (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/i386 (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/i386 (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/mips64el (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/mips64el (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/ppc64el (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/ppc64el (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• civetweb/s390x (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/s390x (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• ck/amd64 (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/amd64 (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/arm64 (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/arm64 (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/armel (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/armel (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/armhf (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/armhf (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/i386 (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/i386 (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/mips64el (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/mips64el (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/ppc64el (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/ppc64el (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• ck/s390x (0.7.1-12 to 0.7.1-12)
  • Migration status for ck/s390x (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• clamav/amd64 (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/amd64 (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/arm64 (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/arm64 (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/armel (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/armel (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/armhf (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/armhf (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/i386 (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/i386 (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/mips64el (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/mips64el (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/ppc64el (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/ppc64el (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clamav/s390x (1.0.3+dfsg-2 to 1.0.3+dfsg-2)
  • Migration status for clamav/s390x (1.0.3+dfsg-2 to 1.0.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• clanlib/amd64 (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/amd64 (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/arm64 (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/arm64 (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/armel (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/armel (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/armhf (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/armhf (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/i386 (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/i386 (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/mips64el (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/mips64el (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/ppc64el (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/ppc64el (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• clanlib/s390x (1.0~svn3827-11 to 1.0~svn3827-11)
  • Migration status for clanlib/s390x (1.0~svn3827-11 to 1.0~svn3827-11): Will attempt migration (Any information below is purely informational)
• claws-mail/amd64 (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/amd64 (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/arm64 (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/arm64 (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/armel (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/armel (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/armhf (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/armhf (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/i386 (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/i386 (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/mips64el (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/mips64el (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/ppc64el (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/ppc64el (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• claws-mail/s390x (4.2.0-1 to 4.2.0-1)
  • Migration status for claws-mail/s390x (4.2.0-1 to 4.2.0-1): Will attempt migration (Any information below is purely informational)
• clblast/amd64 (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/amd64 (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/arm64 (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/arm64 (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/armel (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/armel (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/armhf (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/armhf (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/i386 (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/i386 (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/mips64el (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/mips64el (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/ppc64el (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/ppc64el (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• clblast/s390x (1.6.1-1 to 1.6.1-1)
  • Migration status for clblast/s390x (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• cld2/amd64 (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/amd64 (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• cld2/arm64 (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/arm64 (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• cld2/armel (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/armel (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• cld2/armhf (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/armhf (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• cld2/i386 (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/i386 (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• cld2/mips64el (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/mips64el (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• cld2/ppc64el (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/ppc64el (0.0.0-git20150806-9 to 0.0.0-git20150806-9): Will attempt migration (Any information below is purely informational)
• clhep/amd64 (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/amd64 (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/arm64 (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/arm64 (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/armel (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/armel (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/armhf (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/armhf (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/i386 (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/i386 (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/mips64el (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/mips64el (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/ppc64el (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/ppc64el (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clhep/s390x (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1)
  • Migration status for clhep/s390x (2.1.4.1+dfsg-1.1 to 2.1.4.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clipper/amd64 (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/amd64 (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/arm64 (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/arm64 (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/armel (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/armel (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/armhf (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/armhf (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/i386 (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/i386 (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/mips64el (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/mips64el (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/ppc64el (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/ppc64el (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• clipper/s390x (2.1.20201109-2 to 2.1.20201109-2)
  • Migration status for clipper/s390x (2.1.20201109-2 to 2.1.20201109-2): Will attempt migration (Any information below is purely informational)
• cln/amd64 (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/amd64 (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/arm64 (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/arm64 (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/armel (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/armel (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/armhf (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/armhf (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/i386 (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/i386 (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/mips64el (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/mips64el (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/ppc64el (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/ppc64el (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cln/s390x (1.3.6-4 to 1.3.6-4)
  • Migration status for cln/s390x (1.3.6-4 to 1.3.6-4): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/amd64 (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/amd64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/arm64 (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/arm64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/armel (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/armel (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/armhf (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/armhf (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/i386 (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/i386 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/mips64el (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/mips64el (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/ppc64el (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/ppc64el (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/s390x (2.0.1-1 to 2.0.1-1)
  • Migration status for cloudflare-ddns/s390x (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• clp/amd64 (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/amd64 (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/arm64 (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/arm64 (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/armel (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/armel (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/armhf (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/armhf (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/i386 (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/i386 (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/mips64el (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/mips64el (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/ppc64el (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/ppc64el (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clp/s390x (1.17.6-3 to 1.17.6-3)
  • Migration status for clp/s390x (1.17.6-3 to 1.17.6-3): Will attempt migration (Any information below is purely informational)
• clsync/amd64 (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/amd64 (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/arm64 (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/arm64 (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/armel (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/armel (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/armhf (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/armhf (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/i386 (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/i386 (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/mips64el (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/mips64el (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/ppc64el (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/ppc64el (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clsync/s390x (0.4.5-2 to 0.4.5-2)
  • Migration status for clsync/s390x (0.4.5-2 to 0.4.5-2): Will attempt migration (Any information below is purely informational)
• clthreads/amd64 (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/amd64 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/arm64 (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/arm64 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/armel (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/armel (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/armhf (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/armhf (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/i386 (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/i386 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/mips64el (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/mips64el (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/ppc64el (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/ppc64el (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/s390x (2.4.2-1 to 2.4.2-1)
  • Migration status for clthreads/s390x (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• clucene-core/amd64 (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/amd64 (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/arm64 (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/arm64 (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/armel (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/armel (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/armhf (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/armhf (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/i386 (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/i386 (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/mips64el (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/mips64el (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/ppc64el (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/ppc64el (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/s390x (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1)
  • Migration status for clucene-core/s390x (2.3.3.4+dfsg-1.1 to 2.3.3.4+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/amd64 (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/amd64 (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/arm64 (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/arm64 (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/armel (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/armel (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/armhf (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/armhf (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/i386 (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/i386 (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/mips64el (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/mips64el (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/ppc64el (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/ppc64el (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/s390x (3.0.27-3 to 3.0.27-3)
  • Migration status for clutter-gst-3.0/s390x (3.0.27-3 to 3.0.27-3): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/amd64 (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/amd64 (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/arm64 (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/arm64 (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/armel (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/armel (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/armhf (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/armhf (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/i386 (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/i386 (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/mips64el (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/mips64el (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/ppc64el (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/ppc64el (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/s390x (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/s390x (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• clxclient/amd64 (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/amd64 (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/arm64 (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/arm64 (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/armel (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/armel (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/armhf (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/armhf (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/i386 (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/i386 (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/mips64el (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/mips64el (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/ppc64el (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/ppc64el (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• clxclient/s390x (3.9.2-2 to 3.9.2-2)
  • Migration status for clxclient/s390x (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• cmark-gfm/amd64 (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/amd64 (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/arm64 (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/arm64 (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/armel (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/armel (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/armhf (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/armhf (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/i386 (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/i386 (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/mips64el (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/mips64el (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/ppc64el (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/ppc64el (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark-gfm/s390x (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6)
  • Migration status for cmark-gfm/s390x (0.29.0.gfm.6-6 to 0.29.0.gfm.6-6): Will attempt migration (Any information below is purely informational)
• cmark/amd64 (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/amd64 (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/arm64 (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/arm64 (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/armel (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/armel (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/armhf (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/armhf (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/i386 (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/i386 (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/mips64el (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/mips64el (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/ppc64el (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/ppc64el (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmark/s390x (0.30.2-6 to 0.30.2-6)
  • Migration status for cmark/s390x (0.30.2-6 to 0.30.2-6): Will attempt migration (Any information below is purely informational)
• cmigemo/amd64 (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/amd64 (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/arm64 (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/arm64 (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/armel (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/armel (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/armhf (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/armhf (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/i386 (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/i386 (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/mips64el (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/mips64el (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/ppc64el (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/ppc64el (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cmigemo/s390x (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1)
  • Migration status for cmigemo/s390x (1:1.2+gh0.20220623-1 to 1:1.2+gh0.20220623-1): Will attempt migration (Any information below is purely informational)
• cminpack/amd64 (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/amd64 (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/arm64 (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/arm64 (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/armel (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/armel (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/armhf (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/armhf (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/i386 (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/i386 (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/mips64el (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/mips64el (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/ppc64el (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/ppc64el (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• cminpack/s390x (1.3.6-5 to 1.3.6-5)
  • Migration status for cminpack/s390x (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• codeblocks/amd64 (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/amd64 (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/arm64 (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/arm64 (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/armel (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/armel (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/armhf (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/armhf (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/i386 (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/i386 (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/mips64el (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/mips64el (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/ppc64el (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/ppc64el (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codeblocks/s390x (20.03+svn13046-0.2 to 20.03+svn13046-0.2)
  • Migration status for codeblocks/s390x (20.03+svn13046-0.2 to 20.03+svn13046-0.2): Will attempt migration (Any information below is purely informational)
• codec2/amd64 (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/amd64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/arm64 (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/arm64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/armel (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/armel (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/armhf (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/armhf (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/i386 (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/i386 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/mips64el (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/mips64el (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/ppc64el (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/ppc64el (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• codec2/s390x (1.2.0-2 to 1.2.0-2)
  • Migration status for codec2/s390x (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• cogl/amd64 (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/amd64 (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/arm64 (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/arm64 (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/armel (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/armel (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/armhf (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/armhf (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/i386 (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/i386 (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/mips64el (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/mips64el (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/ppc64el (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/ppc64el (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• cogl/s390x (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/s390x (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• coinor-cbc/amd64 (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/amd64 (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/arm64 (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/arm64 (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/armel (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/armel (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/armhf (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/armhf (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/i386 (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/i386 (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/mips64el (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/mips64el (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/ppc64el (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/ppc64el (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cbc/s390x (2.10.11+ds1-1 to 2.10.11+ds1-1)
  • Migration status for coinor-cbc/s390x (2.10.11+ds1-1 to 2.10.11+ds1-1): Will attempt migration (Any information below is purely informational)
• coinor-cgl/amd64 (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/amd64 (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/arm64 (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/arm64 (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/armel (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/armel (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/armhf (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/armhf (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/i386 (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/i386 (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/mips64el (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/mips64el (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/ppc64el (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/ppc64el (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-cgl/s390x (0.60.3+repack1-4 to 0.60.3+repack1-4)
  • Migration status for coinor-cgl/s390x (0.60.3+repack1-4 to 0.60.3+repack1-4): Will attempt migration (Any information below is purely informational)
• coinor-csdp/amd64 (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/amd64 (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/arm64 (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/arm64 (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/armel (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/armel (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/armhf (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/armhf (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/i386 (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/i386 (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/mips64el (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/mips64el (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/ppc64el (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/ppc64el (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-csdp/s390x (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/s390x (6.2.0-5 to 6.2.0-5): Will attempt migration (Any information below is purely informational)
• coinor-dylp/amd64 (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/amd64 (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/arm64 (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/arm64 (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/armel (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/armel (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/armhf (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/armhf (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/i386 (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/i386 (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/mips64el (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/mips64el (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/ppc64el (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/ppc64el (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• coinor-dylp/s390x (1.10.4-3 to 1.10.4-3)
  • Migration status for coinor-dylp/s390x (1.10.4-3 to 1.10.4-3): Will attempt migration (Any information below is purely informational)
• collada-dom/amd64 (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/amd64 (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/arm64 (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/arm64 (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/armel (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/armel (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/armhf (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/armhf (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/i386 (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/i386 (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/mips64el (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/mips64el (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/ppc64el (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/ppc64el (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collada-dom/s390x (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/s390x (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• colord-gtk/amd64 (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/amd64 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/arm64 (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/arm64 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/armel (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/armel (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/armhf (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/armhf (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/i386 (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/i386 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/mips64el (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/mips64el (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/ppc64el (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/ppc64el (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colord-gtk/s390x (0.3.0-4 to 0.3.0-4)
  • Migration status for colord-gtk/s390x (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• colpack/amd64 (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/amd64 (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/arm64 (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/arm64 (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/armel (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/armel (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/armhf (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/armhf (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/i386 (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/i386 (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/mips64el (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/mips64el (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/ppc64el (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/ppc64el (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• colpack/s390x (1.0.10-7 to 1.0.10-7)
  • Migration status for colpack/s390x (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• combblas/amd64 (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/amd64 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/arm64 (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/arm64 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/armel (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/armel (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/armhf (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/armhf (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/i386 (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/i386 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/mips64el (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/mips64el (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/ppc64el (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/ppc64el (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• combblas/s390x (2.0.0-3 to 2.0.0-3)
  • Migration status for combblas/s390x (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• compiz/amd64 (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/amd64 (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/arm64 (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/arm64 (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/armel (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/armel (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/armhf (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/armhf (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/i386 (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/i386 (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/mips64el (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/mips64el (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/ppc64el (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/ppc64el (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• compiz/s390x (2:0.8.18-5 to 2:0.8.18-5)
  • Migration status for compiz/s390x (2:0.8.18-5 to 2:0.8.18-5): Will attempt migration (Any information below is purely informational)
• consolekit2/amd64 (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/amd64 (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/arm64 (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/arm64 (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/armel (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/armel (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/armhf (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/armhf (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/i386 (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/i386 (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/mips64el (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/mips64el (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/ppc64el (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/ppc64el (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• consolekit2/s390x (1.2.6-3 to 1.2.6-3)
  • Migration status for consolekit2/s390x (1.2.6-3 to 1.2.6-3): Will attempt migration (Any information below is purely informational)
• corosync/amd64 (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/amd64 (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/arm64 (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/arm64 (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/armel (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/armel (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/armhf (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/armhf (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/i386 (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/i386 (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/mips64el (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/mips64el (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/ppc64el (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/ppc64el (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• corosync/s390x (3.1.7-1 to 3.1.7-1)
  • Migration status for corosync/s390x (3.1.7-1 to 3.1.7-1): Will attempt migration (Any information below is purely informational)
• cpdb-libs/amd64 (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/amd64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/arm64 (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/arm64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/armel (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/armel (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/armhf (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/armhf (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/i386 (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/i386 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/mips64el (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/mips64el (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/ppc64el (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/ppc64el (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpdb-libs/s390x (1.2.0-3 to 1.2.0-3)
  • Migration status for cpdb-libs/s390x (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/amd64 (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/amd64 (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/arm64 (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/arm64 (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/armel (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/armel (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/armhf (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/armhf (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/i386 (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/i386 (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/mips64el (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/mips64el (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/ppc64el (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/ppc64el (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/s390x (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/s390x (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/amd64 (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/amd64 (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/arm64 (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/arm64 (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/armel (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/armel (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/armhf (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/armhf (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/i386 (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/i386 (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/mips64el (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/mips64el (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/ppc64el (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/ppc64el (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-muse/s390x (2.8.7+dfsg-3 to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse/s390x (2.8.7+dfsg-3 to 2.8.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/amd64 (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/amd64 (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/arm64 (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/arm64 (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/armel (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/armel (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/armhf (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/armhf (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/i386 (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/i386 (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/mips64el (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/mips64el (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/ppc64el (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/ppc64el (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/s390x (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/s390x (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/amd64 (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/amd64 (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/arm64 (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/arm64 (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/armel (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/armel (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/armhf (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/armhf (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/i386 (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/i386 (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/mips64el (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/mips64el (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/ppc64el (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/ppc64el (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-visir/s390x (4.4.2+dfsg-1 to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir/s390x (4.4.2+dfsg-1 to 4.4.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• cppad/amd64 (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/amd64 (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/arm64 (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/arm64 (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/armel (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/armel (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/armhf (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/armhf (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/i386 (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/i386 (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/mips64el (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/mips64el (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/ppc64el (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/ppc64el (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cppad/s390x (2023.00.00.0-3 to 2023.00.00.0-3)
  • Migration status for cppad/s390x (2023.00.00.0-3 to 2023.00.00.0-3): Will attempt migration (Any information below is purely informational)
• cpputest/amd64 (4.0-2 to 4.0-2)
  • Migration status for cpputest/amd64 (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/arm64 (4.0-2 to 4.0-2)
  • Migration status for cpputest/arm64 (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/armel (4.0-2 to 4.0-2)
  • Migration status for cpputest/armel (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/armhf (4.0-2 to 4.0-2)
  • Migration status for cpputest/armhf (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/i386 (4.0-2 to 4.0-2)
  • Migration status for cpputest/i386 (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/mips64el (4.0-2 to 4.0-2)
  • Migration status for cpputest/mips64el (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/ppc64el (4.0-2 to 4.0-2)
  • Migration status for cpputest/ppc64el (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cpputest/s390x (4.0-2 to 4.0-2)
  • Migration status for cpputest/s390x (4.0-2 to 4.0-2): Will attempt migration (Any information below is purely informational)
• cppzmq/amd64 (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/amd64 (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/arm64 (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/arm64 (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/armel (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/armel (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/armhf (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/armhf (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/i386 (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/i386 (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/mips64el (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/mips64el (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/ppc64el (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/ppc64el (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cppzmq/s390x (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/s390x (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/amd64 (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/amd64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/arm64 (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/arm64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/armel (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/armhf (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/armhf (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/i386 (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/i386 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/mips64el (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/mips64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cpu-features/s390x (0.9.0-1 to 0.9.0-1)
  • Migration status for cpu-features/s390x (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• cqrlib/amd64 (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/amd64 (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/arm64 (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/arm64 (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/armel (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/armel (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/armhf (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/armhf (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/i386 (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/i386 (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/mips64el (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/mips64el (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/ppc64el (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/ppc64el (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cqrlib/s390x (1.1.4-3 to 1.1.4-3)
  • Migration status for cqrlib/s390x (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• cracklib2/amd64 (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/amd64 (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/arm64 (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/arm64 (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/armel (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/armel (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/armhf (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/armhf (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/i386 (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/i386 (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/mips64el (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/mips64el (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/ppc64el (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/ppc64el (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• cracklib2/s390x (2.9.6-5.1 to 2.9.6-5.1)
  • Migration status for cracklib2/s390x (2.9.6-5.1 to 2.9.6-5.1): Will attempt migration (Any information below is purely informational)
• createrepo-c/amd64 (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/amd64 (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/arm64 (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/arm64 (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/armel (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/armel (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/armhf (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/armhf (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/i386 (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/i386 (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/mips64el (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/mips64el (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/ppc64el (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/ppc64el (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• createrepo-c/s390x (0.17.3-2 to 0.17.3-2)
  • Migration status for createrepo-c/s390x (0.17.3-2 to 0.17.3-2): Will attempt migration (Any information below is purely informational)
• croaring/amd64 (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/amd64 (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• croaring/arm64 (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/arm64 (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• croaring/armel (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/armel (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• croaring/armhf (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/armhf (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• croaring/i386 (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/i386 (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• croaring/mips64el (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/mips64el (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• croaring/ppc64el (0.2.66+ds-2 to 0.2.66+ds-2)
  • Migration status for croaring/ppc64el (0.2.66+ds-2 to 0.2.66+ds-2): Will attempt migration (Any information below is purely informational)
• crossguid/amd64 (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/amd64 (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/arm64 (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/arm64 (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/armel (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/armel (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/armhf (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/armhf (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/i386 (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/i386 (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/mips64el (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/mips64el (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/ppc64el (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/ppc64el (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crossguid/s390x (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/s390x (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• cryptominisat/amd64 (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/amd64 (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/arm64 (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/arm64 (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/armel (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/armel (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/armhf (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/armhf (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/i386 (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/i386 (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/mips64el (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/mips64el (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/ppc64el (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/ppc64el (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptominisat/s390x (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1)
  • Migration status for cryptominisat/s390x (5.11.15+dfsg1-1 to 5.11.15+dfsg1-1): Will attempt migration (Any information below is purely informational)
• cryptsetup/amd64 (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/amd64 (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• cryptsetup/arm64 (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/arm64 (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• cryptsetup/armel (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/armel (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• cryptsetup/armhf (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/armhf (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• cryptsetup/i386 (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/i386 (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• cryptsetup/mips64el (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/mips64el (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• cryptsetup/s390x (2:2.6.1-6 to 2:2.6.1-6)
  • Migration status for cryptsetup/s390x (2:2.6.1-6 to 2:2.6.1-6): Will attempt migration (Any information below is purely informational)
• csmith/amd64 (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/amd64 (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/arm64 (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/arm64 (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/armel (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/armel (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/armhf (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/armhf (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/i386 (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/i386 (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/mips64el (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/mips64el (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/ppc64el (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/ppc64el (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csmith/s390x (2.3.0-7 to 2.3.0-7)
  • Migration status for csmith/s390x (2.3.0-7 to 2.3.0-7): Will attempt migration (Any information below is purely informational)
• csound/amd64 (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/amd64 (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/arm64 (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/arm64 (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/armel (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/armel (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/armhf (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/armhf (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/i386 (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/i386 (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/mips64el (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/mips64el (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/ppc64el (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/ppc64el (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• csound/s390x (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1)
  • Migration status for csound/s390x (1:6.18.1+dfsg-1 to 1:6.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ctemplate/amd64 (2.4-3 to 2.4-3)
  • Migration status for ctemplate/amd64 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/arm64 (2.4-3 to 2.4-3)
  • Migration status for ctemplate/arm64 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/armel (2.4-3 to 2.4-3)
  • Migration status for ctemplate/armel (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/armhf (2.4-3 to 2.4-3)
  • Migration status for ctemplate/armhf (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/i386 (2.4-3 to 2.4-3)
  • Migration status for ctemplate/i386 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/mips64el (2.4-3 to 2.4-3)
  • Migration status for ctemplate/mips64el (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/ppc64el (2.4-3 to 2.4-3)
  • Migration status for ctemplate/ppc64el (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctemplate/s390x (2.4-3 to 2.4-3)
  • Migration status for ctemplate/s390x (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ctpl/amd64 (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/amd64 (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/arm64 (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/arm64 (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/armel (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/armel (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/armhf (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/armhf (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/i386 (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/i386 (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/mips64el (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/mips64el (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/ppc64el (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/ppc64el (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• ctpl/s390x (0.3.4+dfsg-4 to 0.3.4+dfsg-4)
  • Migration status for ctpl/s390x (0.3.4+dfsg-4 to 0.3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• cups-filters/amd64 (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/amd64 (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/arm64 (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/arm64 (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/armel (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/armel (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/armhf (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/armhf (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/i386 (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/i386 (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/mips64el (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/mips64el (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/ppc64el (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/ppc64el (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups-filters/s390x (1.28.17-3 to 1.28.17-3)
  • Migration status for cups-filters/s390x (1.28.17-3 to 1.28.17-3): Will attempt migration (Any information below is purely informational)
• cups/amd64 (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/amd64 (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/arm64 (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/arm64 (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/armel (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/armel (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/armhf (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/armhf (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/i386 (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/i386 (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/mips64el (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/mips64el (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/ppc64el (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/ppc64el (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• cups/s390x (2.4.7-1 to 2.4.7-1)
  • Migration status for cups/s390x (2.4.7-1 to 2.4.7-1): Will attempt migration (Any information below is purely informational)
• curl_pu (8.5.0-2 to 7.88.1-10+deb12u5)
  • Migration status for curl_pu (8.5.0-2 to 7.88.1-10+deb12u5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: curl is newer in the target suite (8.5.0-2 7.88.1-10+deb12u5)
• curlpp/amd64 (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/amd64 (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/arm64 (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/arm64 (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/armel (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/armel (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/armhf (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/armhf (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/i386 (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/i386 (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/mips64el (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/mips64el (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/ppc64el (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/ppc64el (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• curlpp/s390x (0.8.1-5.1 to 0.8.1-5.1)
  • Migration status for curlpp/s390x (0.8.1-5.1 to 0.8.1-5.1): Will attempt migration (Any information below is purely informational)
• cvc4/amd64 (1.8-3 to 1.8-3)
  • Migration status for cvc4/amd64 (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/arm64 (1.8-3 to 1.8-3)
  • Migration status for cvc4/arm64 (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/armel (1.8-3 to 1.8-3)
  • Migration status for cvc4/armel (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/armhf (1.8-3 to 1.8-3)
  • Migration status for cvc4/armhf (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/i386 (1.8-3 to 1.8-3)
  • Migration status for cvc4/i386 (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/mips64el (1.8-3 to 1.8-3)
  • Migration status for cvc4/mips64el (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/ppc64el (1.8-3 to 1.8-3)
  • Migration status for cvc4/ppc64el (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc4/s390x (1.8-3 to 1.8-3)
  • Migration status for cvc4/s390x (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc5/amd64 (1.0.5-3 to 1.0.5-3)
  • Migration status for cvc5/amd64 (1.0.5-3 to 1.0.5-3): Will attempt migration (Any information below is purely informational)
• cvc5/arm64 (1.0.5-3 to 1.0.5-3)
  • Migration status for cvc5/arm64 (1.0.5-3 to 1.0.5-3): Will attempt migration (Any information below is purely informational)
• cvc5/ppc64el (1.0.5-3 to 1.0.5-3)
  • Migration status for cvc5/ppc64el (1.0.5-3 to 1.0.5-3): Will attempt migration (Any information below is purely informational)
• cvc5/s390x (1.0.5-3 to 1.0.5-3)
  • Migration status for cvc5/s390x (1.0.5-3 to 1.0.5-3): Will attempt migration (Any information below is purely informational)
• cwidget/amd64 (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/amd64 (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/arm64 (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/arm64 (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/armel (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/armel (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/armhf (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/armhf (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/i386 (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/i386 (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/mips64el (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/mips64el (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/ppc64el (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/ppc64el (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwidget/s390x (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/s390x (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cyclonedds/amd64 (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/amd64 (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/arm64 (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/arm64 (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/armel (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/armel (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/armhf (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/armhf (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/i386 (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/i386 (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/mips64el (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/mips64el (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/ppc64el (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/ppc64el (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyclonedds/s390x (0.10.4-1 to 0.10.4-1)
  • Migration status for cyclonedds/s390x (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/amd64 (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/amd64 (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/arm64 (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/arm64 (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/armel (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/armel (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/armhf (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/armhf (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/i386 (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/i386 (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/mips64el (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/mips64el (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/ppc64el (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/ppc64el (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• cyrus-sasl2/s390x (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4)
  • Migration status for cyrus-sasl2/s390x (2.1.28+dfsg1-4 to 2.1.28+dfsg1-4): Will attempt migration (Any information below is purely informational)
• czmq/amd64 (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/amd64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/arm64 (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/arm64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/armel (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/armel (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/armhf (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/armhf (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/i386 (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/i386 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/mips64el (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/mips64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/ppc64el (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/ppc64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• czmq/s390x (4.2.1-1 to 4.2.1-1)
  • Migration status for czmq/s390x (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• d-spy/amd64 (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/amd64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/arm64 (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/arm64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/armel (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/armel (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/armhf (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/armhf (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/i386 (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/i386 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/mips64el (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/mips64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/ppc64el (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/ppc64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• d-spy/s390x (1.8.0-1 to 1.8.0-1)
  • Migration status for d-spy/s390x (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• dahdi-tools/amd64 (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/amd64 (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/arm64 (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/arm64 (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/armel (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/armel (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/armhf (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/armhf (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/i386 (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/i386 (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/mips64el (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/mips64el (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/ppc64el (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/ppc64el (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dahdi-tools/s390x (1:3.1.0-2 to 1:3.1.0-2)
  • Migration status for dahdi-tools/s390x (1:3.1.0-2 to 1:3.1.0-2): Will attempt migration (Any information below is purely informational)
• dante/amd64 (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/amd64 (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/arm64 (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/arm64 (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/armel (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/armel (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/armhf (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/armhf (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/i386 (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/i386 (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/mips64el (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/mips64el (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/ppc64el (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/ppc64el (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• dante/s390x (1.4.2+dfsg-7 to 1.4.2+dfsg-7)
  • Migration status for dante/s390x (1.4.2+dfsg-7 to 1.4.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• darkradiant/amd64 (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/amd64 (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/arm64 (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/arm64 (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/armel (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/armel (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/armhf (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/armhf (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/i386 (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/i386 (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/mips64el (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/mips64el (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/ppc64el (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/ppc64el (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• darkradiant/s390x (3.8.0-2 to 3.8.0-2)
  • Migration status for darkradiant/s390x (3.8.0-2 to 3.8.0-2): Will attempt migration (Any information below is purely informational)
• dart/amd64 (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13)
  • Migration status for dart/amd64 (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13): Will attempt migration (Any information below is purely informational)
• dart/arm64 (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13)
  • Migration status for dart/arm64 (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13): Will attempt migration (Any information below is purely informational)
• dart/armel (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13)
  • Migration status for dart/armel (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13): Will attempt migration (Any information below is purely informational)
• dart/armhf (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13)
  • Migration status for dart/armhf (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13): Will attempt migration (Any information below is purely informational)
• dart/i386 (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13)
  • Migration status for dart/i386 (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13): Will attempt migration (Any information below is purely informational)
• dart/ppc64el (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13)
  • Migration status for dart/ppc64el (6.12.1+dfsg4-13 to 6.12.1+dfsg4-13): Will attempt migration (Any information below is purely informational)
• dataquay/amd64 (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/amd64 (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/arm64 (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/arm64 (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/armel (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/armel (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/armhf (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/armhf (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/i386 (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/i386 (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/mips64el (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/mips64el (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/ppc64el (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/ppc64el (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dataquay/s390x (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/s390x (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• dav1d/amd64 (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/amd64 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/arm64 (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/arm64 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/armel (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/armel (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/armhf (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/armhf (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/i386 (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/i386 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/mips64el (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/mips64el (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/ppc64el (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/ppc64el (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• dav1d/s390x (1.3.0-2 to 1.3.0-2)
  • Migration status for dav1d/s390x (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• davix/amd64 (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/amd64 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/arm64 (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/arm64 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/armel (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/armel (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/armhf (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/armhf (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/i386 (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/i386 (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/mips64el (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/mips64el (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/ppc64el (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/ppc64el (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• davix/s390x (0.8.5-1 to 0.8.5-1)
  • Migration status for davix/s390x (0.8.5-1 to 0.8.5-1): Will attempt migration (Any information below is purely informational)
• db5.3/amd64 (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/amd64 (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/arm64 (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/arm64 (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/armel (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/armel (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/armhf (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/armhf (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/i386 (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/i386 (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/mips64el (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/mips64el (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/ppc64el (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/ppc64el (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• db5.3/s390x (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4)
  • Migration status for db5.3/s390x (5.3.28+dfsg2-4 to 5.3.28+dfsg2-4): Will attempt migration (Any information below is purely informational)
• dbus-c++/amd64 (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/amd64 (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/amd64 efl (not considered)
    • Invalidated by dependency
• dbus-c++/arm64 (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/arm64 (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/arm64 efl (not considered)
    • Invalidated by dependency
• dbus-c++/armel (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/armel (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/armel efl (not considered)
    • Invalidated by dependency
• dbus-c++/armhf (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/armhf (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/armhf efl (not considered)
    • Invalidated by dependency
• dbus-c++/i386 (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/i386 (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/i386 efl (not considered)
    • Invalidated by dependency
• dbus-c++/mips64el (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/mips64el (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/mips64el efl (not considered)
    • Invalidated by dependency
• dbus-c++/ppc64el (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/ppc64el (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/ppc64el efl (not considered)
    • Invalidated by dependency
• dbus-c++/s390x (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/s390x (0.9.0-12 to 0.9.0-12): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dbus-c++/s390x efl (not considered)
    • Invalidated by dependency
• dbus-cpp/amd64 (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/amd64 (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/arm64 (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/arm64 (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/armel (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/armel (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/armhf (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/armhf (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/i386 (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/i386 (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/mips64el (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/mips64el (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/ppc64el (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/ppc64el (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-cpp/s390x (5.0.3-6 to 5.0.3-6)
  • Migration status for dbus-cpp/s390x (5.0.3-6 to 5.0.3-6): Will attempt migration (Any information below is purely informational)
• dbus-glib/amd64 (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/amd64 (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/arm64 (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/arm64 (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/armel (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/armel (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/armhf (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/armhf (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/i386 (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/i386 (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/mips64el (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/mips64el (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/ppc64el (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/ppc64el (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-glib/s390x (0.112-3 to 0.112-3)
  • Migration status for dbus-glib/s390x (0.112-3 to 0.112-3): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/amd64 (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/amd64 (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/arm64 (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/arm64 (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/armel (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/armel (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/armhf (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/armhf (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/i386 (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/i386 (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/mips64el (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/mips64el (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/ppc64el (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/ppc64el (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus-test-runner/s390x (19.04.0-1 to 19.04.0-1)
  • Migration status for dbus-test-runner/s390x (19.04.0-1 to 19.04.0-1): Will attempt migration (Any information below is purely informational)
• dbus/amd64 (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/amd64 (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/arm64 (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/arm64 (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/armel (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/armel (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/armhf (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/armhf (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/i386 (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/i386 (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/mips64el (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/mips64el (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/ppc64el (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/ppc64el (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dbus/s390x (1.14.10-3 to 1.14.10-3)
  • Migration status for dbus/s390x (1.14.10-3 to 1.14.10-3): Will attempt migration (Any information below is purely informational)
• dcap/amd64 (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/amd64 (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcap/arm64 (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/arm64 (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcap/armel (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/armel (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcap/armhf (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/armhf (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcap/i386 (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/i386 (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcap/ppc64el (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/ppc64el (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcap/s390x (2.47.14-1 to 2.47.14-1)
  • Migration status for dcap/s390x (2.47.14-1 to 2.47.14-1): Will attempt migration (Any information below is purely informational)
• dcmtk/amd64 (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/amd64 (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dcmtk/arm64 (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/arm64 (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dcmtk/armhf (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/armhf (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dcmtk/i386 (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/i386 (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dcmtk/mips64el (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/mips64el (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dcmtk/ppc64el (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/ppc64el (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dcmtk/s390x (3.6.7-9 to 3.6.7-9)
  • Migration status for dcmtk/s390x (3.6.7-9 to 3.6.7-9): Will attempt migration (Any information below is purely informational)
• dconf/amd64 (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/amd64 (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/arm64 (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/arm64 (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/armel (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/armel (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/armhf (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/armhf (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/i386 (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/i386 (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/mips64el (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/mips64el (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/ppc64el (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/ppc64el (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dconf/s390x (0.40.0-4 to 0.40.0-4)
  • Migration status for dconf/s390x (0.40.0-4 to 0.40.0-4): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/amd64 (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/amd64 (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/arm64 (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/arm64 (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/armel (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/armel (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/armhf (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/armhf (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/i386 (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/i386 (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/mips64el (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/mips64el (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/ppc64el (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/ppc64el (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd-opentracing-cpp/s390x (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/s390x (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dde-network-utils/amd64 (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/amd64 (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/arm64 (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/arm64 (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/armel (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/armel (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/armhf (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/armhf (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/i386 (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/i386 (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/mips64el (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/mips64el (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/ppc64el (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/ppc64el (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-network-utils/s390x (5.4.13-2 to 5.4.13-2)
  • Migration status for dde-network-utils/s390x (5.4.13-2 to 5.4.13-2): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/amd64 (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/amd64 (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/arm64 (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/arm64 (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/armel (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/armel (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/armhf (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/armhf (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/i386 (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/i386 (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/mips64el (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/mips64el (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/ppc64el (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/ppc64el (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• dde-qt-dbus-factory/s390x (5.5.22-1 to 5.5.22-1)
  • Migration status for dde-qt-dbus-factory/s390x (5.5.22-1 to 5.5.22-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debconf-kde/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• debian-edu-artwork_pu (2.12.4-1 to 2.12.3-2~deb12u1)
  • Migration status for debian-edu-artwork_pu (2.12.4-1 to 2.12.3-2~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: debian-edu-artwork is newer in the target suite (2.12.4-1 2.12.3-2~deb12u1)
• deepin-movie-reborn/amd64 (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/amd64 (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/arm64 (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/arm64 (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/armel (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/armel (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/armhf (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/armhf (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/i386 (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/i386 (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/mips64el (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/mips64el (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/ppc64el (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/ppc64el (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• deepin-movie-reborn/s390x (5.10.8-2 to 5.10.8-2)
  • Migration status for deepin-movie-reborn/s390x (5.10.8-2 to 5.10.8-2): Will attempt migration (Any information below is purely informational)
• devhelp/amd64 (43.0-4 to 43.0-4)
  • Migration status for devhelp/amd64 (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/arm64 (43.0-4 to 43.0-4)
  • Migration status for devhelp/arm64 (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/armel (43.0-4 to 43.0-4)
  • Migration status for devhelp/armel (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/armhf (43.0-4 to 43.0-4)
  • Migration status for devhelp/armhf (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/i386 (43.0-4 to 43.0-4)
  • Migration status for devhelp/i386 (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/mips64el (43.0-4 to 43.0-4)
  • Migration status for devhelp/mips64el (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/ppc64el (43.0-4 to 43.0-4)
  • Migration status for devhelp/ppc64el (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devhelp/s390x (43.0-4 to 43.0-4)
  • Migration status for devhelp/s390x (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/amd64 (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/amd64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/arm64 (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/arm64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/armel (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/armel (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/armhf (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/armhf (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/i386 (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/i386 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/mips64el (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/mips64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/ppc64el (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/ppc64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• device-tree-compiler/s390x (1.7.0-1 to 1.7.0-1)
  • Migration status for device-tree-compiler/s390x (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• deviceinfo/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for deviceinfo/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• dico/amd64 (2.11-4 to 2.11-4)
  • Migration status for dico/amd64 (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/arm64 (2.11-4 to 2.11-4)
  • Migration status for dico/arm64 (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/armel (2.11-4 to 2.11-4)
  • Migration status for dico/armel (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/armhf (2.11-4 to 2.11-4)
  • Migration status for dico/armhf (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/i386 (2.11-4 to 2.11-4)
  • Migration status for dico/i386 (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/mips64el (2.11-4 to 2.11-4)
  • Migration status for dico/mips64el (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/ppc64el (2.11-4 to 2.11-4)
  • Migration status for dico/ppc64el (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dico/s390x (2.11-4 to 2.11-4)
  • Migration status for dico/s390x (2.11-4 to 2.11-4): Will attempt migration (Any information below is purely informational)
• dicomscope/amd64 (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/amd64 (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/arm64 (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/arm64 (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/armel (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/armel (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/armhf (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/armhf (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/i386 (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/i386 (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/mips64el (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/mips64el (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/ppc64el (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/ppc64el (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dicomscope/s390x (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/s390x (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• ding-libs/amd64 (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/amd64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/arm64 (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/arm64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/armel (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/armel (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/armhf (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/armhf (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/i386 (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/i386 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/mips64el (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/mips64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/ppc64el (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/ppc64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• ding-libs/s390x (0.6.2-2 to 0.6.2-2)
  • Migration status for ding-libs/s390x (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• diodon/amd64 (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/amd64 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/arm64 (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/arm64 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/armel (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/armel (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/armhf (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/armhf (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/i386 (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/i386 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/mips64el (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/mips64el (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/ppc64el (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/ppc64el (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• diodon/s390x (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/s390x (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• dipy/amd64 (1.7.0-4 to 1.7.0-4)
  • Migration status for dipy/amd64 (1.7.0-4 to 1.7.0-4): Will attempt migration (Any information below is purely informational)
• dipy/arm64 (1.7.0-4 to 1.7.0-4)
  • Migration status for dipy/arm64 (1.7.0-4 to 1.7.0-4): Will attempt migration (Any information below is purely informational)
• dipy/armel (1.7.0-4 to 1.7.0-4)
  • Migration status for dipy/armel (1.7.0-4 to 1.7.0-4): Will attempt migration (Any information below is purely informational)
• dipy/armhf (1.7.0-4 to 1.7.0-4)
  • Migration status for dipy/armhf (1.7.0-4 to 1.7.0-4): Will attempt migration (Any information below is purely informational)
• dipy/i386 (1.7.0-4 to 1.7.0-4)
  • Migration status for dipy/i386 (1.7.0-4 to 1.7.0-4): Will attempt migration (Any information below is purely informational)
• dipy/s390x (1.7.0-4 to 1.7.0-4)
  • Migration status for dipy/s390x (1.7.0-4 to 1.7.0-4): Will attempt migration (Any information below is purely informational)
• dirdiff/amd64 (2.1-9 to 2.1-9)
  • Migration status for dirdiff/amd64 (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/arm64 (2.1-9 to 2.1-9)
  • Migration status for dirdiff/arm64 (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/armel (2.1-9 to 2.1-9)
  • Migration status for dirdiff/armel (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/armhf (2.1-9 to 2.1-9)
  • Migration status for dirdiff/armhf (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/i386 (2.1-9 to 2.1-9)
  • Migration status for dirdiff/i386 (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/mips64el (2.1-9 to 2.1-9)
  • Migration status for dirdiff/mips64el (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/ppc64el (2.1-9 to 2.1-9)
  • Migration status for dirdiff/ppc64el (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• dirdiff/s390x (2.1-9 to 2.1-9)
  • Migration status for dirdiff/s390x (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• directfb/amd64 (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/amd64 (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/arm64 (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/arm64 (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/armel (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/armel (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/armhf (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/armhf (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/i386 (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/i386 (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/mips64el (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/mips64el (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/ppc64el (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/ppc64el (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• directfb/s390x (1.7.7-11 to 1.7.7-11)
  • Migration status for directfb/s390x (1.7.7-11 to 1.7.7-11): Will attempt migration (Any information below is purely informational)
• discount/amd64 (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/amd64 (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/arm64 (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/arm64 (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/armel (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/armel (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/armhf (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/armhf (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/i386 (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/i386 (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/mips64el (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/mips64el (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/ppc64el (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/ppc64el (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• discount/s390x (2.2.7-2 to 2.2.7-2)
  • Migration status for discount/s390x (2.2.7-2 to 2.2.7-2): Will attempt migration (Any information below is purely informational)
• distorm3/amd64 (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/amd64 (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/arm64 (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/arm64 (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/armel (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/armel (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/armhf (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/armhf (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/i386 (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/i386 (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/mips64el (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/mips64el (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/ppc64el (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/ppc64el (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• distorm3/s390x (3.5.2b-3 to 3.5.2b-3)
  • Migration status for distorm3/s390x (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
• dleyna/amd64 (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/amd64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/arm64 (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/arm64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/armel (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/armel (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/armhf (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/armhf (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/i386 (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/i386 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/mips64el (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/mips64el (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/ppc64el (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/ppc64el (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dleyna/s390x (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/s390x (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dlib/amd64 (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/amd64 (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/arm64 (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/arm64 (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/armel (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/armel (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/armhf (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/armhf (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/i386 (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/i386 (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/mips64el (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/mips64el (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/ppc64el (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/ppc64el (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlib/s390x (19.24+dfsg-1 to 19.24+dfsg-1)
  • Migration status for dlib/s390x (19.24+dfsg-1 to 19.24+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlm/amd64 (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/amd64 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/arm64 (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/arm64 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/armel (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/armel (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/armhf (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/armhf (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/i386 (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/i386 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/mips64el (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/mips64el (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/ppc64el (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/ppc64el (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlm/s390x (4.2.0-3 to 4.2.0-3)
  • Migration status for dlm/s390x (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• dlt-daemon/amd64 (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/amd64 (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/arm64 (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/arm64 (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/armel (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/armel (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/armhf (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/armhf (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/i386 (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/i386 (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/mips64el (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/mips64el (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/ppc64el (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/ppc64el (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-daemon/s390x (2.18.10-9 to 2.18.10-9)
  • Migration status for dlt-daemon/s390x (2.18.10-9 to 2.18.10-9): Will attempt migration (Any information below is purely informational)
• dlt-viewer/amd64 (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/amd64 (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/arm64 (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/arm64 (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/armel (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/armel (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/armhf (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/armhf (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/i386 (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/i386 (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/mips64el (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/mips64el (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/ppc64el (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/ppc64el (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/s390x (2.25.0+dfsg-1 to 2.25.0+dfsg-1)
  • Migration status for dlt-viewer/s390x (2.25.0+dfsg-1 to 2.25.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• dmalloc/amd64 (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/amd64 (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/arm64 (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/arm64 (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/armel (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/armel (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/armhf (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/armhf (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/i386 (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/i386 (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/mips64el (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/mips64el (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/ppc64el (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/ppc64el (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• dmalloc/s390x (5.5.2-14 to 5.5.2-14)
  • Migration status for dmalloc/s390x (5.5.2-14 to 5.5.2-14): Will attempt migration (Any information below is purely informational)
• docopt.cpp/amd64 (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/amd64 (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/arm64 (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/arm64 (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/armel (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/armel (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/armhf (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/armhf (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/i386 (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/i386 (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/mips64el (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/mips64el (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/ppc64el (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/ppc64el (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• docopt.cpp/s390x (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/s390x (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• dolphin/amd64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/amd64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/arm64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/arm64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/armel (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/armel (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/armhf (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/armhf (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/i386 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/i386 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/mips64el (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/mips64el (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/ppc64el (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/ppc64el (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/s390x (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/s390x (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• doodle/amd64 (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/amd64 (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/arm64 (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/arm64 (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/armel (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/armel (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/armhf (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/armhf (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/i386 (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/i386 (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/mips64el (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/mips64el (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/ppc64el (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/ppc64el (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• doodle/s390x (0.7.2-7 to 0.7.2-7)
  • Migration status for doodle/s390x (0.7.2-7 to 0.7.2-7): Will attempt migration (Any information below is purely informational)
• dotconf/amd64 (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/amd64 (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/arm64 (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/arm64 (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/armel (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/armel (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/armhf (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/armhf (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/i386 (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/i386 (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/mips64el (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/mips64el (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/ppc64el (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/ppc64el (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dotconf/s390x (1.3-0.3 to 1.3-0.3)
  • Migration status for dotconf/s390x (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• dothost/amd64 (0.2-7 to 0.2-7)
  • Migration status for dothost/amd64 (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/arm64 (0.2-7 to 0.2-7)
  • Migration status for dothost/arm64 (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/armel (0.2-7 to 0.2-7)
  • Migration status for dothost/armel (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/armhf (0.2-7 to 0.2-7)
  • Migration status for dothost/armhf (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/i386 (0.2-7 to 0.2-7)
  • Migration status for dothost/i386 (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/mips64el (0.2-7 to 0.2-7)
  • Migration status for dothost/mips64el (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/ppc64el (0.2-7 to 0.2-7)
  • Migration status for dothost/ppc64el (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• dothost/s390x (0.2-7 to 0.2-7)
  • Migration status for dothost/s390x (0.2-7 to 0.2-7): Will attempt migration (Any information below is purely informational)
• double-conversion/amd64 (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/amd64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/arm64 (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/arm64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/armel (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/armel (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/armhf (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/armhf (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/i386 (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/i386 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/mips64el (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/mips64el (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/ppc64el (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/ppc64el (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• double-conversion/s390x (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/s390x (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• draco/amd64 (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/amd64 (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/arm64 (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/arm64 (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/armel (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/armel (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/armhf (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/armhf (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/i386 (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/i386 (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/mips64el (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/mips64el (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/ppc64el (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/ppc64el (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• draco/s390x (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/s390x (1.5.6+dfsg-3 to 1.5.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• dragonbox/amd64 (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/amd64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/arm64 (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/arm64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/armel (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/armel (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/armhf (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/armhf (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/i386 (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/i386 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/mips64el (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/mips64el (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/ppc64el (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/ppc64el (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dragonbox/s390x (1.1.3-1 to 1.1.3-1)
  • Migration status for dragonbox/s390x (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• dsdcc/amd64 (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/amd64 (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/arm64 (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/arm64 (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/armel (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/armel (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/armhf (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/armhf (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/i386 (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/i386 (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/mips64el (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/mips64el (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/ppc64el (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/ppc64el (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsdcc/s390x (1.9.3-2 to 1.9.3-2)
  • Migration status for dsdcc/s390x (1.9.3-2 to 1.9.3-2): Will attempt migration (Any information below is purely informational)
• dsfmt/amd64 (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/amd64 (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/arm64 (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/arm64 (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/armel (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/armel (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/armhf (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/armhf (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/i386 (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/i386 (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/mips64el (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/mips64el (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/ppc64el (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/ppc64el (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dsfmt/s390x (2.2.3+dfsg-5 to 2.2.3+dfsg-5)
  • Migration status for dsfmt/s390x (2.2.3+dfsg-5 to 2.2.3+dfsg-5): Will attempt migration (Any information below is purely informational)
• dt-utils/amd64 (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/amd64 (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/arm64 (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/arm64 (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/armel (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/armel (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/armhf (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/armhf (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/i386 (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/i386 (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/mips64el (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/mips64el (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/ppc64el (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/ppc64el (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dt-utils/s390x (2021.03.0+ds-2 to 2021.03.0+ds-2)
  • Migration status for dt-utils/s390x (2021.03.0+ds-2 to 2021.03.0+ds-2): Will attempt migration (Any information below is purely informational)
• dtkgui/amd64 (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/amd64 (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/arm64 (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/arm64 (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/armel (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/armel (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/armhf (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/armhf (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/i386 (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/i386 (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/mips64el (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/mips64el (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/ppc64el (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/ppc64el (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkgui/s390x (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/s390x (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkwidget/amd64 (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/amd64 (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/arm64 (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/arm64 (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/armel (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/armel (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/armhf (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/armhf (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/i386 (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/i386 (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/mips64el (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/mips64el (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/ppc64el (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/ppc64el (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• dtkwidget/s390x (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/s390x (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• duktape/amd64 (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/amd64 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/arm64 (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/arm64 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/armel (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/armel (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/armhf (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/armhf (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/i386 (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/i386 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/mips64el (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/mips64el (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/ppc64el (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/ppc64el (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• duktape/s390x (2.7.0-2 to 2.7.0-2)
  • Migration status for duktape/s390x (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• dune-geometry/amd64 (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/amd64 (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/arm64 (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/arm64 (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/armel (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/armel (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/armhf (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/armhf (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/i386 (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/i386 (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/mips64el (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/mips64el (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/ppc64el (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/ppc64el (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-geometry/s390x (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/s390x (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/amd64 (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/amd64 (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/arm64 (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/arm64 (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/armel (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/armel (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/armhf (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/armhf (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/i386 (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/i386 (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/mips64el (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/mips64el (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/ppc64el (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/ppc64el (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/s390x (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/s390x (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid/amd64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-grid/amd64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-grid/arm64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-grid/arm64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-grid/armel (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-grid/armel (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-grid/armhf (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-grid/armhf (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-grid/mips64el (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-grid/mips64el (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-grid/s390x (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-grid/s390x (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/amd64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/amd64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/arm64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/arm64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/armel (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/armel (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/armhf (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/armhf (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/i386 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/i386 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/mips64el (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/mips64el (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/ppc64el (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/ppc64el (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/s390x (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/s390x (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dyssol/amd64 (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/amd64 (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/arm64 (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/arm64 (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/armel (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/armel (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/armhf (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/armhf (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/i386 (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/i386 (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/mips64el (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/mips64el (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/ppc64el (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/ppc64el (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• dyssol/s390x (1.1.1+ds1-2 to 1.1.1+ds1-2)
  • Migration status for dyssol/s390x (1.1.1+ds1-2 to 1.1.1+ds1-2): Will attempt migration (Any information below is purely informational)
• eb/amd64 (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/amd64 (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/arm64 (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/arm64 (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/armel (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/armel (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/armhf (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/armhf (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/i386 (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/i386 (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/mips64el (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/mips64el (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/ppc64el (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/ppc64el (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eb/s390x (4.4.3-14 to 4.4.3-14)
  • Migration status for eb/s390x (4.4.3-14 to 4.4.3-14): Will attempt migration (Any information below is purely informational)
• eckit/amd64 (1.25.0-1 to 1.25.0-1)
  • Migration status for eckit/amd64 (1.25.0-1 to 1.25.0-1): Will attempt migration (Any information below is purely informational)
• eckit/arm64 (1.25.0-1 to 1.25.0-1)
  • Migration status for eckit/arm64 (1.25.0-1 to 1.25.0-1): Will attempt migration (Any information below is purely informational)
• eckit/mips64el (1.25.0-1 to 1.25.0-1)
  • Migration status for eckit/mips64el (1.25.0-1 to 1.25.0-1): Will attempt migration (Any information below is purely informational)
• eckit/ppc64el (1.25.0-1 to 1.25.0-1)
  • Migration status for eckit/ppc64el (1.25.0-1 to 1.25.0-1): Will attempt migration (Any information below is purely informational)
• eckit/s390x (1.25.0-1 to 1.25.0-1)
  • Migration status for eckit/s390x (1.25.0-1 to 1.25.0-1): Will attempt migration (Any information below is purely informational)
• ecl/amd64 (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/amd64 (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/arm64 (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/arm64 (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/armel (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/armel (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/armhf (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/armhf (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/i386 (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/i386 (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/mips64el (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/mips64el (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/ppc64el (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/ppc64el (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecl/s390x (21.2.1+ds-4 to 21.2.1+ds-4)
  • Migration status for ecl/s390x (21.2.1+ds-4 to 21.2.1+ds-4): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/amd64 (111-6 to 111-6)
  • Migration status for ecryptfs-utils/amd64 (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/arm64 (111-6 to 111-6)
  • Migration status for ecryptfs-utils/arm64 (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/armel (111-6 to 111-6)
  • Migration status for ecryptfs-utils/armel (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/armhf (111-6 to 111-6)
  • Migration status for ecryptfs-utils/armhf (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/i386 (111-6 to 111-6)
  • Migration status for ecryptfs-utils/i386 (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/mips64el (111-6 to 111-6)
  • Migration status for ecryptfs-utils/mips64el (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/ppc64el (111-6 to 111-6)
  • Migration status for ecryptfs-utils/ppc64el (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• ecryptfs-utils/s390x (111-6 to 111-6)
  • Migration status for ecryptfs-utils/s390x (111-6 to 111-6): Will attempt migration (Any information below is purely informational)
• edflib/amd64 (1.24-1 to 1.24-1)
  • Migration status for edflib/amd64 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edflib/arm64 (1.24-1 to 1.24-1)
  • Migration status for edflib/arm64 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edflib/armel (1.24-1 to 1.24-1)
  • Migration status for edflib/armel (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edflib/armhf (1.24-1 to 1.24-1)
  • Migration status for edflib/armhf (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edflib/i386 (1.24-1 to 1.24-1)
  • Migration status for edflib/i386 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edflib/mips64el (1.24-1 to 1.24-1)
  • Migration status for edflib/mips64el (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edflib/ppc64el (1.24-1 to 1.24-1)
  • Migration status for edflib/ppc64el (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/amd64 (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/amd64 (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/arm64 (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/arm64 (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/armel (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/armel (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/armhf (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/armhf (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/i386 (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/i386 (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/mips64el (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/mips64el (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/ppc64el (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/ppc64el (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• edge-addition-planarity-suite/s390x (3.0.2.0-2 to 3.0.2.0-2)
  • Migration status for edge-addition-planarity-suite/s390x (3.0.2.0-2 to 3.0.2.0-2): Will attempt migration (Any information below is purely informational)
• editorconfig-core/amd64 (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/amd64 (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• editorconfig-core/arm64 (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/arm64 (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• editorconfig-core/armel (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/armel (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• editorconfig-core/armhf (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/armhf (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• editorconfig-core/mips64el (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/mips64el (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• editorconfig-core/ppc64el (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/ppc64el (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• editorconfig-core/s390x (0.12.6-0.1 to 0.12.6-0.1)
  • Migration status for editorconfig-core/s390x (0.12.6-0.1 to 0.12.6-0.1): Will attempt migration (Any information below is purely informational)
• efibootguard/amd64 (0.15-1 to 0.15-1)
  • Migration status for efibootguard/amd64 (0.15-1 to 0.15-1): Will attempt migration (Any information below is purely informational)
• efibootguard/arm64 (0.15-1 to 0.15-1)
  • Migration status for efibootguard/arm64 (0.15-1 to 0.15-1): Will attempt migration (Any information below is purely informational)
• efibootguard/armhf (0.15-1 to 0.15-1)
  • Migration status for efibootguard/armhf (0.15-1 to 0.15-1): Will attempt migration (Any information below is purely informational)
• efibootguard/i386 (0.15-1 to 0.15-1)
  • Migration status for efibootguard/i386 (0.15-1 to 0.15-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/amd64 (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/amd64 (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/arm64 (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/arm64 (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/armel (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/armel (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/armhf (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/armhf (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/i386 (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/i386 (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/mips64el (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/mips64el (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/ppc64el (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/ppc64el (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• egl-wayland/s390x (1:1.1.12-1 to 1:1.1.12-1)
  • Migration status for egl-wayland/s390x (1:1.1.12-1 to 1:1.1.12-1): Will attempt migration (Any information below is purely informational)
• elfutils/amd64 (0.190-1 to 0.190-1)
  • Migration status for elfutils/amd64 (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/arm64 (0.190-1 to 0.190-1)
  • Migration status for elfutils/arm64 (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/armel (0.190-1 to 0.190-1)
  • Migration status for elfutils/armel (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/armhf (0.190-1 to 0.190-1)
  • Migration status for elfutils/armhf (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/i386 (0.190-1 to 0.190-1)
  • Migration status for elfutils/i386 (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/mips64el (0.190-1 to 0.190-1)
  • Migration status for elfutils/mips64el (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/ppc64el (0.190-1 to 0.190-1)
  • Migration status for elfutils/ppc64el (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• elfutils/s390x (0.190-1 to 0.190-1)
  • Migration status for elfutils/s390x (0.190-1 to 0.190-1): Will attempt migration (Any information below is purely informational)
• ell/amd64 (0.61-1 to 0.61-1)
  • Migration status for ell/amd64 (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/arm64 (0.61-1 to 0.61-1)
  • Migration status for ell/arm64 (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/armel (0.61-1 to 0.61-1)
  • Migration status for ell/armel (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/armhf (0.61-1 to 0.61-1)
  • Migration status for ell/armhf (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/i386 (0.61-1 to 0.61-1)
  • Migration status for ell/i386 (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/mips64el (0.61-1 to 0.61-1)
  • Migration status for ell/mips64el (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/ppc64el (0.61-1 to 0.61-1)
  • Migration status for ell/ppc64el (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• ell/s390x (0.61-1 to 0.61-1)
  • Migration status for ell/s390x (0.61-1 to 0.61-1): Will attempt migration (Any information below is purely informational)
• emoslib/amd64 (2:4.5.9-9 to 2:4.5.9-9)
  • Migration status for emoslib/amd64 (2:4.5.9-9 to 2:4.5.9-9): Will attempt migration (Any information below is purely informational)
• emoslib/arm64 (2:4.5.9-9 to 2:4.5.9-9)
  • Migration status for emoslib/arm64 (2:4.5.9-9 to 2:4.5.9-9): Will attempt migration (Any information below is purely informational)
• emoslib/mips64el (2:4.5.9-9 to 2:4.5.9-9)
  • Migration status for emoslib/mips64el (2:4.5.9-9 to 2:4.5.9-9): Will attempt migration (Any information below is purely informational)
• emoslib/ppc64el (2:4.5.9-9 to 2:4.5.9-9)
  • Migration status for emoslib/ppc64el (2:4.5.9-9 to 2:4.5.9-9): Will attempt migration (Any information below is purely informational)
• enca/amd64 (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/amd64 (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/arm64 (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/arm64 (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/armel (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/armel (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/armhf (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/armhf (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/i386 (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/i386 (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/mips64el (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/mips64el (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/ppc64el (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/ppc64el (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enca/s390x (1.19-1.1 to 1.19-1.1)
  • Migration status for enca/s390x (1.19-1.1 to 1.19-1.1): Will attempt migration (Any information below is purely informational)
• enchant-2/amd64 (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/amd64 (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/arm64 (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/arm64 (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/armel (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/armel (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/armhf (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/armhf (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/i386 (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/i386 (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/mips64el (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/mips64el (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/ppc64el (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/ppc64el (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enchant-2/s390x (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/s390x (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• enet/amd64 (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/amd64 (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/arm64 (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/arm64 (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/armel (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/armel (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/armhf (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/armhf (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/i386 (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/i386 (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/mips64el (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/mips64el (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/ppc64el (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/ppc64el (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• enet/s390x (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for enet/s390x (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• eog/amd64 (45.1-1 to 45.1-1)
  • Migration status for eog/amd64 (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/arm64 (45.1-1 to 45.1-1)
  • Migration status for eog/arm64 (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/armel (45.1-1 to 45.1-1)
  • Migration status for eog/armel (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/armhf (45.1-1 to 45.1-1)
  • Migration status for eog/armhf (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/i386 (45.1-1 to 45.1-1)
  • Migration status for eog/i386 (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/mips64el (45.1-1 to 45.1-1)
  • Migration status for eog/mips64el (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/ppc64el (45.1-1 to 45.1-1)
  • Migration status for eog/ppc64el (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eog/s390x (45.1-1 to 45.1-1)
  • Migration status for eog/s390x (45.1-1 to 45.1-1): Will attempt migration (Any information below is purely informational)
• eos-sdk/amd64 (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/amd64 (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/arm64 (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/arm64 (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/armel (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/armel (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/armhf (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/armhf (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/i386 (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/i386 (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/mips64el (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/mips64el (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/ppc64el (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/ppc64el (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• eos-sdk/s390x (0~git20230107+ds-5 to 0~git20230107+ds-5)
  • Migration status for eos-sdk/s390x (0~git20230107+ds-5 to 0~git20230107+ds-5): Will attempt migration (Any information below is purely informational)
• erfa/amd64 (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/amd64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/arm64 (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/arm64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/armel (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/armel (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/armhf (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/armhf (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/i386 (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/i386 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/mips64el (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/mips64el (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/ppc64el (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/ppc64el (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• erfa/s390x (2.0.1-1 to 2.0.1-1)
  • Migration status for erfa/s390x (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• espeak/amd64 (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/amd64 (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/arm64 (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/arm64 (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/armel (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/armel (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/armhf (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/armhf (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/i386 (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/i386 (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/mips64el (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/mips64el (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/ppc64el (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/ppc64el (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• espeak/s390x (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
  • Migration status for espeak/s390x (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
• evemu/amd64 (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/amd64 (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/arm64 (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/arm64 (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/armel (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/armel (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/armhf (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/armhf (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/i386 (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/i386 (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/mips64el (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/mips64el (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/ppc64el (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/ppc64el (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evemu/s390x (2.7.0-3 to 2.7.0-3)
  • Migration status for evemu/s390x (2.7.0-3 to 2.7.0-3): Will attempt migration (Any information below is purely informational)
• evince/amd64 (45.0-1 to 45.0-1)
  • Migration status for evince/amd64 (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/arm64 (45.0-1 to 45.0-1)
  • Migration status for evince/arm64 (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/armel (45.0-1 to 45.0-1)
  • Migration status for evince/armel (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/armhf (45.0-1 to 45.0-1)
  • Migration status for evince/armhf (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/i386 (45.0-1 to 45.0-1)
  • Migration status for evince/i386 (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/mips64el (45.0-1 to 45.0-1)
  • Migration status for evince/mips64el (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/ppc64el (45.0-1 to 45.0-1)
  • Migration status for evince/ppc64el (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evince/s390x (45.0-1 to 45.0-1)
  • Migration status for evince/s390x (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/amd64 (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/amd64 (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/arm64 (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/arm64 (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/armel (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/armel (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/armhf (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/armhf (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/i386 (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/i386 (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/mips64el (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/mips64el (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/ppc64el (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/ppc64el (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• evolution-data-server/s390x (3.50.2-1 to 3.50.2-1)
  • Migration status for evolution-data-server/s390x (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• execline/amd64 (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/amd64 (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/arm64 (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/arm64 (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/armel (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/armel (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/armhf (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/armhf (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/i386 (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/i386 (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/mips64el (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/mips64el (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/ppc64el (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/ppc64el (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• execline/s390x (2.9.4.0-1 to 2.9.4.0-1)
  • Migration status for execline/s390x (2.9.4.0-1 to 2.9.4.0-1): Will attempt migration (Any information below is purely informational)
• exiv2/amd64 (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/amd64 (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/arm64 (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/arm64 (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/armel (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/armel (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/armhf (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/armhf (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/i386 (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/i386 (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/mips64el (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/mips64el (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/ppc64el (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/ppc64el (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exiv2/s390x (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/s390x (0.27.6-1 to 0.27.6-1): Will attempt migration (Any information below is purely informational)
• exo/amd64 (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/amd64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/arm64 (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/arm64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/armel (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/armel (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/armhf (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/armhf (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/i386 (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/i386 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/mips64el (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/mips64el (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/ppc64el (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/ppc64el (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• exo/s390x (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/s390x (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• expat/amd64 (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/amd64 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/arm64 (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/arm64 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/armel (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/armel (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/armhf (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/armhf (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/i386 (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/i386 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/mips64el (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/mips64el (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/ppc64el (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/ppc64el (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• expat/s390x (2.5.0-2 to 2.5.0-2)
  • Migration status for expat/s390x (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• eztrace/amd64 (2.1-6 to 2.1-6)
  • Migration status for eztrace/amd64 (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• eztrace/arm64 (2.1-6 to 2.1-6)
  • Migration status for eztrace/arm64 (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• eztrace/armel (2.1-6 to 2.1-6)
  • Migration status for eztrace/armel (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• eztrace/armhf (2.1-6 to 2.1-6)
  • Migration status for eztrace/armhf (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• eztrace/mips64el (2.1-6 to 2.1-6)
  • Migration status for eztrace/mips64el (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• eztrace/ppc64el (2.1-6 to 2.1-6)
  • Migration status for eztrace/ppc64el (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• eztrace/s390x (2.1-6 to 2.1-6)
  • Migration status for eztrace/s390x (2.1-6 to 2.1-6): Will attempt migration (Any information below is purely informational)
• f2fs-tools/amd64 (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/amd64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/arm64 (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/arm64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/armel (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/armel (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/armhf (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/armhf (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/i386 (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/i386 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/mips64el (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/mips64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/ppc64el (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/ppc64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• f2fs-tools/s390x (1.16.0-1 to 1.16.0-1)
  • Migration status for f2fs-tools/s390x (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• faad2/amd64 (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/amd64 (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/arm64 (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/arm64 (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/armel (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/armel (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/armhf (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/armhf (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/i386 (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/i386 (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/mips64el (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/mips64el (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/ppc64el (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/ppc64el (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faad2/s390x (2.11.1-1 to 2.11.1-1)
  • Migration status for faad2/s390x (2.11.1-1 to 2.11.1-1): Will attempt migration (Any information below is purely informational)
• faifa/amd64 (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/amd64 (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/arm64 (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/arm64 (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/armel (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/armel (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/armhf (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/armhf (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/i386 (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/i386 (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/mips64el (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/mips64el (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/ppc64el (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/ppc64el (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• faifa/s390x (0.2~svn82-3 to 0.2~svn82-3)
  • Migration status for faifa/s390x (0.2~svn82-3 to 0.2~svn82-3): Will attempt migration (Any information below is purely informational)
• fakechroot/amd64 (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/amd64 (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/arm64 (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/arm64 (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/armel (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/armel (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/armhf (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/armhf (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/i386 (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/i386 (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/mips64el (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/mips64el (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/ppc64el (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/ppc64el (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakechroot/s390x (2.20.1+ds-15 to 2.20.1+ds-15)
  • Migration status for fakechroot/s390x (2.20.1+ds-15 to 2.20.1+ds-15): Will attempt migration (Any information below is purely informational)
• fakeroot/amd64 (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/amd64 (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/arm64 (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/arm64 (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/armel (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/armel (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/armhf (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/armhf (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/i386 (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/i386 (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/mips64el (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/mips64el (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/ppc64el (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/ppc64el (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• fakeroot/s390x (1.32.2-1 to 1.32.2-1)
  • Migration status for fakeroot/s390x (1.32.2-1 to 1.32.2-1): Will attempt migration (Any information below is purely informational)
• faketime/amd64 (0.9.10-2.1 to 0.9.10-2.1)
  • Migration status for faketime/amd64 (0.9.10-2.1 to 0.9.10-2.1): Will attempt migration (Any information below is purely informational)
• faketime/arm64 (0.9.10-2.1 to 0.9.10-2.1)
  • Migration status for faketime/arm64 (0.9.10-2.1 to 0.9.10-2.1): Will attempt migration (Any information below is purely informational)
• faketime/mips64el (0.9.10-2.1 to 0.9.10-2.1)
  • Migration status for faketime/mips64el (0.9.10-2.1 to 0.9.10-2.1): Will attempt migration (Any information below is purely informational)
• faketime/ppc64el (0.9.10-2.1 to 0.9.10-2.1)
  • Migration status for faketime/ppc64el (0.9.10-2.1 to 0.9.10-2.1): Will attempt migration (Any information below is purely informational)
• faketime/s390x (0.9.10-2.1 to 0.9.10-2.1)
  • Migration status for faketime/s390x (0.9.10-2.1 to 0.9.10-2.1): Will attempt migration (Any information below is purely informational)
• farstream-0.2/amd64 (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/amd64 (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/arm64 (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/arm64 (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/armel (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/armel (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/armhf (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/armhf (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/i386 (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/i386 (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/mips64el (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/mips64el (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/ppc64el (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/ppc64el (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• farstream-0.2/s390x (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/s390x (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• fastcdr/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastcdr/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for fastcdr/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• fastjet/amd64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/amd64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/arm64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/arm64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/armel (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/armel (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/armhf (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/armhf (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/i386 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/i386 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/mips64el (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/mips64el (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/ppc64el (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/ppc64el (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastjet/s390x (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/s390x (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fathom/amd64 (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/amd64 (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/arm64 (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/arm64 (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/armel (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/armel (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/armhf (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/armhf (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/i386 (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/i386 (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/mips64el (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/mips64el (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/ppc64el (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/ppc64el (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• fathom/s390x (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1)
  • Migration status for fathom/s390x (1.0+git.20190811.97fb5c-1 to 1.0+git.20190811.97fb5c-1): Will attempt migration (Any information below is purely informational)
• faudio/amd64 (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/amd64 (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/arm64 (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/arm64 (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/armel (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/armel (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/armhf (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/armhf (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/i386 (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/i386 (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/mips64el (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/mips64el (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/ppc64el (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/ppc64el (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• faudio/s390x (23.11+dfsg-1 to 23.11+dfsg-1)
  • Migration status for faudio/s390x (23.11+dfsg-1 to 23.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/amd64 (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/amd64 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/arm64 (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/arm64 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/armel (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/armel (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/armhf (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/armhf (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/i386 (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/i386 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/mips64el (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/mips64el (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/ppc64el (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/ppc64el (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-anthy/s390x (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/s390x (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/amd64 (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/amd64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/arm64 (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/arm64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/armel (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/armel (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/armhf (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/armhf (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/i386 (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/i386 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/mips64el (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/mips64el (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/ppc64el (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/ppc64el (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/s390x (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/s390x (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/amd64 (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/amd64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/arm64 (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/arm64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/armel (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/armel (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/armhf (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/armhf (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/i386 (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/i386 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/mips64el (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/mips64el (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/ppc64el (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/ppc64el (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/s390x (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/s390x (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/amd64 (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/amd64 (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/arm64 (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/arm64 (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/armel (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/armel (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/armhf (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/armhf (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/i386 (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/i386 (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/mips64el (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/mips64el (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/ppc64el (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/ppc64el (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/s390x (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/s390x (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/amd64 (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/amd64 (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/arm64 (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/arm64 (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/armel (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/armel (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/armhf (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/armhf (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/i386 (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/i386 (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/mips64el (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/mips64el (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/ppc64el (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/ppc64el (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/s390x (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/s390x (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/amd64 (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/amd64 (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/arm64 (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/arm64 (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/armel (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/armel (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/armhf (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/armhf (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/i386 (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/i386 (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/mips64el (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/mips64el (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/ppc64el (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/ppc64el (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-hangul/s390x (0.3.1-3 to 0.3.1-3)
  • Migration status for fcitx-hangul/s390x (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/amd64 (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/amd64 (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/arm64 (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/arm64 (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/armel (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/armel (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/armhf (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/armhf (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/i386 (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/i386 (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/mips64el (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/mips64el (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/ppc64el (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/ppc64el (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-libpinyin/s390x (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/s390x (0.5.4-5 to 0.5.4-5): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/amd64 (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/amd64 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/arm64 (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/arm64 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/armel (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/armel (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/armhf (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/armhf (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/i386 (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/i386 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/mips64el (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/mips64el (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/ppc64el (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/ppc64el (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/s390x (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/s390x (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/amd64 (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/amd64 (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/arm64 (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/arm64 (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/armel (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/armel (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/armhf (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/armhf (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/i386 (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/i386 (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/mips64el (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/mips64el (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/ppc64el (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/ppc64el (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/s390x (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/s390x (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-rime/amd64 (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/amd64 (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/arm64 (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/arm64 (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/armel (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/armel (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/armhf (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/armhf (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/i386 (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/i386 (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/mips64el (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/mips64el (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/ppc64el (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/ppc64el (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-rime/s390x (0.3.2+git20230425-1 to 0.3.2+git20230425-1)
  • Migration status for fcitx-rime/s390x (0.3.2+git20230425-1 to 0.3.2+git20230425-1): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/amd64 (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/amd64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/arm64 (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/arm64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/armel (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/armel (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/armhf (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/armhf (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/i386 (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/i386 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/mips64el (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/mips64el (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/ppc64el (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/ppc64el (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/s390x (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/s390x (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/amd64 (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/amd64 (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/arm64 (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/arm64 (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/armel (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/armel (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/armhf (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/armhf (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/i386 (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/i386 (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/mips64el (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/mips64el (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/ppc64el (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/ppc64el (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-sunpinyin/s390x (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/s390x (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/amd64 (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/amd64 (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/arm64 (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/arm64 (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/armel (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/armel (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/armhf (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/armhf (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/i386 (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/i386 (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/mips64el (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/mips64el (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/ppc64el (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/ppc64el (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx-ui-light/s390x (0.1.3-5 to 0.1.3-5)
  • Migration status for fcitx-ui-light/s390x (0.1.3-5 to 0.1.3-5): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/amd64 (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/amd64 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/arm64 (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/arm64 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/armel (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/armel (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/armhf (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/armhf (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/i386 (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/i386 (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/mips64el (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/mips64el (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/ppc64el (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/ppc64el (5.1.2-1 to 5.1.2-1): Will attempt migration (Any information below is purely informational)
• fcitx5-anthy/s390x (5.1.2-1 to 5.1.2-1)
  • Migration status for fcitx5-anthy/s390x (5.1.2-1 to 5.1.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-anthy/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-bamboo/amd64 (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/amd64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• fcitx5-bamboo/arm64 (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/arm64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• fcitx5-bamboo/armel (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/armel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• fcitx5-bamboo/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• fcitx5-bamboo/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• fcitx5-bamboo/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• fcitx5-bamboo/s390x (1.0.4-1 to 1.0.4-1)
  • Migration status for fcitx5-bamboo/s390x (1.0.4-1 to 1.0.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-bamboo/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-chewing/amd64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/amd64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/arm64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/arm64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/armel (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/armel (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/armhf (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/armhf (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/i386 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/i386 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/mips64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/mips64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/ppc64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/ppc64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-chewing/s390x (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-chewing/s390x (5.1.1-1 to 5.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-chewing/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-gtk/amd64 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/amd64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/arm64 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/arm64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/armel (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/armel (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/armhf (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/armhf (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/i386 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/i386 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/mips64el (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/mips64el (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/ppc64el (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/ppc64el (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-gtk/s390x (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-gtk/s390x (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/amd64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/amd64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/arm64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/arm64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/armel (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/armel (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/armhf (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/armhf (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/i386 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/i386 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/mips64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/mips64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/ppc64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/ppc64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-hangul/s390x (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-hangul/s390x (5.1.1-1 to 5.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-hangul/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-keyman/amd64 (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/amd64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-keyman/arm64 (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/arm64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-keyman/armel (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/armel (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-keyman/armhf (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/armhf (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-keyman/i386 (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/i386 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-keyman/mips64el (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/mips64el (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-keyman/ppc64el (1.0.7-1 to 1.0.7-1)
  • Migration status for fcitx5-keyman/ppc64el (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/amd64 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/amd64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/arm64 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/arm64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/armel (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/armel (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/armhf (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/armhf (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/i386 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/i386 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/mips64el (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/mips64el (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/ppc64el (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/ppc64el (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-kkc/s390x (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-kkc/s390x (5.1.0-1 to 5.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-kkc/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-libthai/amd64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/amd64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/arm64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/arm64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/armel (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/armel (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/armhf (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/armhf (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/i386 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/i386 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/mips64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/mips64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/ppc64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/ppc64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-libthai/s390x (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-libthai/s390x (5.1.1-1 to 5.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-libthai/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-lua/amd64 (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/amd64 (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/arm64 (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/arm64 (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/armel (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/armel (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/armhf (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/armhf (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/i386 (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/i386 (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/mips64el (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/mips64el (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/ppc64el (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/ppc64el (5.0.11-1 to 5.0.11-1): Will attempt migration (Any information below is purely informational)
• fcitx5-lua/s390x (5.0.11-1 to 5.0.11-1)
  • Migration status for fcitx5-lua/s390x (5.0.11-1 to 5.0.11-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-lua/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-m17n/amd64 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/amd64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/arm64 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/arm64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/armel (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/armel (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/armhf (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/armhf (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/i386 (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/i386 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/mips64el (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/mips64el (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/ppc64el (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/ppc64el (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• fcitx5-m17n/s390x (5.1.0-1 to 5.1.0-1)
  • Migration status for fcitx5-m17n/s390x (5.1.0-1 to 5.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-m17n/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-qt/amd64 (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/amd64 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/arm64 (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/arm64 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/armel (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/armel (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/armhf (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/armhf (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/i386 (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/i386 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/mips64el (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/mips64el (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/ppc64el (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/ppc64el (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/s390x (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-qt/s390x (5.1.3-1 to 5.1.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-qt/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-rime/amd64 (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/amd64 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/arm64 (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/arm64 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/armel (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/armel (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/armhf (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/armhf (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/i386 (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/i386 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/mips64el (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/mips64el (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/ppc64el (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/ppc64el (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• fcitx5-rime/s390x (5.1.3-1 to 5.1.3-1)
  • Migration status for fcitx5-rime/s390x (5.1.3-1 to 5.1.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-rime/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-sayura/amd64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/amd64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/arm64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/arm64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/armel (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/armel (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/armhf (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/armhf (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/i386 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/i386 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/mips64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/mips64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/ppc64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/ppc64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-sayura/s390x (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-sayura/s390x (5.1.1-1 to 5.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-sayura/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-skk/amd64 (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/amd64 (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/arm64 (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/arm64 (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/armel (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/armel (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/armhf (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/armhf (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/i386 (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/i386 (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/mips64el (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/mips64el (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/ppc64el (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/ppc64el (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• fcitx5-skk/s390x (5.1.0-2 to 5.1.0-2)
  • Migration status for fcitx5-skk/s390x (5.1.0-2 to 5.1.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-skk/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fcitx5-unikey/amd64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/amd64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/arm64 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/arm64 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/armel (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/armel (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/armhf (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/armhf (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/i386 (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/i386 (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/mips64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/mips64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/ppc64el (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/ppc64el (5.1.1-1 to 5.1.1-1): Will attempt migration (Any information below is purely informational)
• fcitx5-unikey/s390x (5.1.1-1 to 5.1.1-1)
  • Migration status for fcitx5-unikey/s390x (5.1.1-1 to 5.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fcitx5-unikey/s390x fcitx5 (not considered)
    • Invalidated by dependency
• fclib/amd64 (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/amd64 (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/arm64 (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/arm64 (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/armel (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/armel (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/armhf (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/armhf (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/i386 (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/i386 (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/mips64el (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/mips64el (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/ppc64el (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/ppc64el (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fclib/s390x (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/s390x (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fcml/amd64 (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/amd64 (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/arm64 (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/arm64 (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/armel (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/armel (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/armhf (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/armhf (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/i386 (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/i386 (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/mips64el (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/mips64el (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/ppc64el (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/ppc64el (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• fcml/s390x (1.2.2-2 to 1.2.2-2)
  • Migration status for fcml/s390x (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• feedbackd/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/amd64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/arm64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/armel (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/armhf (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/i386 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/mips64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/ppc64el (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• feedbackd/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for feedbackd/s390x (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• fenicsx-performance-tests/amd64 (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/amd64 (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/amd64 petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/amd64 fenics-dolfinx
• fenicsx-performance-tests/arm64 (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/arm64 (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/arm64 petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/arm64 fenics-dolfinx
• fenicsx-performance-tests/armel (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/armel (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/armel petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/armel fenics-dolfinx
• fenicsx-performance-tests/armhf (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/armhf (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/armhf petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/armhf fenics-dolfinx
• fenicsx-performance-tests/i386 (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/i386 (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/i386 petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/i386 fenics-dolfinx
• fenicsx-performance-tests/mips64el (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/mips64el (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/mips64el petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/mips64el fenics-dolfinx
• fenicsx-performance-tests/ppc64el (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/ppc64el (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/ppc64el petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/ppc64el fenics-dolfinx
• fenicsx-performance-tests/s390x (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1)
  • Migration status for fenicsx-performance-tests/s390x (0.7.0~git20231007.4ba90a6-1 to 0.7.0~git20231007.4ba90a6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fenicsx-performance-tests/s390x petsc (not considered)
    • Invalidated by dependency
    • Depends: fenicsx-performance-tests/s390x fenics-dolfinx
• ffcall/amd64 (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/amd64 (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/arm64 (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/arm64 (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/armel (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/armel (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/armhf (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/armhf (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/i386 (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/i386 (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/mips64el (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/mips64el (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/ppc64el (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/ppc64el (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffcall/s390x (2.4-2.1 to 2.4-2.1)
  • Migration status for ffcall/s390x (2.4-2.1 to 2.4-2.1): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/amd64 (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/amd64 (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/arm64 (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/arm64 (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/armel (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/armel (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/armhf (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/armhf (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/i386 (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/i386 (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/mips64el (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/mips64el (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/ppc64el (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/ppc64el (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/s390x (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2)
  • Migration status for ffmpegthumbnailer/s390x (2.2.2+git20220218+dfsg-2 to 2.2.2+git20220218+dfsg-2): Will attempt migration (Any information below is purely informational)
• fifechan/amd64 (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/amd64 (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/arm64 (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/arm64 (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/armel (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/armel (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/armhf (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/armhf (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/i386 (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/i386 (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/mips64el (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/mips64el (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/ppc64el (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/ppc64el (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• fifechan/s390x (0.1.5-3 to 0.1.5-3)
  • Migration status for fifechan/s390x (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• file/amd64 (1:5.45-2 to 1:5.45-2)
  • Migration status for file/amd64 (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/arm64 (1:5.45-2 to 1:5.45-2)
  • Migration status for file/arm64 (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/armel (1:5.45-2 to 1:5.45-2)
  • Migration status for file/armel (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/armhf (1:5.45-2 to 1:5.45-2)
  • Migration status for file/armhf (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/i386 (1:5.45-2 to 1:5.45-2)
  • Migration status for file/i386 (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/mips64el (1:5.45-2 to 1:5.45-2)
  • Migration status for file/mips64el (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/ppc64el (1:5.45-2 to 1:5.45-2)
  • Migration status for file/ppc64el (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• file/s390x (1:5.45-2 to 1:5.45-2)
  • Migration status for file/s390x (1:5.45-2 to 1:5.45-2): Will attempt migration (Any information below is purely informational)
• finalcut/amd64 (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/amd64 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/arm64 (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/arm64 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/armel (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/armel (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/armhf (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/armhf (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/i386 (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/i386 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/mips64el (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/mips64el (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/ppc64el (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/ppc64el (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• finalcut/s390x (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/s390x (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• firefox-esr_pu (115.6.0esr-1 to 115.6.0esr-1~deb12u1)
  • Migration status for firefox-esr_pu (115.6.0esr-1 to 115.6.0esr-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: firefox-esr is newer in the target suite (115.6.0esr-1 115.6.0esr-1~deb12u1)
• firmware-microbit-micropython/amd64 (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/amd64 (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/arm64 (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/arm64 (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/armel (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/armel (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/armhf (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/armhf (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/i386 (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/i386 (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/mips64el (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/mips64el (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/ppc64el (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/ppc64el (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• firmware-microbit-micropython/s390x (1.0.1-4 to 1.0.1-4)
  • Migration status for firmware-microbit-micropython/s390x (1.0.1-4 to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fish_pu (3.6.4-1 to 3.6.0-3.1+deb12u1)
  • Migration status for fish_pu (3.6.4-1 to 3.6.0-3.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: fish is newer in the target suite (3.6.4-1 3.6.0-3.1+deb12u1)
• flac/amd64 (1.4.3+ds-2 to 1.4.3+ds-2)
  • Migration status for flac/amd64 (1.4.3+ds-2 to 1.4.3+ds-2): Will attempt migration (Any information below is purely informational)
• flac/arm64 (1.4.3+ds-2 to 1.4.3+ds-2)
  • Migration status for flac/arm64 (1.4.3+ds-2 to 1.4.3+ds-2): Will attempt migration (Any information below is purely informational)
• flac/armhf (1.4.3+ds-2 to 1.4.3+ds-2)
  • Migration status for flac/armhf (1.4.3+ds-2 to 1.4.3+ds-2): Will attempt migration (Any information below is purely informational)
• flac/mips64el (1.4.3+ds-2 to 1.4.3+ds-2)
  • Migration status for flac/mips64el (1.4.3+ds-2 to 1.4.3+ds-2): Will attempt migration (Any information below is purely informational)
• flac/ppc64el (1.4.3+ds-2 to 1.4.3+ds-2)
  • Migration status for flac/ppc64el (1.4.3+ds-2 to 1.4.3+ds-2): Will attempt migration (Any information below is purely informational)
• flac/s390x (1.4.3+ds-2 to 1.4.3+ds-2)
  • Migration status for flac/s390x (1.4.3+ds-2 to 1.4.3+ds-2): Will attempt migration (Any information below is purely informational)
• flam3/amd64 (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/amd64 (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flam3/arm64 (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/arm64 (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flam3/armhf (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/armhf (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flam3/mips64el (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/mips64el (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flam3/ppc64el (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/ppc64el (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flam3/s390x (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/s390x (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flashrom/amd64 (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for flashrom/amd64 (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• flashrom/arm64 (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for flashrom/arm64 (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• flashrom/armhf (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for flashrom/armhf (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• flashrom/mips64el (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for flashrom/mips64el (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• flashrom/ppc64el (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for flashrom/ppc64el (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• flashrom/s390x (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for flashrom/s390x (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• flatbuffers/amd64 (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6)
  • Migration status for flatbuffers/amd64 (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6): Will attempt migration (Any information below is purely informational)
• flatbuffers/arm64 (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6)
  • Migration status for flatbuffers/arm64 (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6): Will attempt migration (Any information below is purely informational)
• flatbuffers/armhf (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6)
  • Migration status for flatbuffers/armhf (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6): Will attempt migration (Any information below is purely informational)
• flatbuffers/mips64el (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6)
  • Migration status for flatbuffers/mips64el (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6): Will attempt migration (Any information below is purely informational)
• flatbuffers/ppc64el (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6)
  • Migration status for flatbuffers/ppc64el (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6): Will attempt migration (Any information below is purely informational)
• flatbuffers/s390x (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6)
  • Migration status for flatbuffers/s390x (2.0.8+dfsg1-6 to 2.0.8+dfsg1-6): Will attempt migration (Any information below is purely informational)
• flatpak/amd64 (1.14.5-1 to 1.14.5-1)
  • Migration status for flatpak/amd64 (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• flatpak/arm64 (1.14.5-1 to 1.14.5-1)
  • Migration status for flatpak/arm64 (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• flatpak/armhf (1.14.5-1 to 1.14.5-1)
  • Migration status for flatpak/armhf (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• flatpak/mips64el (1.14.5-1 to 1.14.5-1)
  • Migration status for flatpak/mips64el (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• flatpak/ppc64el (1.14.5-1 to 1.14.5-1)
  • Migration status for flatpak/ppc64el (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• flatpak/s390x (1.14.5-1 to 1.14.5-1)
  • Migration status for flatpak/s390x (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• flatzebra/amd64 (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/amd64 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/arm64 (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/arm64 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/armel (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/armel (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/armhf (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/armhf (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/i386 (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/i386 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/mips64el (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/mips64el (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/ppc64el (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/ppc64el (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flatzebra/s390x (0.1.7-2 to 0.1.7-2)
  • Migration status for flatzebra/s390x (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• flex/amd64 (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/amd64 (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/arm64 (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/arm64 (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/armel (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/armel (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/armhf (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/armhf (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/i386 (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/i386 (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/mips64el (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/mips64el (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/ppc64el (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/ppc64el (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flex/s390x (2.6.4-8.2 to 2.6.4-8.2)
  • Migration status for flex/s390x (2.6.4-8.2 to 2.6.4-8.2): Will attempt migration (Any information below is purely informational)
• flite/amd64 (2.2-6 to 2.2-6)
  • Migration status for flite/amd64 (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/arm64 (2.2-6 to 2.2-6)
  • Migration status for flite/arm64 (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/armel (2.2-6 to 2.2-6)
  • Migration status for flite/armel (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/armhf (2.2-6 to 2.2-6)
  • Migration status for flite/armhf (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/i386 (2.2-6 to 2.2-6)
  • Migration status for flite/i386 (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/mips64el (2.2-6 to 2.2-6)
  • Migration status for flite/mips64el (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/ppc64el (2.2-6 to 2.2-6)
  • Migration status for flite/ppc64el (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• flite/s390x (2.2-6 to 2.2-6)
  • Migration status for flite/s390x (2.2-6 to 2.2-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/amd64 (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/amd64 (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/arm64 (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/arm64 (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/armel (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/armel (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/armhf (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/armhf (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/i386 (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/i386 (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/mips64el (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/mips64el (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/ppc64el (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/ppc64el (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fltk1.3/s390x (1.3.8-6 to 1.3.8-6)
  • Migration status for fltk1.3/s390x (1.3.8-6 to 1.3.8-6): Will attempt migration (Any information below is purely informational)
• fluidsynth/amd64 (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/amd64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/arm64 (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/arm64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/armel (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/armel (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/armhf (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/armhf (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/i386 (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/i386 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/mips64el (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/mips64el (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/ppc64el (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/ppc64el (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• fluidsynth/s390x (2.3.4-1 to 2.3.4-1)
  • Migration status for fluidsynth/s390x (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• flxmlrpc/amd64 (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/amd64 (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/arm64 (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/arm64 (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/armel (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/armel (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/armhf (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/armhf (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/i386 (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/i386 (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/mips64el (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/mips64el (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/ppc64el (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/ppc64el (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• flxmlrpc/s390x (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/s390x (0.1.4-6 to 0.1.4-6): Will attempt migration (Any information below is purely informational)
• foma/amd64 (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/amd64 (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/arm64 (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/arm64 (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/armel (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/armel (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/armhf (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/armhf (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/i386 (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/i386 (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/mips64el (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/mips64el (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/ppc64el (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/ppc64el (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• foma/s390x (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1)
  • Migration status for foma/s390x (1:0.10.0+s311-1.1 to 1:0.10.0+s311-1.1): Will attempt migration (Any information below is purely informational)
• font-manager/amd64 (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/amd64 (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/arm64 (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/arm64 (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/armel (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/armel (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/armhf (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/armhf (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/i386 (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/i386 (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/mips64el (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/mips64el (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/ppc64el (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/ppc64el (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• font-manager/s390x (0.8.8-3 to 0.8.8-3)
  • Migration status for font-manager/s390x (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• fontconfig/amd64 (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/amd64 (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/arm64 (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/arm64 (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/armel (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/armel (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/armhf (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/armhf (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/i386 (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/i386 (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/mips64el (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/mips64el (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/ppc64el (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/ppc64el (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• fontconfig/s390x (2.14.2-6 to 2.14.2-6)
  • Migration status for fontconfig/s390x (2.14.2-6 to 2.14.2-6): Will attempt migration (Any information below is purely informational)
• foonathan-memory/amd64 (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/amd64 (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/arm64 (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/arm64 (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/armel (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/armel (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/armhf (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/armhf (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/i386 (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/i386 (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/mips64el (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/mips64el (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/ppc64el (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/ppc64el (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• foonathan-memory/s390x (0.7.3-2 to 0.7.3-2)
  • Migration status for foonathan-memory/s390x (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• forge/amd64 (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/amd64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/arm64 (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/arm64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/armel (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/armel (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/armhf (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/armhf (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/i386 (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/i386 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/mips64el (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/mips64el (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/ppc64el (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/ppc64el (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• forge/s390x (1.0.1-3 to 1.0.1-3)
  • Migration status for forge/s390x (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• fosfat/amd64 (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/amd64 (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/arm64 (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/arm64 (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/armel (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/armel (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/armhf (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/armhf (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/i386 (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/i386 (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/mips64el (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/mips64el (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/ppc64el (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/ppc64el (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fosfat/s390x (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5)
  • Migration status for fosfat/s390x (0.4.0-13-ged091bb-5 to 0.4.0-13-ged091bb-5): Will attempt migration (Any information below is purely informational)
• fparserc++/amd64 (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/amd64 (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/arm64 (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/arm64 (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/armel (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/armel (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/armhf (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/armhf (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/i386 (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/i386 (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/mips64el (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/mips64el (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/ppc64el (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/ppc64el (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fparserc++/s390x (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/s390x (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fpzip/amd64 (1.3.0-3 to 1.3.0-3)
  • Migration status for fpzip/amd64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• fpzip/arm64 (1.3.0-3 to 1.3.0-3)
  • Migration status for fpzip/arm64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• fpzip/mips64el (1.3.0-3 to 1.3.0-3)
  • Migration status for fpzip/mips64el (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• fpzip/ppc64el (1.3.0-3 to 1.3.0-3)
  • Migration status for fpzip/ppc64el (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• fpzip/s390x (1.3.0-3 to 1.3.0-3)
  • Migration status for fpzip/s390x (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• frame/amd64 (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/amd64 (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/arm64 (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/arm64 (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/armel (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/armel (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/armhf (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/armhf (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/i386 (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/i386 (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/mips64el (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/mips64el (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/ppc64el (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/ppc64el (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frame/s390x (2.5.0-5 to 2.5.0-5)
  • Migration status for frame/s390x (2.5.0-5 to 2.5.0-5): Will attempt migration (Any information below is purely informational)
• frameworkintegration/amd64 (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/amd64 (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/arm64 (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/arm64 (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/armel (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/armel (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/armhf (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/armhf (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/i386 (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/i386 (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/mips64el (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/mips64el (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/ppc64el (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/ppc64el (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• frameworkintegration/s390x (5.107.0-2 to 5.107.0-2)
  • Migration status for frameworkintegration/s390x (5.107.0-2 to 5.107.0-2): Will attempt migration (Any information below is purely informational)
• freealut/amd64 (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/amd64 (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/arm64 (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/arm64 (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/armel (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/armel (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/armhf (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/armhf (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/i386 (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/i386 (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/mips64el (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/mips64el (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/ppc64el (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/ppc64el (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freealut/s390x (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/s390x (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freeglut/amd64 (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/amd64 (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/arm64 (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/arm64 (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/armel (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/armel (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/armhf (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/armhf (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/i386 (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/i386 (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/mips64el (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/mips64el (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/ppc64el (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/ppc64el (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeglut/s390x (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/s390x (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freeimage_pu (3.18.0+ds2-10 to 3.18.0+ds2-9+deb12u1)
  • Migration status for freeimage_pu (3.18.0+ds2-10 to 3.18.0+ds2-9+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: freeimage is newer in the target suite (3.18.0+ds2-10 3.18.0+ds2-9+deb12u1)
• freerdp2/amd64 (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/amd64 (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/arm64 (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/arm64 (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/armel (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/armel (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/armhf (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/armhf (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/i386 (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/i386 (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/mips64el (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/mips64el (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/ppc64el (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/ppc64el (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freerdp2/s390x (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1)
  • Migration status for freerdp2/s390x (2.11.2+dfsg1-1 to 2.11.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
• freetds/amd64 (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/amd64 (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetds/arm64 (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/arm64 (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetds/armel (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/armel (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetds/armhf (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/armhf (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetds/mips64el (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/mips64el (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetds/ppc64el (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/ppc64el (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetds/s390x (1.3.17+ds-2 to 1.3.17+ds-2)
  • Migration status for freetds/s390x (1.3.17+ds-2 to 1.3.17+ds-2): Will attempt migration (Any information below is purely informational)
• freetype/amd64 (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/amd64 (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/arm64 (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/arm64 (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/armel (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/armel (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/armhf (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/armhf (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/i386 (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/i386 (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/mips64el (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/mips64el (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/ppc64el (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/ppc64el (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype/s390x (2.13.2+dfsg-1 to 2.13.2+dfsg-1)
  • Migration status for freetype/s390x (2.13.2+dfsg-1 to 2.13.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetype_pu (2.13.2+dfsg-1 to 2.12.1+dfsg-5+deb12u2)
  • Migration status for freetype_pu (2.13.2+dfsg-1 to 2.12.1+dfsg-5+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: freetype is newer in the target suite (2.13.2+dfsg-1 2.12.1+dfsg-5+deb12u2)
• freexl/amd64 (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/amd64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• freexl/arm64 (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/arm64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• freexl/armhf (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/armhf (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• freexl/i386 (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/i386 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• freexl/mips64el (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/mips64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• freexl/ppc64el (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/ppc64el (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• freexl/s390x (2.0.0-1 to 2.0.0-1)
  • Migration status for freexl/s390x (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• fribidi/amd64 (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/amd64 (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/arm64 (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/arm64 (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/armel (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/armel (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/armhf (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/armhf (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/i386 (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/i386 (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/mips64el (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/mips64el (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/ppc64el (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/ppc64el (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fribidi/s390x (1.0.13-3 to 1.0.13-3)
  • Migration status for fribidi/s390x (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• fstrm/amd64 (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/amd64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/arm64 (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/arm64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/armel (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/armel (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/armhf (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/armhf (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/i386 (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/i386 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/mips64el (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/mips64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/ppc64el (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/ppc64el (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fstrm/s390x (0.6.1-1 to 0.6.1-1)
  • Migration status for fstrm/s390x (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/amd64 (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/amd64 (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/arm64 (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/arm64 (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/armel (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/armel (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/armhf (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/armhf (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/i386 (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/i386 (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/mips64el (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/mips64el (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/ppc64el (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/ppc64el (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• fsverity-utils/s390x (1.5-1.1 to 1.5-1.1)
  • Migration status for fsverity-utils/s390x (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• ftgl/amd64 (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/amd64 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/arm64 (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/arm64 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/armel (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/armel (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/armhf (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/armhf (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/i386 (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/i386 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/mips64el (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/mips64el (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/ppc64el (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/ppc64el (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftgl/s390x (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/s390x (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftplib/amd64 (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/amd64 (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/arm64 (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/arm64 (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/armel (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/armel (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/armhf (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/armhf (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/i386 (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/i386 (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/mips64el (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/mips64el (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/ppc64el (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/ppc64el (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• ftplib/s390x (4.0-1-4 to 4.0-1-4)
  • Migration status for ftplib/s390x (4.0-1-4 to 4.0-1-4): Will attempt migration (Any information below is purely informational)
• funtools/amd64 (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/amd64 (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/arm64 (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/arm64 (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/armel (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/armel (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/armhf (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/armhf (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/i386 (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/i386 (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/mips64el (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/mips64el (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/ppc64el (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/ppc64el (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• funtools/s390x (1.4.8-1 to 1.4.8-1)
  • Migration status for funtools/s390x (1.4.8-1 to 1.4.8-1): Will attempt migration (Any information below is purely informational)
• fuse/amd64 (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/amd64 (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/arm64 (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/arm64 (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/armel (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/armel (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/armhf (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/armhf (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/i386 (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/i386 (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/mips64el (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/mips64el (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/ppc64el (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/ppc64el (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• fuse/s390x (2.9.9-8 to 2.9.9-8)
  • Migration status for fuse/s390x (2.9.9-8 to 2.9.9-8): Will attempt migration (Any information below is purely informational)
• getdp/amd64 (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/amd64 (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/amd64 slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/amd64 petsc
• getdp/arm64 (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/arm64 (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/arm64 slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/arm64 petsc
• getdp/armel (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/armel (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/armel slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/armel petsc
• getdp/armhf (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/armhf (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/armhf slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/armhf petsc
• getdp/i386 (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/i386 (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/i386 slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/i386 petsc
• getdp/mips64el (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/mips64el (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/mips64el slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/mips64el petsc
• getdp/ppc64el (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/ppc64el (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/ppc64el slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/ppc64el petsc
• getdp/s390x (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1)
  • Migration status for getdp/s390x (3.2.0+dfsg1-1.1 to 3.2.0+dfsg1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: getdp/s390x slepc (not considered)
    • Invalidated by dependency
    • Depends: getdp/s390x petsc
• ghostscript_pu (10.02.1~dfsg-1 to 10.0.0~dfsg-11+deb12u3)
  • Migration status for ghostscript_pu (10.02.1~dfsg-1 to 10.0.0~dfsg-11+deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ghostscript is newer in the target suite (10.02.1~dfsg-1 10.0.0~dfsg-11+deb12u3)
• gitit/amd64 (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/amd64 (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/amd64 haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/arm64 (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/arm64 (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/arm64 haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/armel (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/armel (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/armel haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/armhf (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/armhf (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/armhf haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/i386 (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/i386 (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/i386 haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/mips64el (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/mips64el (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/mips64el haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/ppc64el (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/ppc64el (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/ppc64el haskell-pandoc (not considered)
    • Invalidated by dependency
• gitit/s390x (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1)
  • Migration status for gitit/s390x (0.15.1.1+dfsg-1 to 0.15.1.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gitit/s390x haskell-pandoc (not considered)
    • Invalidated by dependency
• gqrx-sdr/amd64 (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/amd64 (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/amd64 gnuradio
• gqrx-sdr/arm64 (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/arm64 (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/arm64 gnuradio
• gqrx-sdr/armel (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/armel (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/armel gnuradio
• gqrx-sdr/armhf (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/armhf (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/armhf gnuradio
• gqrx-sdr/i386 (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/i386 (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/i386 gnuradio
• gqrx-sdr/mips64el (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/mips64el (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/mips64el gnuradio
• gqrx-sdr/ppc64el (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/ppc64el (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/ppc64el gnuradio
• gqrx-sdr/s390x (2.17.3-1 to 2.17.3-1)
  • Migration status for gqrx-sdr/s390x (2.17.3-1 to 2.17.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gqrx-sdr/s390x gnuradio
• gr-air-modes/amd64 (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/amd64 (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/amd64 gnuradio
• gr-air-modes/arm64 (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/arm64 (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/arm64 gnuradio
• gr-air-modes/armel (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/armel (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/armel gnuradio
• gr-air-modes/armhf (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/armhf (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/armhf gnuradio
• gr-air-modes/i386 (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/i386 (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/i386 gnuradio
• gr-air-modes/mips64el (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/mips64el (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/mips64el gnuradio
• gr-air-modes/ppc64el (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/ppc64el (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/ppc64el gnuradio
• gr-air-modes/s390x (0.0.20210211-3 to 0.0.20210211-3)
  • Migration status for gr-air-modes/s390x (0.0.20210211-3 to 0.0.20210211-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-air-modes/s390x gnuradio
• gr-fosphor/amd64 (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/amd64 (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/amd64 gnuradio
• gr-fosphor/arm64 (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/arm64 (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/arm64 gnuradio
• gr-fosphor/armel (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/armel (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/armel gnuradio
• gr-fosphor/armhf (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/armhf (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/armhf gnuradio
• gr-fosphor/i386 (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/i386 (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/i386 gnuradio
• gr-fosphor/mips64el (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/mips64el (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/mips64el gnuradio
• gr-fosphor/ppc64el (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/ppc64el (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/ppc64el gnuradio
• gr-fosphor/s390x (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1)
  • Migration status for gr-fosphor/s390x (3.9~0.974ab2f-1 to 3.9~0.974ab2f-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-fosphor/s390x gnuradio
• gr-funcube/amd64 (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/amd64 (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/amd64 gnuradio
• gr-funcube/arm64 (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/arm64 (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/arm64 gnuradio
• gr-funcube/armel (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/armel (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/armel gnuradio
• gr-funcube/armhf (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/armhf (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/armhf gnuradio
• gr-funcube/i386 (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/i386 (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/i386 gnuradio
• gr-funcube/mips64el (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/mips64el (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/mips64el gnuradio
• gr-funcube/ppc64el (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/ppc64el (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/ppc64el gnuradio
• gr-funcube/s390x (3.10.0~rc3-3 to 3.10.0~rc3-3)
  • Migration status for gr-funcube/s390x (3.10.0~rc3-3 to 3.10.0~rc3-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-funcube/s390x gnuradio
• gr-gsm/amd64 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/amd64 (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/amd64 gnuradio
• gr-gsm/arm64 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/arm64 (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/arm64 gnuradio
• gr-gsm/armel (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/armel (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/armel gnuradio
• gr-gsm/armhf (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/armhf (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/armhf gnuradio
• gr-gsm/i386 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/i386 (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/i386 gnuradio
• gr-gsm/mips64el (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/mips64el (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/mips64el gnuradio
• gr-gsm/ppc64el (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/ppc64el (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/ppc64el gnuradio
• gr-gsm/s390x (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/s390x (1.0.0~20220727-1 to 1.0.0~20220727-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-gsm/s390x gnuradio
• gr-hpsdr/amd64 (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/amd64 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/amd64 gnuradio
• gr-hpsdr/arm64 (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/arm64 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/arm64 gnuradio
• gr-hpsdr/armel (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/armel (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/armel gnuradio
• gr-hpsdr/armhf (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/armhf (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/armhf gnuradio
• gr-hpsdr/i386 (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/i386 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/i386 gnuradio
• gr-hpsdr/mips64el (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/mips64el (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/mips64el gnuradio
• gr-hpsdr/ppc64el (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/ppc64el (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/ppc64el gnuradio
• gr-hpsdr/s390x (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/s390x (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-hpsdr/s390x gnuradio
• gr-iqbal/amd64 (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/amd64 (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/amd64 gnuradio
• gr-iqbal/arm64 (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/arm64 (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/arm64 gnuradio
• gr-iqbal/armel (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/armel (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/armel gnuradio
• gr-iqbal/armhf (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/armhf (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/armhf gnuradio
• gr-iqbal/i386 (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/i386 (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/i386 gnuradio
• gr-iqbal/mips64el (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/mips64el (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/mips64el gnuradio
• gr-iqbal/ppc64el (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/ppc64el (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/ppc64el gnuradio
• gr-iqbal/s390x (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/s390x (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-iqbal/s390x gnuradio
• gr-limesdr/amd64 (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/amd64 (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/amd64 gnuradio
• gr-limesdr/arm64 (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/arm64 (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/arm64 gnuradio
• gr-limesdr/armel (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/armel (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/armel gnuradio
• gr-limesdr/armhf (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/armhf (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/armhf gnuradio
• gr-limesdr/i386 (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/i386 (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/i386 gnuradio
• gr-limesdr/mips64el (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/mips64el (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/mips64el gnuradio
• gr-limesdr/ppc64el (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/ppc64el (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/ppc64el gnuradio
• gr-limesdr/s390x (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/s390x (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
    • Depends: gr-limesdr/s390x gnuradio
• gr-osmosdr/amd64 (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/amd64 (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/amd64 gnuradio
• gr-osmosdr/arm64 (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/arm64 (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/arm64 gnuradio
• gr-osmosdr/armel (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/armel (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/armel gnuradio
• gr-osmosdr/armhf (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/armhf (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/armhf gnuradio
• gr-osmosdr/i386 (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/i386 (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/i386 gnuradio
• gr-osmosdr/mips64el (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/mips64el (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/mips64el gnuradio
• gr-osmosdr/ppc64el (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/ppc64el (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/ppc64el gnuradio
• gr-osmosdr/s390x (0.2.5-2 to 0.2.5-2)
  • Migration status for gr-osmosdr/s390x (0.2.5-2 to 0.2.5-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-osmosdr/s390x gnuradio
• gr-radar/amd64 (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/amd64 (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/amd64 gnuradio
• gr-radar/arm64 (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/arm64 (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/arm64 gnuradio
• gr-radar/armel (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/armel (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/armel gnuradio
• gr-radar/armhf (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/armhf (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/armhf gnuradio
• gr-radar/i386 (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/i386 (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/i386 gnuradio
• gr-radar/mips64el (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/mips64el (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/mips64el gnuradio
• gr-radar/ppc64el (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/ppc64el (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/ppc64el gnuradio
• gr-radar/s390x (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/s390x (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-radar/s390x gnuradio
• gr-rds/amd64 (3.10-1 to 3.10-1)
  • Migration status for gr-rds/amd64 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/amd64 gnuradio
• gr-rds/arm64 (3.10-1 to 3.10-1)
  • Migration status for gr-rds/arm64 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/arm64 gnuradio
• gr-rds/armel (3.10-1 to 3.10-1)
  • Migration status for gr-rds/armel (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/armel gnuradio
• gr-rds/armhf (3.10-1 to 3.10-1)
  • Migration status for gr-rds/armhf (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/armhf gnuradio
• gr-rds/i386 (3.10-1 to 3.10-1)
  • Migration status for gr-rds/i386 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/i386 gnuradio
• gr-rds/mips64el (3.10-1 to 3.10-1)
  • Migration status for gr-rds/mips64el (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/mips64el gnuradio
• gr-rds/ppc64el (3.10-1 to 3.10-1)
  • Migration status for gr-rds/ppc64el (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/ppc64el gnuradio
• gr-rds/s390x (3.10-1 to 3.10-1)
  • Migration status for gr-rds/s390x (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: gr-rds/s390x gnuradio
• gr-satellites/amd64 (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/amd64 (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/amd64 gnuradio
• gr-satellites/arm64 (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/arm64 (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/arm64 gnuradio
• gr-satellites/armel (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/armel (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/armel gnuradio
• gr-satellites/armhf (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/armhf (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/armhf gnuradio
• gr-satellites/i386 (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/i386 (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/i386 gnuradio
• gr-satellites/mips64el (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/mips64el (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/mips64el gnuradio
• gr-satellites/ppc64el (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/ppc64el (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/ppc64el gnuradio
• gr-satellites/s390x (4.4.0-2 to 4.4.0-2)
  • Migration status for gr-satellites/s390x (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: gr-satellites/s390x gnuradio
• gst-plugins-bad1.0_pu (1.22.8-1 to 1.22.0-4+deb12u4)
  • Migration status for gst-plugins-bad1.0_pu (1.22.8-1 to 1.22.0-4+deb12u4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: gst-plugins-bad1.0 is newer in the target suite (1.22.8-1 1.22.0-4+deb12u4)
• haproxy_pu (2.9.1-1 to 2.6.12-1+deb12u1)
  • Migration status for haproxy_pu (2.9.1-1 to 2.6.12-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: haproxy is newer in the target suite (2.9.1-1 2.6.12-1+deb12u1)
• harfbuzz/amd64 (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/amd64 (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/arm64 (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/arm64 (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/armel (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/armel (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/armhf (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/armhf (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/i386 (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/i386 (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/mips64el (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/mips64el (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/ppc64el (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/ppc64el (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• harfbuzz/s390x (8.0.1-1 to 8.0.1-1)
  • Migration status for harfbuzz/s390x (8.0.1-1 to 8.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-diagrams/amd64 (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/amd64 (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/arm64 (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/arm64 (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/armel (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/armel (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/armhf (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/armhf (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/i386 (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/i386 (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/mips64el (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/mips64el (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/ppc64el (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/ppc64el (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-diagrams/s390x (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-diagrams/s390x (1.4.0.1-1 to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-hakyll/amd64 (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/amd64 (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/amd64 haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/arm64 (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/arm64 (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/arm64 haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/armel (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/armel (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/armel haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/armhf (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/armhf (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/armhf haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/i386 (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/i386 (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/i386 haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/mips64el (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/mips64el (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/mips64el haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/ppc64el (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/ppc64el (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/ppc64el haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-hakyll/s390x (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/s390x (4.16.2.0-2 to 4.16.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-hakyll/s390x haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/amd64 (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/amd64 (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/amd64 haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/arm64 (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/arm64 (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/arm64 haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/armel (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/armel (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/armel haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/armhf (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/armhf (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/armhf haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/i386 (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/i386 (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/i386 haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/mips64el (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/mips64el (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/mips64el haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/ppc64el (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/ppc64el (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/ppc64el haskell-pandoc (not considered)
    • Invalidated by dependency
• haskell-pandoc-server/s390x (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/s390x (0.1.0.2-3 to 0.1.0.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: haskell-pandoc-server/s390x haskell-pandoc (not considered)
    • Invalidated by dependency
• isl/amd64 (0.26-3 to 0.26-3)
  • Migration status for isl/amd64 (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/arm64 (0.26-3 to 0.26-3)
  • Migration status for isl/arm64 (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/armel (0.26-3 to 0.26-3)
  • Migration status for isl/armel (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/armhf (0.26-3 to 0.26-3)
  • Migration status for isl/armhf (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/i386 (0.26-3 to 0.26-3)
  • Migration status for isl/i386 (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/mips64el (0.26-3 to 0.26-3)
  • Migration status for isl/mips64el (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/ppc64el (0.26-3 to 0.26-3)
  • Migration status for isl/ppc64el (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• isl/s390x (0.26-3 to 0.26-3)
  • Migration status for isl/s390x (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• jansson/amd64 (2.14-2 to 2.14-2)
  • Migration status for jansson/amd64 (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/arm64 (2.14-2 to 2.14-2)
  • Migration status for jansson/arm64 (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/armel (2.14-2 to 2.14-2)
  • Migration status for jansson/armel (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/armhf (2.14-2 to 2.14-2)
  • Migration status for jansson/armhf (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/i386 (2.14-2 to 2.14-2)
  • Migration status for jansson/i386 (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/mips64el (2.14-2 to 2.14-2)
  • Migration status for jansson/mips64el (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/ppc64el (2.14-2 to 2.14-2)
  • Migration status for jansson/ppc64el (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jansson/s390x (2.14-2 to 2.14-2)
  • Migration status for jansson/s390x (2.14-2 to 2.14-2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/amd64 (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/amd64 (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/arm64 (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/arm64 (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/armel (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/armel (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/armhf (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/armhf (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/i386 (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/i386 (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/mips64el (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/mips64el (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/ppc64el (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/ppc64el (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• jpeg-xl/s390x (0.7.0-10.2 to 0.7.0-10.2)
  • Migration status for jpeg-xl/s390x (0.7.0-10.2 to 0.7.0-10.2): Will attempt migration (Any information below is purely informational)
• keyutils/amd64 (1.6.3-2 to 1.6.3-2)
  • Migration status for keyutils/amd64 (1.6.3-2 to 1.6.3-2): Will attempt migration (Any information below is purely informational)
• keyutils/armhf (1.6.3-2 to 1.6.3-2)
  • Migration status for keyutils/armhf (1.6.3-2 to 1.6.3-2): Will attempt migration (Any information below is purely informational)
• keyutils/i386 (1.6.3-2 to 1.6.3-2)
  • Migration status for keyutils/i386 (1.6.3-2 to 1.6.3-2): Will attempt migration (Any information below is purely informational)
• keyutils/mips64el (1.6.3-2 to 1.6.3-2)
  • Migration status for keyutils/mips64el (1.6.3-2 to 1.6.3-2): Will attempt migration (Any information below is purely informational)
• keyutils/ppc64el (1.6.3-2 to 1.6.3-2)
  • Migration status for keyutils/ppc64el (1.6.3-2 to 1.6.3-2): Will attempt migration (Any information below is purely informational)
• keyutils/s390x (1.6.3-2 to 1.6.3-2)
  • Migration status for keyutils/s390x (1.6.3-2 to 1.6.3-2): Will attempt migration (Any information below is purely informational)
• lame/amd64 (3.100-6 to 3.100-6)
  • Migration status for lame/amd64 (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/arm64 (3.100-6 to 3.100-6)
  • Migration status for lame/arm64 (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/armel (3.100-6 to 3.100-6)
  • Migration status for lame/armel (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/armhf (3.100-6 to 3.100-6)
  • Migration status for lame/armhf (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/i386 (3.100-6 to 3.100-6)
  • Migration status for lame/i386 (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/mips64el (3.100-6 to 3.100-6)
  • Migration status for lame/mips64el (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/ppc64el (3.100-6 to 3.100-6)
  • Migration status for lame/ppc64el (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• lame/s390x (3.100-6 to 3.100-6)
  • Migration status for lame/s390x (3.100-6 to 3.100-6): Will attempt migration (Any information below is purely informational)
• libcap2/amd64 (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/amd64 (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/arm64 (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/arm64 (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/armel (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/armel (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/armhf (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/armhf (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/i386 (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/i386 (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/mips64el (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/mips64el (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/ppc64el (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/ppc64el (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libcap2/s390x (1:2.66-4 to 1:2.66-4)
  • Migration status for libcap2/s390x (1:2.66-4 to 1:2.66-4): Will attempt migration (Any information below is purely informational)
• libdatetime-timezone-perl_pu (1:2.60-2+2023d to 1:2.60-1+2023d)
  • Migration status for libdatetime-timezone-perl_pu (1:2.60-2+2023d to 1:2.60-1+2023d): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libdatetime-timezone-perl is newer in the target suite (1:2.60-2+2023d 1:2.60-1+2023d)
• libepoxy/amd64 (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/amd64 (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/arm64 (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/arm64 (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/armel (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/armel (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/armhf (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/armhf (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/i386 (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/i386 (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/mips64el (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/mips64el (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/ppc64el (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/ppc64el (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libepoxy/s390x (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/s390x (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libfirefox-marionette-perl_pu (1.49-1 to 1.35-1+deb12u1)
  • Migration status for libfirefox-marionette-perl_pu (1.49-1 to 1.35-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libfirefox-marionette-perl is newer in the target suite (1.49-1 1.35-1+deb12u1)
• libfontenc/amd64 (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/amd64 (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/arm64 (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/arm64 (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/armel (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/armel (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/armhf (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/armhf (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/i386 (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/i386 (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/mips64el (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/mips64el (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/ppc64el (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/ppc64el (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libfontenc/s390x (1:1.1.4-1 to 1:1.1.4-1)
  • Migration status for libfontenc/s390x (1:1.1.4-1 to 1:1.1.4-1): Will attempt migration (Any information below is purely informational)
• libhdate/amd64 (1.6.02-2.1 to 1.6.02-2.1)
  • Migration status for libhdate/amd64 (1.6.02-2.1 to 1.6.02-2.1): Will attempt migration (Any information below is purely informational)
• libhdate/i386 (1.6.02-2.1 to 1.6.02-2.1)
  • Migration status for libhdate/i386 (1.6.02-2.1 to 1.6.02-2.1): Will attempt migration (Any information below is purely informational)
• libhdate/ppc64el (1.6.02-2.1 to 1.6.02-2.1)
  • Migration status for libhdate/ppc64el (1.6.02-2.1 to 1.6.02-2.1): Will attempt migration (Any information below is purely informational)
• libhdate/s390x (1.6.02-2.1 to 1.6.02-2.1)
  • Migration status for libhdate/s390x (1.6.02-2.1 to 1.6.02-2.1): Will attempt migration (Any information below is purely informational)
• libidn2/amd64 (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/amd64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/arm64 (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/arm64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/armel (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/armel (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/armhf (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/armhf (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/i386 (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/i386 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/mips64el (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/mips64el (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/ppc64el (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/ppc64el (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libidn2/s390x (2.3.4-1 to 2.3.4-1)
  • Migration status for libidn2/s390x (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/amd64 (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/amd64 (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/arm64 (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/arm64 (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/armel (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/armel (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/armhf (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/armhf (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/i386 (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/i386 (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/mips64el (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/mips64el (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/ppc64el (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/ppc64el (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjpeg-turbo/s390x (1:2.1.5-2 to 1:2.1.5-2)
  • Migration status for libjpeg-turbo/s390x (1:2.1.5-2 to 1:2.1.5-2): Will attempt migration (Any information below is purely informational)
• libjsoncpp/amd64 (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/amd64 (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/arm64 (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/arm64 (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/armel (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/armel (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/armhf (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/armhf (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/i386 (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/i386 (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/mips64el (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/mips64el (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/ppc64el (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/ppc64el (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libjsoncpp/s390x (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/s390x (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• liboggz/amd64 (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/amd64 (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/arm64 (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/arm64 (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/armel (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/armel (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/armhf (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/armhf (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/i386 (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/i386 (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/mips64el (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/mips64el (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/ppc64el (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/ppc64el (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• liboggz/s390x (1.1.1-8 to 1.1.1-8)
  • Migration status for liboggz/s390x (1.1.1-8 to 1.1.1-8): Will attempt migration (Any information below is purely informational)
• libpipeline/amd64 (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/amd64 (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/arm64 (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/arm64 (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/armel (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/armel (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/armhf (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/armhf (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/i386 (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/i386 (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/mips64el (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/mips64el (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/ppc64el (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/ppc64el (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libpipeline/s390x (1.5.7-1 to 1.5.7-1)
  • Migration status for libpipeline/s390x (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• libproxy/amd64 (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/amd64 (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/arm64 (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/arm64 (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/armel (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/armel (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/armhf (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/armhf (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/i386 (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/i386 (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/mips64el (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/mips64el (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/ppc64el (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/ppc64el (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libproxy/s390x (0.4.18-1.2 to 0.4.18-1.2)
  • Migration status for libproxy/s390x (0.4.18-1.2 to 0.4.18-1.2): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/amd64 (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/amd64 (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/arm64 (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/arm64 (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/armel (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/armel (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/armhf (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/armhf (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/i386 (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/i386 (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/mips64el (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/mips64el (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/ppc64el (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/ppc64el (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/s390x (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/s390x (0.18+ds-1 to 0.18+ds-1): Will attempt migration (Any information below is purely informational)
• libreoffice_pu (4:7.6.4~rc1-1 to 4:7.4.7-1+deb12u1)
  • Migration status for libreoffice_pu (4:7.6.4~rc1-1 to 4:7.4.7-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libreoffice is newer in the target suite (4:7.6.4~rc1-1 4:7.4.7-1+deb12u1)
• libselinux/amd64 (3.5-1 to 3.5-1)
  • Migration status for libselinux/amd64 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/arm64 (3.5-1 to 3.5-1)
  • Migration status for libselinux/arm64 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/armel (3.5-1 to 3.5-1)
  • Migration status for libselinux/armel (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/armhf (3.5-1 to 3.5-1)
  • Migration status for libselinux/armhf (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/i386 (3.5-1 to 3.5-1)
  • Migration status for libselinux/i386 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/mips64el (3.5-1 to 3.5-1)
  • Migration status for libselinux/mips64el (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/ppc64el (3.5-1 to 3.5-1)
  • Migration status for libselinux/ppc64el (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libselinux/s390x (3.5-1 to 3.5-1)
  • Migration status for libselinux/s390x (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/amd64 (3.5-1 to 3.5-1)
  • Migration status for libsemanage/amd64 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/arm64 (3.5-1 to 3.5-1)
  • Migration status for libsemanage/arm64 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/armel (3.5-1 to 3.5-1)
  • Migration status for libsemanage/armel (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/armhf (3.5-1 to 3.5-1)
  • Migration status for libsemanage/armhf (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/i386 (3.5-1 to 3.5-1)
  • Migration status for libsemanage/i386 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/mips64el (3.5-1 to 3.5-1)
  • Migration status for libsemanage/mips64el (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/ppc64el (3.5-1 to 3.5-1)
  • Migration status for libsemanage/ppc64el (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libsemanage/s390x (3.5-1 to 3.5-1)
  • Migration status for libsemanage/s390x (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• libspreadsheet-parseexcel-perl_pu (0.6600-1 to 0.6500-4~deb12u1)
  • Migration status for libspreadsheet-parseexcel-perl_pu (0.6600-1 to 0.6500-4~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libspreadsheet-parseexcel-perl is newer in the target suite (0.6600-1 0.6500-4~deb12u1)
• libssh_pu (0.10.6-2 to 0.10.6-0+deb12u1)
  • Migration status for libssh_pu (0.10.6-2 to 0.10.6-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libssh is newer in the target suite (0.10.6-2 0.10.6-0+deb12u1)
• libtasn1-6/amd64 (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/amd64 (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/arm64 (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/arm64 (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/armel (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/armel (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/armhf (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/armhf (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/i386 (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/i386 (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/mips64el (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/mips64el (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/ppc64el (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/ppc64el (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtasn1-6/s390x (4.19.0-3 to 4.19.0-3)
  • Migration status for libtasn1-6/s390x (4.19.0-3 to 4.19.0-3): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/amd64 (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/amd64 (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/arm64 (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/arm64 (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/armel (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/armel (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/armhf (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/armhf (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/i386 (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/i386 (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/mips64el (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/mips64el (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/ppc64el (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/ppc64el (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
• libtext-charwidth-perl/s390x (0.04-11 to 0.04-11)
  • Migration status for libtext-charwidth-perl/s390x (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
    • Depends: libtext-charwidth-perl/s390x perl/s390x
• libtext-iconv-perl/amd64 (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/amd64 (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/arm64 (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/arm64 (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/armel (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/armel (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/armhf (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/armhf (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/i386 (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/i386 (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/mips64el (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/mips64el (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/ppc64el (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/ppc64el (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
• libtext-iconv-perl/s390x (1.7-8 to 1.7-8)
  • Migration status for libtext-iconv-perl/s390x (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
    • Depends: libtext-iconv-perl/s390x perl/s390x
• libxml2/amd64 (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/amd64 (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/arm64 (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/arm64 (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/armel (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/armel (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/armhf (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/armhf (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/i386 (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/i386 (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/mips64el (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/mips64el (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/ppc64el (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/ppc64el (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• libxml2/s390x (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3)
  • Migration status for libxml2/s390x (2.9.14+dfsg-1.3 to 2.9.14+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• linux-signed-amd64_pu (6.5.13+1 to 6.1.69+1)
  • Migration status for linux-signed-amd64_pu (6.5.13+1 to 6.1.69+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-amd64 is newer in the target suite (6.5.13+1 6.1.69+1)
• linux-signed-arm64_pu (6.5.13+1 to 6.1.69+1)
  • Migration status for linux-signed-arm64_pu (6.5.13+1 to 6.1.69+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-arm64 is newer in the target suite (6.5.13+1 6.1.69+1)
• linux-signed-i386_pu (6.5.13+1 to 6.1.69+1)
  • Migration status for linux-signed-i386_pu (6.5.13+1 to 6.1.69+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-i386 is newer in the target suite (6.5.13+1 6.1.69+1)
• linux_pu (6.5.13-1 to 6.1.69-1)
  • Migration status for linux_pu (6.5.13-1 to 6.1.69-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux is newer in the target suite (6.5.13-1 6.1.69-1)
• localslackirc_pu (1.24-1 to 1.17-1.1+deb12u1)
  • Migration status for localslackirc_pu (1.24-1 to 1.17-1.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: localslackirc is newer in the target suite (1.24-1 1.17-1.1+deb12u1)
• lua-system/amd64 (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/amd64 (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/arm64 (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/arm64 (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/armel (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/armel (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/armhf (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/armhf (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/i386 (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/i386 (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/mips64el (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/mips64el (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/ppc64el (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/ppc64el (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lua-system/s390x (0.2.1-6 to 0.2.1-6)
  • Migration status for lua-system/s390x (0.2.1-6 to 0.2.1-6): Will attempt migration (Any information below is purely informational)
• lz4/amd64 (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/amd64 (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/arm64 (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/arm64 (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/armel (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/armel (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/armhf (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/armhf (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/i386 (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/i386 (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/mips64el (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/mips64el (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/ppc64el (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/ppc64el (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• lz4/s390x (1.9.4-1 to 1.9.4-1)
  • Migration status for lz4/s390x (1.9.4-1 to 1.9.4-1): Will attempt migration (Any information below is purely informational)
• mpclib3/amd64 (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/amd64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/arm64 (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/arm64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/armel (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/armel (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/armhf (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/armhf (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/i386 (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/i386 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/mips64el (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/mips64el (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/ppc64el (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/ppc64el (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mpclib3/s390x (1.3.1-1 to 1.3.1-1)
  • Migration status for mpclib3/s390x (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• mu-editor/amd64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/amd64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/arm64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/arm64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/armel (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/armel (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/armhf (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/armhf (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/i386 (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/i386 (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/mips64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/mips64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/ppc64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/ppc64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mu-editor/s390x (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for mu-editor/s390x (1.0.3+dfsg-6 to 1.0.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/amd64 (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/amd64 (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/arm64 (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/arm64 (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/armel (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/armel (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/armhf (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/armhf (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/i386 (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/i386 (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/mips64el (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/mips64el (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/ppc64el (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/ppc64el (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ndcube/s390x (2.0.3-1 to 2.0.3-1)
  • Migration status for ndcube/s390x (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nftables/amd64 (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/amd64 (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/arm64 (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/arm64 (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/armel (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/armel (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/armhf (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/armhf (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/i386 (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/i386 (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/mips64el (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/mips64el (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/ppc64el (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/ppc64el (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• nftables/s390x (1.0.9-1 to 1.0.9-1)
  • Migration status for nftables/s390x (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• node-iconv/armel (3.0.1+~3.0.0-1 to 3.0.1+~3.0.0-1)
  • Migration status for node-iconv/armel (3.0.1+~3.0.0-1 to 3.0.1+~3.0.0-1): Will attempt migration (Any information below is purely informational)
• node-modern-syslog/armel (1.2.0-4 to 1.2.0-4)
  • Migration status for node-modern-syslog/armel (1.2.0-4 to 1.2.0-4): Will attempt migration (Any information below is purely informational)
• node-opencv/armel (7.0.0+git20200316.f0a03a4b-1 to 7.0.0+git20200316.f0a03a4b-1)
  • Migration status for node-opencv/armel (7.0.0+git20200316.f0a03a4b-1 to 7.0.0+git20200316.f0a03a4b-1): Will attempt migration (Any information below is purely informational)
• onionprobe_pu (1.1.2+ds-1 to 1.0.0+ds-2.1+deb12u1)
  • Migration status for onionprobe_pu (1.1.2+ds-1 to 1.0.0+ds-2.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: onionprobe is newer in the target suite (1.1.2+ds-1 1.0.0+ds-2.1+deb12u1)
• openjpeg2/amd64 (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/amd64 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/arm64 (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/arm64 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/armel (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/armel (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/armhf (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/armhf (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/i386 (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/i386 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/mips64el (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/mips64el (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/ppc64el (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/ppc64el (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/s390x (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/s390x (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openldap/amd64 (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/amd64 (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/arm64 (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/arm64 (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/armel (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/armel (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/armhf (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/armhf (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/i386 (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/i386 (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/mips64el (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/mips64el (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/ppc64el (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/ppc64el (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openldap/s390x (2.5.13+dfsg-5 to 2.5.13+dfsg-5)
  • Migration status for openldap/s390x (2.5.13+dfsg-5 to 2.5.13+dfsg-5): Will attempt migration (Any information below is purely informational)
• openssh_pu (1:9.6p1-2 to 1:9.2p1-2+deb12u2)
  • Migration status for openssh_pu (1:9.6p1-2 to 1:9.2p1-2+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openssh is newer in the target suite (1:9.6p1-2 1:9.2p1-2+deb12u2)
• openstack-trove/amd64 (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/amd64 (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/arm64 (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/arm64 (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/armel (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/armel (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/armhf (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/armhf (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/i386 (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/i386 (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/mips64el (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/mips64el (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/ppc64el (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/ppc64el (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-trove/s390x (1:20.0.0-2 to 1:20.0.0-2)
  • Migration status for openstack-trove/s390x (1:20.0.0-2 to 1:20.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pam/amd64 (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/amd64 (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/arm64 (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/arm64 (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/armel (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/armel (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/armhf (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/armhf (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/i386 (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/i386 (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/mips64el (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/mips64el (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/ppc64el (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/ppc64el (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• pam/s390x (1.5.2-9.1 to 1.5.2-9.1)
  • Migration status for pam/s390x (1.5.2-9.1 to 1.5.2-9.1): Will attempt migration (Any information below is purely informational)
• perl/amd64 (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/amd64 (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/arm64 (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/arm64 (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/armel (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/armel (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/armhf (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/armhf (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/i386 (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/i386 (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/mips64el (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/mips64el (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/ppc64el (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/ppc64el (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• perl/s390x (5.36.0-10 to 5.36.0-10)
  • Migration status for perl/s390x (5.36.0-10 to 5.36.0-10): Will attempt migration (Any information below is purely informational)
• pipewire_pu (1.0.0-1 to 0.3.65-3+deb12u1)
  • Migration status for pipewire_pu (1.0.0-1 to 0.3.65-3+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: pipewire is newer in the target suite (1.0.0-1 0.3.65-3+deb12u1)
• pkgconf/amd64 (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/amd64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/arm64 (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/arm64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/armel (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/armel (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/armhf (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/armhf (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/i386 (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/i386 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/mips64el (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/mips64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/ppc64el (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/ppc64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• pkgconf/s390x (1.8.1-1 to 1.8.1-1)
  • Migration status for pkgconf/s390x (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• polymake/amd64 (4.11-2 to 4.11-2)
  • Migration status for polymake/amd64 (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/amd64 flint (not considered)
    • Invalidated by dependency
• polymake/arm64 (4.11-2 to 4.11-2)
  • Migration status for polymake/arm64 (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/arm64 flint (not considered)
    • Invalidated by dependency
• polymake/armel (4.11-2 to 4.11-2)
  • Migration status for polymake/armel (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/armel flint (not considered)
    • Invalidated by dependency
• polymake/armhf (4.11-2 to 4.11-2)
  • Migration status for polymake/armhf (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/armhf flint (not considered)
    • Invalidated by dependency
• polymake/i386 (4.11-2 to 4.11-2)
  • Migration status for polymake/i386 (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/i386 flint (not considered)
    • Invalidated by dependency
• polymake/mips64el (4.11-2 to 4.11-2)
  • Migration status for polymake/mips64el (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/mips64el flint (not considered)
    • Invalidated by dependency
    • Depends: polymake/mips64el e-antic
• polymake/ppc64el (4.11-2 to 4.11-2)
  • Migration status for polymake/ppc64el (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/ppc64el flint (not considered)
    • Invalidated by dependency
• polymake/s390x (4.11-2 to 4.11-2)
  • Migration status for polymake/s390x (4.11-2 to 4.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake/s390x flint (not considered)
    • Invalidated by dependency
• postfix_pu (3.8.4-1 to 3.7.9-0+deb12u1)
  • Migration status for postfix_pu (3.8.4-1 to 3.7.9-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: postfix is newer in the target suite (3.8.4-1 3.7.9-0+deb12u1)
• procps/amd64 (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/amd64 (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/arm64 (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/arm64 (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/armel (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/armel (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/armhf (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/armhf (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/i386 (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/i386 (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/mips64el (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/mips64el (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/ppc64el (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/ppc64el (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• procps/s390x (2:4.0.4-2 to 2:4.0.4-2)
  • Migration status for procps/s390x (2:4.0.4-2 to 2:4.0.4-2): Will attempt migration (Any information below is purely informational)
• proftpd-mod-autohost/amd64 (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/amd64 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/amd64 proftpd-dfsg
• proftpd-mod-autohost/arm64 (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/arm64 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/arm64 proftpd-dfsg
• proftpd-mod-autohost/armel (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/armel (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/armel proftpd-dfsg
• proftpd-mod-autohost/armhf (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/armhf (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/armhf proftpd-dfsg
• proftpd-mod-autohost/i386 (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/i386 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/i386 proftpd-dfsg
• proftpd-mod-autohost/mips64el (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/mips64el (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/mips64el proftpd-dfsg
• proftpd-mod-autohost/ppc64el (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/ppc64el (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/ppc64el proftpd-dfsg
• proftpd-mod-autohost/s390x (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/s390x (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-autohost/s390x proftpd-dfsg
• proftpd-mod-case/amd64 (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/amd64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/amd64 proftpd-dfsg
• proftpd-mod-case/arm64 (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/arm64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/arm64 proftpd-dfsg
• proftpd-mod-case/armel (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/armel (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/armel proftpd-dfsg
• proftpd-mod-case/armhf (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/armhf (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/armhf proftpd-dfsg
• proftpd-mod-case/i386 (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/i386 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/i386 proftpd-dfsg
• proftpd-mod-case/mips64el (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/mips64el (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/mips64el proftpd-dfsg
• proftpd-mod-case/ppc64el (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/ppc64el (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/ppc64el proftpd-dfsg
• proftpd-mod-case/s390x (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/s390x (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-case/s390x proftpd-dfsg
• proftpd-mod-clamav/amd64 (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/amd64 (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/amd64 proftpd-dfsg
• proftpd-mod-clamav/arm64 (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/arm64 (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/arm64 proftpd-dfsg
• proftpd-mod-clamav/armel (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/armel (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/armel proftpd-dfsg
• proftpd-mod-clamav/armhf (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/armhf (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/armhf proftpd-dfsg
• proftpd-mod-clamav/i386 (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/i386 (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/i386 proftpd-dfsg
• proftpd-mod-clamav/mips64el (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/mips64el (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/mips64el proftpd-dfsg
• proftpd-mod-clamav/ppc64el (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/ppc64el (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/ppc64el proftpd-dfsg
• proftpd-mod-clamav/s390x (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/s390x (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-clamav/s390x proftpd-dfsg
• proftpd-mod-counter/amd64 (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/amd64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/amd64 proftpd-dfsg
• proftpd-mod-counter/arm64 (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/arm64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/arm64 proftpd-dfsg
• proftpd-mod-counter/armel (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/armel (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/armel proftpd-dfsg
• proftpd-mod-counter/armhf (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/armhf (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/armhf proftpd-dfsg
• proftpd-mod-counter/i386 (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/i386 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/i386 proftpd-dfsg
• proftpd-mod-counter/mips64el (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/mips64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/mips64el proftpd-dfsg
• proftpd-mod-counter/ppc64el (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/ppc64el (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/ppc64el proftpd-dfsg
• proftpd-mod-counter/s390x (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/s390x (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-counter/s390x proftpd-dfsg
• proftpd-mod-fsync/amd64 (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/amd64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/amd64 proftpd-dfsg
• proftpd-mod-fsync/arm64 (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/arm64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/arm64 proftpd-dfsg
• proftpd-mod-fsync/armel (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/armel (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/armel proftpd-dfsg
• proftpd-mod-fsync/armhf (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/armhf (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/armhf proftpd-dfsg
• proftpd-mod-fsync/i386 (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/i386 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/i386 proftpd-dfsg
• proftpd-mod-fsync/mips64el (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/mips64el (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/mips64el proftpd-dfsg
• proftpd-mod-fsync/ppc64el (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/ppc64el (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/ppc64el proftpd-dfsg
• proftpd-mod-fsync/s390x (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/s390x (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-fsync/s390x proftpd-dfsg
• proftpd-mod-geoip2/amd64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/amd64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/amd64 proftpd-dfsg
• proftpd-mod-geoip2/arm64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/arm64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/arm64 proftpd-dfsg
• proftpd-mod-geoip2/armel (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/armel (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/armel proftpd-dfsg
• proftpd-mod-geoip2/armhf (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/armhf (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/armhf proftpd-dfsg
• proftpd-mod-geoip2/i386 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/i386 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/i386 proftpd-dfsg
• proftpd-mod-geoip2/mips64el (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/mips64el (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/mips64el proftpd-dfsg
• proftpd-mod-geoip2/ppc64el (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/ppc64el (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/ppc64el proftpd-dfsg
• proftpd-mod-geoip2/s390x (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/s390x (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-geoip2/s390x proftpd-dfsg
• proftpd-mod-kafka/amd64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/amd64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/amd64 proftpd-dfsg
• proftpd-mod-kafka/arm64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/arm64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/arm64 proftpd-dfsg
• proftpd-mod-kafka/armel (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/armel (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/armel proftpd-dfsg
• proftpd-mod-kafka/armhf (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/armhf (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/armhf proftpd-dfsg
• proftpd-mod-kafka/i386 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/i386 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/i386 proftpd-dfsg
• proftpd-mod-kafka/mips64el (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/mips64el (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/mips64el proftpd-dfsg
• proftpd-mod-kafka/ppc64el (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/ppc64el (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/ppc64el proftpd-dfsg
• proftpd-mod-kafka/s390x (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/s390x (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-kafka/s390x proftpd-dfsg
• proftpd-mod-msg/amd64 (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/amd64 (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/amd64 proftpd-dfsg
• proftpd-mod-msg/arm64 (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/arm64 (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/arm64 proftpd-dfsg
• proftpd-mod-msg/armel (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/armel (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/armel proftpd-dfsg
• proftpd-mod-msg/armhf (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/armhf (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/armhf proftpd-dfsg
• proftpd-mod-msg/i386 (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/i386 (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/i386 proftpd-dfsg
• proftpd-mod-msg/mips64el (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/mips64el (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/mips64el proftpd-dfsg
• proftpd-mod-msg/ppc64el (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/ppc64el (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/ppc64el proftpd-dfsg
• proftpd-mod-msg/s390x (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/s390x (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-msg/s390x proftpd-dfsg
• proftpd-mod-sftp-ldap/amd64 (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/amd64 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/amd64 proftpd-dfsg
• proftpd-mod-sftp-ldap/arm64 (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/arm64 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/arm64 proftpd-dfsg
• proftpd-mod-sftp-ldap/armel (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/armel (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/armel proftpd-dfsg
• proftpd-mod-sftp-ldap/armhf (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/armhf (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/armhf proftpd-dfsg
• proftpd-mod-sftp-ldap/i386 (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/i386 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/i386 proftpd-dfsg
• proftpd-mod-sftp-ldap/mips64el (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/mips64el (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/mips64el proftpd-dfsg
• proftpd-mod-sftp-ldap/ppc64el (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/ppc64el (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/ppc64el proftpd-dfsg
• proftpd-mod-sftp-ldap/s390x (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/s390x (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-sftp-ldap/s390x proftpd-dfsg
• proftpd-mod-statsd/amd64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/amd64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/amd64 proftpd-dfsg
• proftpd-mod-statsd/arm64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/arm64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/arm64 proftpd-dfsg
• proftpd-mod-statsd/armel (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/armel (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/armel proftpd-dfsg
• proftpd-mod-statsd/armhf (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/armhf (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/armhf proftpd-dfsg
• proftpd-mod-statsd/i386 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/i386 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/i386 proftpd-dfsg
• proftpd-mod-statsd/mips64el (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/mips64el (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/mips64el proftpd-dfsg
• proftpd-mod-statsd/ppc64el (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/ppc64el (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/ppc64el proftpd-dfsg
• proftpd-mod-statsd/s390x (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/s390x (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-statsd/s390x proftpd-dfsg
• proftpd-mod-tar/amd64 (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/amd64 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/amd64 proftpd-dfsg
• proftpd-mod-tar/arm64 (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/arm64 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/arm64 proftpd-dfsg
• proftpd-mod-tar/armel (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/armel (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/armel proftpd-dfsg
• proftpd-mod-tar/armhf (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/armhf (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/armhf proftpd-dfsg
• proftpd-mod-tar/i386 (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/i386 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/i386 proftpd-dfsg
• proftpd-mod-tar/mips64el (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/mips64el (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/mips64el proftpd-dfsg
• proftpd-mod-tar/ppc64el (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/ppc64el (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/ppc64el proftpd-dfsg
• proftpd-mod-tar/s390x (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/s390x (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-tar/s390x proftpd-dfsg
• proftpd-mod-vroot/amd64 (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/amd64 (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/amd64 proftpd-dfsg
• proftpd-mod-vroot/arm64 (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/arm64 (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/arm64 proftpd-dfsg
• proftpd-mod-vroot/armel (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/armel (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/armel proftpd-dfsg
• proftpd-mod-vroot/armhf (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/armhf (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/armhf proftpd-dfsg
• proftpd-mod-vroot/i386 (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/i386 (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/i386 proftpd-dfsg
• proftpd-mod-vroot/mips64el (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/mips64el (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/mips64el proftpd-dfsg
• proftpd-mod-vroot/ppc64el (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/ppc64el (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/ppc64el proftpd-dfsg
• proftpd-mod-vroot/s390x (0.9.11-1 to 0.9.11-1)
  • Migration status for proftpd-mod-vroot/s390x (0.9.11-1 to 0.9.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-vroot/s390x proftpd-dfsg
• putty_pu (0.80-1 to 0.78-2+deb12u1)
  • Migration status for putty_pu (0.80-1 to 0.78-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: putty is newer in the target suite (0.80-1 0.78-2+deb12u1)
• python-cassandra-driver/amd64 (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/amd64 (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/arm64 (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/arm64 (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/armel (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/armel (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/armhf (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/armhf (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/i386 (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/i386 (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/mips64el (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/mips64el (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/ppc64el (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/ppc64el (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-cassandra-driver/s390x (3.28.0-1 to 3.28.0-1)
  • Migration status for python-cassandra-driver/s390x (3.28.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/amd64 (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/amd64 (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/arm64 (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/arm64 (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/armel (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/armel (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/armhf (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/armhf (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/i386 (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/i386 (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/mips64el (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/mips64el (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/ppc64el (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/ppc64el (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-uflash/s390x (1.2.4+dfsg-10 to 1.2.4+dfsg-10)
  • Migration status for python-uflash/s390x (1.2.4+dfsg-10 to 1.2.4+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pytorch/ppc64el (2.0.1+dfsg-5 to 2.0.1+dfsg-5)
  • Migration status for pytorch/ppc64el (2.0.1+dfsg-5 to 2.0.1+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pytorch/ppc64el onnx (not considered)
    • Invalidated by dependency
    • Depends: pytorch/ppc64el benchmark
    • Depends: pytorch/ppc64el gloo
• pytorch/s390x (2.0.1+dfsg-5 to 2.0.1+dfsg-5)
  • Migration status for pytorch/s390x (2.0.1+dfsg-5 to 2.0.1+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pytorch/s390x onnx (not considered)
    • Invalidated by dependency
    • Depends: pytorch/s390x benchmark
    • Depends: pytorch/s390x gloo
• qbs/mips64el (2.1.2-2 to 2.1.2-2)
  • Migration status for qbs/mips64el (2.1.2-2 to 2.1.2-2): Will attempt migration (Any information below is purely informational)
• ros2-performance-test-fixture/amd64 (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/amd64 (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/amd64 benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/arm64 (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/arm64 (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/arm64 benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/armel (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/armel benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/armhf (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/armhf (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/armhf benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/i386 (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/i386 (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/i386 benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/mips64el (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/mips64el (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/mips64el benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/ppc64el (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/ppc64el (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/ppc64el benchmark (not considered)
    • Invalidated by dependency
• ros2-performance-test-fixture/s390x (0.2.0-1 to 0.2.0-1)
  • Migration status for ros2-performance-test-fixture/s390x (0.2.0-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ros2-performance-test-fixture/s390x benchmark (not considered)
    • Invalidated by dependency
• roundcube_pu (1.6.5+dfsg-1 to 1.6.5+dfsg-1~deb12u1)
  • Migration status for roundcube_pu (1.6.5+dfsg-1 to 1.6.5+dfsg-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: roundcube is newer in the target suite (1.6.5+dfsg-1 1.6.5+dfsg-1~deb12u1)
• ruby-rmagick/mips64el (5.3.0-2 to 5.3.0-2)
  • Migration status for ruby-rmagick/mips64el (5.3.0-2 to 5.3.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/amd64 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/amd64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/arm64 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/arm64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/armel (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/armel (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/armhf (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/armhf (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/i386 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/i386 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/mips64el (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/mips64el (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/ppc64el (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/ppc64el (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/s390x (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/s390x (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• rust-apr/mips64el (0.1.9-1 to 0.1.9-1)
  • Migration status for rust-apr/mips64el (0.1.9-1 to 0.1.9-1): Will attempt migration (Any information below is purely informational)
• rust-arrayvec/mips64el (0.7.4-2 to 0.7.4-2)
  • Migration status for rust-arrayvec/mips64el (0.7.4-2 to 0.7.4-2): Will attempt migration (Any information below is purely informational)
• rust-chunked-transfer/mips64el (1.4.0-1 to 1.4.0-1)
  • Migration status for rust-chunked-transfer/mips64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-dhcproto/mips64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-dhcproto/mips64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-dhcproto/ppc64el (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-dhcproto/ppc64el (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-dhcproto/s390x (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-dhcproto/s390x (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• rust-downcast-rs/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-downcast-rs/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-ghash/mips64el (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-ghash/mips64el (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-gix-attributes/ppc64el (0.20.1-1 to 0.20.1-1)
  • Migration status for rust-gix-attributes/ppc64el (0.20.1-1 to 0.20.1-1): Will attempt migration (Any information below is purely informational)
• rust-gix-ignore/ppc64el (0.9.1-1 to 0.9.1-1)
  • Migration status for rust-gix-ignore/ppc64el (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• rust-gix-tempfile/ppc64el (11.0.1-1 to 11.0.1-1)
  • Migration status for rust-gix-tempfile/ppc64el (11.0.1-1 to 11.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-iana-time-zone/s390x (0.1.53-1 to 0.1.53-1)
  • Migration status for rust-iana-time-zone/s390x (0.1.53-1 to 0.1.53-1): Will attempt migration (Any information below is purely informational)
• rust-khronos-api/mips64el (3.1.0-1 to 3.1.0-1)
  • Migration status for rust-khronos-api/mips64el (3.1.0-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-libgweather/mips64el (4.3.1-1 to 4.3.1-1)
  • Migration status for rust-libgweather/mips64el (4.3.1-1 to 4.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-nbd/mips64el (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-nbd/mips64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ntest-proc-macro-helper/s390x (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-ntest-proc-macro-helper/s390x (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-pkg-version/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for rust-pkg-version/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-tree-sitter-highlight/armel (0.20.1-1 to 0.20.1-1)
  • Migration status for rust-tree-sitter-highlight/armel (0.20.1-1 to 0.20.1-1): Will attempt migration (Any information below is purely informational)
• rust-unic-langid-macros-impl/s390x (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-unic-langid-macros-impl/s390x (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• shadow/amd64 (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/amd64 (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/arm64 (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/arm64 (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/armel (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/armel (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/armhf (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/armhf (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/i386 (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/i386 (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/mips64el (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/mips64el (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/ppc64el (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/ppc64el (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• shadow/s390x (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3)
  • Migration status for shadow/s390x (1:4.13+dfsg1-3 to 1:4.13+dfsg1-3): Will attempt migration (Any information below is purely informational)
• singular/amd64 (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/amd64 (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/amd64 flint (not considered)
    • Invalidated by dependency
• singular/arm64 (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/arm64 (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/arm64 flint (not considered)
    • Invalidated by dependency
• singular/armel (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/armel (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/armel flint (not considered)
    • Invalidated by dependency
• singular/armhf (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/armhf (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/armhf flint (not considered)
    • Invalidated by dependency
• singular/i386 (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/i386 (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/i386 flint (not considered)
    • Invalidated by dependency
• singular/mips64el (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/mips64el (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/mips64el flint (not considered)
    • Invalidated by dependency
• singular/ppc64el (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/ppc64el (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/ppc64el flint (not considered)
    • Invalidated by dependency
• singular/s390x (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1)
  • Migration status for singular/s390x (1:4.3.2-p10+ds-1 to 1:4.3.2-p10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: singular/s390x flint (not considered)
    • Invalidated by dependency
• specutils/amd64 (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/amd64 (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/arm64 (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/arm64 (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/armel (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/armel (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/armhf (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/armhf (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/i386 (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/i386 (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/mips64el (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/mips64el (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/ppc64el (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/ppc64el (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• specutils/s390x (1.12.0-1 to 1.12.0-1)
  • Migration status for specutils/s390x (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sundials/amd64 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/amd64 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/amd64 petsc (not considered)
    • Invalidated by dependency
• sundials/arm64 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/arm64 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/arm64 petsc (not considered)
    • Invalidated by dependency
• sundials/armel (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/armel (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/armel petsc (not considered)
    • Invalidated by dependency
• sundials/armhf (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/armhf (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/armhf petsc (not considered)
    • Invalidated by dependency
• sundials/i386 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/i386 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/i386 petsc (not considered)
    • Invalidated by dependency
• sundials/mips64el (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/mips64el (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/mips64el petsc (not considered)
    • Invalidated by dependency
• sundials/ppc64el (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/ppc64el (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/ppc64el petsc (not considered)
    • Invalidated by dependency
• sundials/s390x (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/s390x (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sundials/s390x petsc (not considered)
    • Invalidated by dependency
• swupdate_pu (2023.12+dfsg-1 to 2022.12+dfsg-4+deb12u1)
  • Migration status for swupdate_pu (2023.12+dfsg-1 to 2022.12+dfsg-4+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: swupdate is newer in the target suite (2023.12+dfsg-1 2022.12+dfsg-4+deb12u1)
• thunderbird_pu (1:115.6.0-1 to 1:115.6.0-1~deb12u1)
  • Migration status for thunderbird_pu (1:115.6.0-1 to 1:115.6.0-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: thunderbird is newer in the target suite (1:115.6.0-1 1:115.6.0-1~deb12u1)
• w3m/amd64 (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/amd64 (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/arm64 (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/arm64 (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/armel (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/armel (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/armhf (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/armhf (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/i386 (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/i386 (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/mips64el (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/mips64el (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/ppc64el (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/ppc64el (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• w3m/s390x (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/s390x (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• x264/amd64 (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/amd64 (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/arm64 (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/arm64 (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/armel (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/armel (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/armhf (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/armhf (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/i386 (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/i386 (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/mips64el (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/mips64el (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/ppc64el (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/ppc64el (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• x264/s390x (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3)
  • Migration status for x264/s390x (2:0.164.3095+gitbaee400-3 to 2:0.164.3095+gitbaee400-3): Will attempt migration (Any information below is purely informational)
• xorg-server_pu (2:21.1.10-1 to 2:21.1.7-3+deb12u4)
  • Migration status for xorg-server_pu (2:21.1.10-1 to 2:21.1.7-3+deb12u4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: xorg-server is newer in the target suite (2:21.1.10-1 2:21.1.7-3+deb12u4)
• z3/amd64 (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/amd64 (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/arm64 (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/arm64 (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/armel (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/armel (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/armhf (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/armhf (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/i386 (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/i386 (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/mips64el (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/mips64el (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/ppc64el (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/ppc64el (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• z3/s390x (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/s390x (4.8.12-3.1 to 4.8.12-3.1): Will attempt migration (Any information below is purely informational)
• amberol (- to 0.10.3-2)
  • Migration status for amberol (- to 0.10.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amberol.html
    • autopkgtest for amberol/0.10.3-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• apt-verify (- to 2.0-1)
  • Migration status for apt-verify (- to 2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-verify.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• asciiart (0.0.10-2 to 0.3.0-1)
  • Migration status for asciiart (0.0.10-2 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by abhijith@openmailbox.org, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asciiart.html
    • autopkgtest for asciiart/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• atop (2.9.0-2 to 2.10.0-1)
  • Migration status for atop (2.9.0-2 to 2.10.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atop.html
    • autopkgtest for atop/2.10.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• atril (1.26.1-1 to 1.26.1-3)
  • Migration status for atril (1.26.1-1 to 1.26.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atril.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• binutils-bpf (13 to 14)
  • Migration status for binutils-bpf (13 to 14): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-bpf.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• biomaj3-core (3.0.28-1 to 3.0.28-2)
  • Migration status for biomaj3-core (3.0.28-1 to 3.0.28-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biomaj3-core.html
    • autopkgtest for biomaj3-core/3.0.28-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• blupimania (- to 1.6.2-15-g8f23b7a-1)
  • Migration status for blupimania (- to 1.6.2-15-g8f23b7a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by odyx
    • Not built on buildd: arch all binaries uploaded by odyx, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blupimania.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bnd (5.0.1-4 to 5.0.1-5)
  • Migration status for bnd (5.0.1-4 to 5.0.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bnd.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bookworm (1.1.2+git20210715-3 to 1.1.2+git20210715-4)
  • Migration status for bookworm (1.1.2+git20210715-3 to 1.1.2+git20210715-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookworm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• buildbot (3.9.2-2 to 3.10.1-1)
  • Migration status for buildbot (3.9.2-2 to 3.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating buildbot will fix bugs in testing: #1057929
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buildbot.html
    • autopkgtest for buildbot/3.10.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• cc-cedict (- to 0.0~repack20231203-1)
  • Migration status for cc-cedict (- to 0.0~repack20231203-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by paulliu, a new source-only upload is needed to allow migration
    • Too young, only 1 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cc-cedict.html
    • autopkgtest for cc-cedict/0.0~repack20231203-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• cjs (6.0.0-1 to 6.0.0-2)
  • Migration status for cjs (6.0.0-1 to 6.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cjs.html
    • autopkgtest for cjs/6.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• clog (- to 1.3.0-1.1)
  • Migration status for clog (- to 1.3.0-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clog.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• clonezilla (5.5.20-1 to 5.5.23-1)
  • Migration status for clonezilla (5.5.20-1 to 5.5.23-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clonezilla.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cnvkit (0.9.9-2 to 0.9.10-1)
  • Migration status for cnvkit (0.9.9-2 to 0.9.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cnvkit.html
    • autopkgtest for cnvkit/0.9.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• condor (- to 23.2.0+dfsg-2)
  • Migration status for condor (- to 23.2.0+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/condor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• connman (1.42-3 to 1.42-5)
  • Migration status for connman (1.42-3 to 1.42-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/connman.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debian-ports-archive-keyring (2023.02.01 to 2024.01.05)
  • Migration status for debian-ports-archive-keyring (2023.02.01 to 2024.01.05): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-ports-archive-keyring.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dh-octave (1.6.0 to 1.6.1)
  • Migration status for dh-octave (1.6.0 to 1.6.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-octave.html
    • autopkgtest for dh-octave/1.6.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• dom4j (2.1.3-2 to 2.1.4-1)
  • Migration status for dom4j (2.1.3-2 to 2.1.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dom4j.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• durdraw (- to 0.24.1-1)
  • Migration status for durdraw (- to 0.24.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/durdraw.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• epiphany-browser (45.1-1 to 45.2-1)
  • Migration status for epiphany-browser (45.1-1 to 45.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epiphany-browser.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• esup-el (- to 0.7.1+git20220203.4b49c8d-1)
  • Migration status for esup-el (- to 0.7.1+git20220203.4b49c8d-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esup-el.html
    • autopkgtest for esup-el/0.7.1+git20220203.4b49c8d-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• exim4 (4.97-3 to 4.97-4)
  • Migration status for exim4 (4.97-3 to 4.97-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exim4.html
    • autopkgtest for exim4/4.97-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• fcitx5 (5.1.5-1 to 5.1.6-1)
  • Migration status for fcitx5 (5.1.5-1 to 5.1.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fcitx5.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fcitx5-table-extra (- to 5.1.0-1)
  • Migration status for fcitx5-table-extra (- to 5.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by 073plan@gmail.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fcitx5-table-extra.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fheroes2 (- to 1.0.9+dfsg-1)
  • Migration status for fheroes2 (- to 1.0.9+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 10 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• folium (0.15.0+dfsg-1 to 0.15.1+dfsg-2)
  • Migration status for folium (0.15.0+dfsg-1 to 0.15.1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/folium.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• g-golf (- to 0.8.0~rc1-1)
  • Migration status for g-golf (- to 0.8.0~rc1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by weinholt
    • Not built on buildd: arch all binaries uploaded by weinholt, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/g-golf.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ghostscript (10.02.1~dfsg-1 to 10.02.1~dfsg-2)
  • Migration status for ghostscript (10.02.1~dfsg-1 to 10.02.1~dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for asymptote/2.86+ds1-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ghostscript/10.02.1~dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating ghostscript will fix bugs in testing: #1036869
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/ghostscript.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gkrellm-radio (2.0.4-2 to 2.0.4-3)
  • Migration status for gkrellm-radio (2.0.4-2 to 2.0.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: gkrellm-radio lirc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gkrellm-radio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-software (45.2-1 to 45.3-1)
  • Migration status for gnome-software (45.2-1 to 45.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating gnome-software will fix bugs in testing: #1059983
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-software.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-1.22 (- to 1.22~rc1-1)
  • Migration status for golang-1.22 (- to 1.22~rc1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • golang-1.22/arm64 has unsatisfiable dependency
    • Not built on buildd: arch all binaries uploaded by i@zhsj.me, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by i@zhsj.me
    • autopkgtest for golang-1.22/1.22~rc1-1: amd64: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.22.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-calmh-incontainer (- to 0.0~git20221224.b3e71b1-1)
  • Migration status for golang-github-calmh-incontainer (- to 0.0~git20221224.b3e71b1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by felix.sipma@ens-lyon.org, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-calmh-incontainer.html
    • autopkgtest for golang-github-calmh-incontainer/0.0~git20221224.b3e71b1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-darkhz-tview (- to 0.0~git20231221.b7c392e-1)
  • Migration status for golang-github-darkhz-tview (- to 0.0~git20231221.b7c392e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-darkhz-tview.html
    • autopkgtest for golang-github-darkhz-tview/0.0~git20231221.b7c392e-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-davidmytton-url-verifier (- to 1.0.0-1)
  • Migration status for golang-github-davidmytton-url-verifier (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-davidmytton-url-verifier.html
    • autopkgtest for golang-github-davidmytton-url-verifier/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-etherlabsio-go-m3u8 (- to 1.0.0-1)
  • Migration status for golang-github-etherlabsio-go-m3u8 (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-etherlabsio-go-m3u8.html
    • autopkgtest for golang-github-etherlabsio-go-m3u8/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-gammazero-deque (- to 0.2.1-1)
  • Migration status for golang-github-gammazero-deque (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gammazero-deque.html
    • autopkgtest for golang-github-gammazero-deque/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-ovn-org-libovsdb (- to 0.6.0-2)
  • Migration status for golang-github-ovn-org-libovsdb (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-ovn-org-libovsdb/0.6.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ovn-org-libovsdb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-theckman-yacspin (- to 0.13.12-1)
  • Migration status for golang-github-theckman-yacspin (- to 0.13.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-theckman-yacspin.html
    • autopkgtest for golang-github-theckman-yacspin/0.13.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• goto-chg-el (1.7.3-1 to 1.7.5-1)
  • Migration status for goto-chg-el (1.7.3-1 to 1.7.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goto-chg-el.html
    • autopkgtest for goto-chg-el/1.7.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• groops (- to 0+git20230516+ds-1)
  • Migration status for groops (- to 0+git20230516+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gthumb (3:3.12.4-1 to 3:3.12.4-2)
  • Migration status for gthumb (3:3.12.4-1 to 3:3.12.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gthumb.html
    • autopkgtest for gthumb/3:3.12.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• gtksheet (- to 4.3.12+dfsg-2)
  • Migration status for gtksheet (- to 4.3.12+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtksheet.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gudhi (3.8.0+dfsg-1 to 3.9.0+dfsg-1)
  • Migration status for gudhi (3.8.0+dfsg-1 to 3.9.0+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gudhi.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gvfs (1.52.1-1 to 1.52.2-1)
  • Migration status for gvfs (1.52.1-1 to 1.52.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvfs.html
    • autopkgtest for gvfs/1.52.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-hslua-cli (1.3.0-2 to 1.4.1-1)
  • Migration status for haskell-hslua-cli (1.3.0-2 to 1.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): haskell-hslua-cli haskell-hslua-repl
    • Build-Depends-Indep: haskell-hslua-cli haskell-hslua-repl
    • Depends: haskell-hslua-cli haskell-hslua-repl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hslua-cli.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-misfortune (0.1.2.1-2 to 0.1.2.1-3)
  • Migration status for haskell-misfortune (0.1.2.1-2 to 0.1.2.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-misfortune.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hcloud-python (1.31.0-1 to 1.33.2-1)
  • Migration status for hcloud-python (1.31.0-1 to 1.33.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hcloud-python.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• httpbin (0.10.1+dfsg-3 to 0.10.1+dfsg-4)
  • Migration status for httpbin (0.10.1+dfsg-3 to 0.10.1+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/httpbin.html
    • autopkgtest for httpbin/0.10.1+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ikvswitch (- to 0.0.1)
  • Migration status for ikvswitch (- to 0.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ikvswitch.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• invidtui (- to 0.3.7-1)
  • Migration status for invidtui (- to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for invidtui/0.3.7-1: amd64: Regression or new test ♻
    • invidtui unsatisfiable Build-Depends(-Arch) on amd64: golang-github-darkhz-mpvipc-dev
    • Not built on buildd: arch amd64 binaries uploaded by tar
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): invidtui golang-github-darkhz-tview
    • Build-Depends(-Arch): invidtui golang-github-davidmytton-url-verifier
    • Build-Depends(-Arch): invidtui golang-github-etherlabsio-go-m3u8
    • Build-Depends(-Arch): invidtui golang-github-gammazero-deque
    • Build-Depends(-Arch): invidtui golang-github-theckman-yacspin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invidtui.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• isodate (0.6.1-1 to 0.6.1-2)
  • Migration status for isodate (0.6.1-1 to 0.6.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/isodate.html
    • autopkgtest for isodate/0.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ivy (2.5.1-2 to 2.5.2-1)
  • Migration status for ivy (2.5.1-2 to 2.5.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ivy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kalk (- to 23.08.3-1)
  • Migration status for kalk (- to 23.08.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kalk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kclock (- to 23.08.0-1)
  • Migration status for kclock (- to 23.08.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kclock.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kdsingleapplication (- to 1.0.0-1)
  • Migration status for kdsingleapplication (- to 1.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdsingleapplication.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lcov (2.0-3 to 2.0-4)
  • Migration status for lcov (2.0-3 to 2.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lcov.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libbgcode (- to 0.0~git20231219.7aaf717-1)
  • Migration status for libbgcode (- to 0.0~git20231219.7aaf717-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by hyperair
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbgcode.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libchdr (- to 0.0~git20230918.9108f34+dfsg-2)
  • Migration status for libchdr (- to 0.0~git20230918.9108f34+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libchdr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libclipboard-perl (0.27-1 to 0.28-1)
  • Migration status for libclipboard-perl (0.27-1 to 0.28-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libclipboard-perl.html
    • autopkgtest for libclipboard-perl/0.28-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libcommons-cli-java (1.5.0-1 to 1.6.0-1)
  • Migration status for libcommons-cli-java (1.5.0-1 to 1.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommons-cli-java.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libcommons-lang3-java (3.13.0-1 to 3.14.0-1)
  • Migration status for libcommons-lang3-java (3.13.0-1 to 3.14.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommons-lang3-java.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libcommons-logging-java (1.2-4 to 1.3.0-1)
  • Migration status for libcommons-logging-java (1.2-4 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for pomegranate-clojure/1.2.1-3: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Implicit dependency: libcommons-logging-java commons-beanutils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommons-logging-java.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libfreemarker-java (2.3.31-2 to 2.3.32-1)
  • Migration status for libfreemarker-java (2.3.31-2 to 2.3.32-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfreemarker-java.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libgtk3-webkit2-perl (0.06-5 to 0.06-6)
  • Migration status for libgtk3-webkit2-perl (0.06-5 to 0.06-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgtk3-webkit2-perl.html
    • autopkgtest for libgtk3-webkit2-perl/0.06-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libjna-java (5.13.0-2 to 5.14.0-1)
  • Migration status for libjna-java (5.13.0-2 to 5.14.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjna-java.html
    • autopkgtest for libjna-java/5.14.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• liblangtag (0.6.4-2 to 0.6.7-1)
  • Migration status for liblangtag (0.6.4-2 to 0.6.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblangtag.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libmateweather (1.26.2-1 to 1.26.3-1)
  • Migration status for libmateweather (1.26.2-1 to 1.26.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmateweather.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libmceliece (0~20230612-2 to 0~20230612-3)
  • Migration status for libmceliece (0~20230612-2 to 0~20230612-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmceliece.html
    • autopkgtest for libmceliece/0~20230612-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libmd (1.1.0-1 to 1.1.0-2)
  • Migration status for libmd (1.1.0-1 to 1.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmd.html
    • autopkgtest for libmd/1.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libsidplayfp (2.5.1-1 to 2.6.0-1)
  • Migration status for libsidplayfp (2.5.1-1 to 2.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsidplayfp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libticables (1.3.6~git20230505.27586cc+dfsg-2 to 1.3.6~git20231126.f67c953+dfsg-1)
  • Migration status for libticables (1.3.6~git20230505.27586cc+dfsg-2 to 1.3.6~git20231126.f67c953+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libticables.html
    • autopkgtest for libticables/1.3.6~git20231126.f67c953+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libticalcs (1.1.10~git20230505.27586cc+dfsg-1 to 1.1.10~git20231126.f67c953+dfsg-1)
  • Migration status for libticalcs (1.1.10~git20230505.27586cc+dfsg-1 to 1.1.10~git20231126.f67c953+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libticalcs.html
    • autopkgtest for libticalcs/1.1.10~git20231126.f67c953+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libticonv (1.1.6~git20230505.27586cc-1 to 1.1.6~git20231126.f67c953-1)
  • Migration status for libticonv (1.1.6~git20230505.27586cc-1 to 1.1.6~git20231126.f67c953-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libticonv.html
    • autopkgtest for libticonv/1.1.6~git20231126.f67c953-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libtifiles (1.1.8~git20230505.27586cc-1 to 1.1.8~git20231126.f67c953-1)
  • Migration status for libtifiles (1.1.8~git20230505.27586cc-1 to 1.1.8~git20231126.f67c953-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtifiles.html
    • autopkgtest for libtifiles/1.1.8~git20231126.f67c953-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• loguru (0.6.0-3 to 0.7.2-3)
  • Migration status for loguru (0.6.0-3 to 0.7.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating loguru will fix bugs in testing: #1056421
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loguru.html
    • autopkgtest for loguru/0.7.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• lutris (0.5.14-1 to 0.5.14-2)
  • Migration status for lutris (0.5.14-1 to 0.5.14-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• mapproxy (2.0.0+dfsg-1 to 2.0.1+dfsg-1)
  • Migration status for mapproxy (2.0.0+dfsg-1 to 2.0.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mapproxy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mapsforge (0.17.0+dfsg.1-3 to 0.20.0-1)
  • Migration status for mapsforge (0.17.0+dfsg.1-3 to 0.20.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mapsforge.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• massxpert2 (- to 8.3.0-1)
  • Migration status for massxpert2 (- to 8.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by lopippo
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massxpert2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mate-media (1.26.0-2 to 1.26.2-1)
  • Migration status for mate-media (1.26.0-2 to 1.26.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-media.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mate-settings-daemon (1.26.0-2 to 1.26.1-1)
  • Migration status for mate-settings-daemon (1.26.0-2 to 1.26.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-settings-daemon.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mate-system-monitor (1.26.0-5 to 1.26.2-1)
  • Migration status for mate-system-monitor (1.26.0-5 to 1.26.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-system-monitor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mes (0.24.2-1 to 0.26-1)
  • Migration status for mes (0.24.2-1 to 0.26-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating mes will fix bugs in testing: #1058635
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mes.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• meta-plasma-mobile (3 to 4)
  • Migration status for meta-plasma-mobile (3 to 4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Depends: meta-plasma-mobile kalk
    • Depends: meta-plasma-mobile kclock
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-plasma-mobile.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mindthegap (2.3.0-2 to 2.3.0-3)
  • Migration status for mindthegap (2.3.0-2 to 2.3.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mindthegap.html
    • autopkgtest for mindthegap/2.3.0-3: amd64: Pass, arm64: Pass, ppc64el: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• multiqc (1.14+dfsg-1 to 1.14+dfsg-1.1)
  • Migration status for multiqc (1.14+dfsg-1 to 1.14+dfsg-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multiqc.html
    • autopkgtest for multiqc/1.14+dfsg-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• octave-iso2mesh (- to 1.9.6+ds-9)
  • Migration status for octave-iso2mesh (- to 1.9.6+ds-9): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-iso2mesh.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• octave-vibes (- to 0.2.0-9)
  • Migration status for octave-vibes (- to 0.2.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-vibes would introduce bugs in testing: #1057591
    • Not built on buildd: arch amd64 binaries uploaded by rafael
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-vibes.html
    • autopkgtest for octave-vibes/0.2.0-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• opensbi (1.3.1-1 to 1.4-1)
  • Migration status for opensbi (1.3.1-1 to 1.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensbi.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• orafce (4.7.0-1 to 4.9.0-1)
  • Migration status for orafce (4.7.0-1 to 4.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orafce.html
    • autopkgtest for orafce/4.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• orthanc (1.12.1+dfsg-4 to 1.12.2+dfsg-1)
  • Migration status for orthanc (1.12.1+dfsg-4 to 1.12.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc.html
    • autopkgtest for orthanc/1.12.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pcl (1.13.0+dfsg-3 to 1.13.0+dfsg-4)
  • Migration status for pcl (1.13.0+dfsg-3 to 1.13.0+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating pcl will fix bugs in testing: #1060105
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-codesniffer (3.7.1-2 to 3.7.2-2)
  • Migration status for php-codesniffer (3.7.1-2 to 3.7.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for php-codesniffer/3.7.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for php-phpseclib/2.0.46-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-codesniffer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-http-promise (1.2.1-1 to 1.3.0-1)
  • Migration status for php-http-promise (1.2.1-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-promise.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-phpstan-phpdoc-parser (1.24.5-1 to 1.25.0-1)
  • Migration status for php-phpstan-phpdoc-parser (1.24.5-1 to 1.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-phpstan-phpdoc-parser.html
    • autopkgtest for php-phpstan-phpdoc-parser/1.25.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• picom-conf (- to 0.17.0-1)
  • Migration status for picom-conf (- to 0.17.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): picom-conf qtilitools
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picom-conf.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• postgres-decoderbufs (2.4.0-1 to 2.5.0-1)
  • Migration status for postgres-decoderbufs (2.4.0-1 to 2.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgres-decoderbufs.html
    • autopkgtest for postgres-decoderbufs/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• postgresql-q3c (2.0.0-8 to 2.0.1-1)
  • Migration status for postgresql-q3c (2.0.0-8 to 2.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-q3c.html
    • autopkgtest for postgresql-q3c/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• praat (6.4.01+dfsg-2 to 6.4.03+dfsg-1)
  • Migration status for praat (6.4.01+dfsg-2 to 6.4.03+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/praat.html
    • autopkgtest for praat/6.4.03+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pulseaudio (16.1+dfsg1-2 to 16.1+dfsg1-3)
  • Migration status for pulseaudio (16.1+dfsg1-2 to 16.1+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for csound/1:6.18.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ffmpeg/7:6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for fluidsynth/2.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Test in progress, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for gnuais/0.3.3-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Test in progress, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for kappanhang/1.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for kworkflow/20191112-1.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for pulseaudio/16.1+dfsg1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for qemu/1:8.1.2+ds-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for sox/14.4.2+git20190427-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Depends: pulseaudio lirc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pulseaudio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pysvn (1.9.15-1 to 1.9.22-1)
  • Migration status for pysvn (1.9.15-1 to 1.9.22-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysvn.html
    • autopkgtest for pysvn/1.9.22-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-asn1 (- to 2.7.0-1)
  • Migration status for python-asn1 (- to 2.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asn1.html
    • autopkgtest for python-asn1/2.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-bioblend (1.2.0-1 to 1.2.0-2)
  • Migration status for python-bioblend (1.2.0-1 to 1.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bioblend.html
    • autopkgtest for python-bioblend/1.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-biom-format (2.1.15.2-1 to 2.1.15.2-2)
  • Migration status for python-biom-format (2.1.15.2-1 to 2.1.15.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-biom-format/2.1.15.2-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for q2-fragment-insertion/2023.7.0-1: amd64: Pass, arm64: Test in progress, ppc64el: Pass
    • autopkgtest for q2-quality-control/n/a: arm64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-biom-format.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-bitarray (2.8.1-1 to 2.9.2-1)
  • Migration status for python-bitarray (2.8.1-1 to 2.9.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bitarray.html
    • autopkgtest for python-bitarray/2.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-ci-info (0.2.0-2 to 0.3.0-1)
  • Migration status for python-ci-info (0.2.0-2 to 0.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating python-ci-info will fix bugs in testing: #1058120
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ci-info.html
    • autopkgtest for python-ci-info/0.3.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-cirpy (- to 1.0.2-1)
  • Migration status for python-cirpy (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cirpy.html
    • autopkgtest for python-cirpy/1.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-datacache (1.2.1-1 to 1.2.1-2)
  • Migration status for python-datacache (1.2.1-1 to 1.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-datacache.html
    • autopkgtest for python-datacache/1.2.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-django-channels (4.0.0-1 to 4.0.0-2)
  • Migration status for python-django-channels (4.0.0-1 to 4.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-channels.html
    • autopkgtest for python-django-channels/4.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-ecdsa (0.18.0-3 to 0.18.0-4)
  • Migration status for python-ecdsa (0.18.0-3 to 0.18.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ecdsa.html
    • autopkgtest for python-ecdsa/0.18.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-flasgger (0.9.7.2~dev2+dfsg-1 to 0.9.7.2~dev2+dfsg-2)
  • Migration status for python-flasgger (0.9.7.2~dev2+dfsg-1 to 0.9.7.2~dev2+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flasgger.html
    • autopkgtest for python-flasgger/0.9.7.2~dev2+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-openai (- to 1.6.1-1)
  • Migration status for python-openai (- to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by cdluminate@gmail.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-openai.html
    • autopkgtest for python-openai/1.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-pandas-flavor (- to 0.6.0-1)
  • Migration status for python-pandas-flavor (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): python-pandas-flavor python-xarray
    • Depends: python-pandas-flavor python-xarray
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pandas-flavor.html
    • autopkgtest for python-pandas-flavor/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-pulp (2.7.0+dfsg-1 to 2.7.0+dfsg-3)
  • Migration status for python-pulp (2.7.0+dfsg-1 to 2.7.0+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating python-pulp will fix bugs in testing: #1056493
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pulp.html
    • autopkgtest for python-pulp/2.7.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-pyaarlo (- to 0.8.0.2-1)
  • Migration status for python-pyaarlo (- to 0.8.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyaarlo.html
    • autopkgtest for python-pyaarlo/0.8.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-ring-doorbell (- to 0.8.5-1)
  • Migration status for python-ring-doorbell (- to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
    • Depends: python-ring-doorbell python-asyncclick
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ring-doorbell.html
    • autopkgtest for python-ring-doorbell/0.8.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• r-cran-ggeffects (1.3.2+dfsg-1 to 1.3.4+dfsg-1)
  • Migration status for r-cran-ggeffects (1.3.2+dfsg-1 to 1.3.4+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggeffects.html
    • autopkgtest for r-cran-ggeffects/1.3.4+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• requests-file (1.5.1-1 to 1.5.1-2)
  • Migration status for requests-file (1.5.1-1 to 1.5.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/requests-file.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-specinfra (2.87.0-2 to 2.87.2-1)
  • Migration status for ruby-specinfra (2.87.0-2 to 2.87.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-specinfra.html
    • autopkgtest for ruby-specinfra/2.87.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-addr2line (0.20.0-3 to 0.21.0-2)
  • Migration status for rust-addr2line (0.20.0-3 to 0.21.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-addr2line rust-fallible-iterator
    • Build-Depends(-Arch): rust-addr2line rust-gimli
    • Build-Depends(-Arch): rust-addr2line rust-object
    • Depends: rust-addr2line rust-fallible-iterator
    • Depends: rust-addr2line rust-gimli
    • Depends: rust-addr2line rust-object
    • Implicit dependency: rust-addr2line rust-backtrace
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-addr2line.html
    • autopkgtest for rust-addr2line/0.21.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-as-raw-xcb-connection (- to 1.0.1-1)
  • Migration status for rust-as-raw-xcb-connection (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by jamessan
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-as-raw-xcb-connection.html
    • autopkgtest for rust-as-raw-xcb-connection/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-backtrace (0.3.68-2 to 0.3.69-2)
  • Migration status for rust-backtrace (0.3.68-2 to 0.3.69-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-backtrace rust-addr2line
    • Build-Depends(-Arch): rust-backtrace rust-object
    • Depends: rust-backtrace rust-addr2line
    • Depends: rust-backtrace rust-object
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-backtrace.html
    • autopkgtest for rust-backtrace/0.3.69-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-circular (- to 0.3.0-1)
  • Migration status for rust-circular (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by holger
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-circular.html
    • autopkgtest for rust-circular/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-concat-idents (- to 1.1.4-1)
  • Migration status for rust-concat-idents (- to 1.1.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-concat-idents.html
    • autopkgtest for rust-concat-idents/1.1.4-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-elfx86exts (0.5.0-3 to 0.6.2-1)
  • Migration status for rust-elfx86exts (0.5.0-3 to 0.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-elfx86exts rust-object
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-elfx86exts.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-emojis (- to 0.6.1-1)
  • Migration status for rust-emojis (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-emojis.html
    • autopkgtest for rust-emojis/0.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-escargot (- to 0.5.8-1)
  • Migration status for rust-escargot (- to 0.5.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by holger
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-escargot.html
    • autopkgtest for rust-escargot/0.5.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-fallible-iterator (0.2.0-2 to 0.3.0-2)
  • Migration status for rust-fallible-iterator (0.2.0-2 to 0.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Implicit dependency: rust-fallible-iterator rust-addr2line
    • Implicit dependency: rust-fallible-iterator rust-framehop
    • Implicit dependency: rust-fallible-iterator rust-gimli
    • Implicit dependency: rust-fallible-iterator rust-postgres
    • Implicit dependency: rust-fallible-iterator rust-postgres-protocol
    • Implicit dependency: rust-fallible-iterator rust-postgres-types
    • Implicit dependency: rust-fallible-iterator rust-tokio-postgres
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fallible-iterator.html
    • autopkgtest for rust-fallible-iterator/0.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-framehop (0.7.1-1 to 0.7.2-1)
  • Migration status for rust-framehop (0.7.1-1 to 0.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-framehop rust-fallible-iterator
    • Build-Depends(-Arch): rust-framehop rust-gimli
    • Depends: rust-framehop rust-fallible-iterator
    • Depends: rust-framehop rust-gimli
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-framehop.html
    • autopkgtest for rust-framehop/0.7.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gdk-pixbuf (0.18.3-1 to 0.18.5-1)
  • Migration status for rust-gdk-pixbuf (0.18.3-1 to 0.18.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-gdk-pixbuf/0.18.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-gtk4/0.7.3-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-libshumate/0.4.1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk-pixbuf.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-gimli (0.27.3-1 to 0.28.1-2)
  • Migration status for rust-gimli (0.27.3-1 to 0.28.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gimli/0.28.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-wasmtime/10.0.1+dfsg-7: armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-gimli rust-fallible-iterator
    • Depends: rust-gimli rust-fallible-iterator
    • Implicit dependency: rust-gimli rust-addr2line
    • Implicit dependency: rust-gimli rust-wasmtime
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gimli.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-gix-prompt (- to 0.8.0-1)
  • Migration status for rust-gix-prompt (- to 0.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-prompt.html
    • autopkgtest for rust-gix-prompt/0.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gstreamer-gl-egl-sys (- to 0.21.2-1)
  • Migration status for rust-gstreamer-gl-egl-sys (- to 0.21.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-gstreamer-gl-egl-sys rust-gstreamer-gl-sys
    • Depends: rust-gstreamer-gl-egl-sys rust-gstreamer-gl-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-gl-egl-sys.html
    • autopkgtest for rust-gstreamer-gl-egl-sys/0.21.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gstreamer-gl-sys (- to 0.21.2-1)
  • Migration status for rust-gstreamer-gl-sys (- to 0.21.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-gstreamer-gl-sys/0.21.2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-gl-sys.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-gstreamer-gl-wayland-sys (- to 0.21.1-1)
  • Migration status for rust-gstreamer-gl-wayland-sys (- to 0.21.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-gstreamer-gl-wayland-sys rust-gstreamer-gl-sys
    • Depends: rust-gstreamer-gl-wayland-sys rust-gstreamer-gl-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-gl-wayland-sys.html
    • autopkgtest for rust-gstreamer-gl-wayland-sys/0.21.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gstreamer-gl-x11-sys (- to 0.21.1-1)
  • Migration status for rust-gstreamer-gl-x11-sys (- to 0.21.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-gstreamer-gl-x11-sys rust-gstreamer-gl-sys
    • Depends: rust-gstreamer-gl-x11-sys rust-gstreamer-gl-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-gl-x11-sys.html
    • autopkgtest for rust-gstreamer-gl-x11-sys/0.21.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-h3-quinn (- to 0.0.4-1)
  • Migration status for rust-h3-quinn (- to 0.0.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-h3-quinn rust-h3
    • Depends: rust-h3-quinn rust-h3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-h3-quinn.html
    • autopkgtest for rust-h3-quinn/0.0.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-lz4-sys (- to 1.9.4-1)
  • Migration status for rust-lz4-sys (- to 1.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by lolando
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lz4-sys.html
    • autopkgtest for rust-lz4-sys/1.9.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-object (0.31.1-1 to 0.32.2-1)
  • Migration status for rust-object (0.31.1-1 to 0.32.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-object rust-ruzstd
    • Depends: rust-object rust-ruzstd
    • Implicit dependency: rust-object rust-addr2line
    • Implicit dependency: rust-object rust-backtrace
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-object.html
    • autopkgtest for rust-object/0.32.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-pdb (- to 0.8.0-2)
  • Migration status for rust-pdb (- to 0.8.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-pdb rust-fallible-iterator
    • Depends: rust-pdb rust-fallible-iterator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pdb.html
    • autopkgtest for rust-pdb/0.8.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-postgres (0.19.4-1 to 0.19.7-1)
  • Migration status for rust-postgres (0.19.4-1 to 0.19.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-postgres rust-fallible-iterator
    • Depends: rust-postgres rust-fallible-iterator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-postgres.html
    • autopkgtest for rust-postgres/0.19.7-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-postgres-protocol (0.6.6-1 to 0.6.6-2)
  • Migration status for rust-postgres-protocol (0.6.6-1 to 0.6.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-postgres-protocol rust-fallible-iterator
    • Depends: rust-postgres-protocol rust-fallible-iterator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-postgres-protocol.html
    • autopkgtest for rust-postgres-protocol/0.6.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-postgres-types (0.2.6-1 to 0.2.6-2)
  • Migration status for rust-postgres-types (0.2.6-1 to 0.2.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-postgres-types rust-fallible-iterator
    • Depends: rust-postgres-types rust-fallible-iterator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-postgres-types.html
    • autopkgtest for rust-postgres-types/0.2.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-powerfmt (- to 0.2.0-1)
  • Migration status for rust-powerfmt (- to 0.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-powerfmt rust-powerfmt-macros
    • Depends: rust-powerfmt rust-powerfmt-macros
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-powerfmt.html
    • autopkgtest for rust-powerfmt/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-powerfmt-macros (- to 0.1.0-1)
  • Migration status for rust-powerfmt-macros (- to 0.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-powerfmt-macros.html
    • autopkgtest for rust-powerfmt-macros/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-repro-env (0.3.2-1 to 0.3.2-2)
  • Migration status for rust-repro-env (0.3.2-1 to 0.3.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-repro-env rust-ruzstd
    • Depends: rust-repro-env rust-ruzstd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-repro-env.html
    • autopkgtest for rust-repro-env/0.3.2-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-rhai-codegen (- to 1.6.0-1)
  • Migration status for rust-rhai-codegen (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by holger
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rhai-codegen.html
    • autopkgtest for rust-rhai-codegen/1.6.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-rockusb (- to 0.1.3-1)
  • Migration status for rust-rockusb (- to 0.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rockusb.html
    • autopkgtest for rust-rockusb/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-rustix-openpty (- to 0.1.1-1)
  • Migration status for rust-rustix-openpty (- to 0.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustix-openpty.html
    • autopkgtest for rust-rustix-openpty/0.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-ruzstd (0.4.0-2 to 0.5.0-1)
  • Migration status for rust-ruzstd (0.4.0-2 to 0.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Implicit dependency: rust-ruzstd rust-object
    • Implicit dependency: rust-ruzstd rust-repro-env
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ruzstd.html
    • autopkgtest for rust-ruzstd/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-str-stack (- to 0.1.0-1)
  • Migration status for rust-str-stack (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by holger
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-str-stack.html
    • autopkgtest for rust-str-stack/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-sys-locale (- to 0.3.1-1)
  • Migration status for rust-sys-locale (- to 0.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sys-locale.html
    • autopkgtest for rust-sys-locale/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-tester (- to 0.9.1-1)
  • Migration status for rust-tester (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by holger
    • Too young, only 1 of 2 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tester.html
    • autopkgtest for rust-tester/0.9.1-1: amd64: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-testing-logger (- to 0.1.1-1)
  • Migration status for rust-testing-logger (- to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by holger
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-testing-logger.html
    • autopkgtest for rust-testing-logger/0.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-tikv-jemalloc-sys (- to 0.5.4-1)
  • Migration status for rust-tikv-jemalloc-sys (- to 0.5.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tikv-jemalloc-sys.html
    • autopkgtest for rust-tikv-jemalloc-sys/0.5.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-tikv-jemallocator (- to 0.5.4-1)
  • Migration status for rust-tikv-jemallocator (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tikv-jemallocator/0.5.4-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-tikv-jemallocator rust-tikv-jemalloc-sys
    • Depends: rust-tikv-jemallocator rust-tikv-jemalloc-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tikv-jemallocator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-tokio-postgres (0.7.10-1 to 0.7.10-2)
  • Migration status for rust-tokio-postgres (0.7.10-1 to 0.7.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-tokio-postgres rust-fallible-iterator
    • Depends: rust-tokio-postgres rust-fallible-iterator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tokio-postgres.html
    • autopkgtest for rust-tokio-postgres/0.7.10-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-vsort (- to 0.2.0-1)
  • Migration status for rust-vsort (- to 0.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-vsort.html
    • autopkgtest for rust-vsort/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• simulide (0.1.7+dfsg-2 to 1.1.0.1909+dfsg-2)
  • Migration status for simulide (0.1.7+dfsg-2 to 1.1.0.1909+dfsg-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating simulide will fix bugs in testing: #1057603
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simulide.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• slowloris (- to 0.2.6+git20230430.890f72d-1)
  • Migration status for slowloris (- to 0.2.6+git20230430.890f72d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by francisco.ruviaro@riseup.net, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slowloris.html
    • autopkgtest for slowloris/0.2.6+git20230430.890f72d-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• socat (1.7.4.4-2 to 1.8.0.0-4)
  • Migration status for socat (1.7.4.4-2 to 1.8.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mariadb/1:10.11.6-1: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, s390x: Pass
    • autopkgtest for systemd/255.2-3: amd64: Test in progress, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socat.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sortable-tablesort.js (- to 3.1.0+ds-1)
  • Migration status for sortable-tablesort.js (- to 3.1.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sortable-tablesort.js.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• spaced (1.2.0-201605+dfsg-3 to 1.2.0-201605+dfsg-4)
  • Migration status for spaced (1.2.0-201605+dfsg-3 to 1.2.0-201605+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spaced.html
    • autopkgtest for spaced/1.2.0-201605+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• sqlalchemy (1.4.47+ds1-1 to 1.4.50+ds1-1)
  • Migration status for sqlalchemy (1.4.47+ds1-1 to 1.4.50+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for designate/1:17.0.0-2: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mistral/17.0.0-1: amd64: Pass, arm64: Test in progress, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for sphinx/7.2.6-3: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sqlalchemy/1.4.50+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlalchemy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• swaks (20201014.0-2 to 20240103.0-1)
  • Migration status for swaks (20201014.0-2 to 20240103.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for exim4/4.97-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for swaks/20240103.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swaks.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• swift-tools (- to 0.0.1)
  • Migration status for swift-tools (- to 0.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• swt4-gtk (4.26.0-1 to 4.26.0-2)
  • Migration status for swt4-gtk (4.26.0-1 to 4.26.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swt4-gtk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tilp2 (1.19~git20220826.71eaa92-1 to 1.19~git20231112.5a2ea63-1)
  • Migration status for tilp2 (1.19~git20220826.71eaa92-1 to 1.19~git20231112.5a2ea63-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tilp2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tinyxml2 (9.0.0+dfsg-3.1 to 10.0.0+dfsg-2)
  • Migration status for tinyxml2 (9.0.0+dfsg-3.1 to 10.0.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by hyperair
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinyxml2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• util-linux (2.39.3-2 to 2.39.3-6)
  • Migration status for util-linux (2.39.3-2 to 2.39.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for autopkgtest/5.31.2: amd64: Test in progress (will not be considered a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for dpdk/23.11-1: amd64: Ignored failure, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libdata-uuid-libuuid-perl/0.05-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for mmdebstrap/1.4.0-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for netplan.io/0.107-5: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for node-mqtt/4.3.7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for ostree/2023.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python3.11/3.11.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for systemd/255.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for util-linux/2.39.3-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/util-linux.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vlc-plugin-pipewire (3-2 to 3-3)
  • Migration status for vlc-plugin-pipewire (3-2 to 3-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlc-plugin-pipewire.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wireshark (4.2.0-1 to 4.2.2-1)
  • Migration status for wireshark (4.2.0-1 to 4.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wireshark.html
    • autopkgtest for wireshark/4.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• wlrctl (- to 0.2.2-1)
  • Migration status for wlrctl (- to 0.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlrctl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xmake (2.8.6+ds-1 to 2.8.6+ds-2)
  • Migration status for xmake (2.8.6+ds-1 to 2.8.6+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmake.html
    • autopkgtest for xmake/2.8.6+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• xphyle (4.4.1-3 to 4.4.4-1)
  • Migration status for xphyle (4.4.1-3 to 4.4.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): xphyle pep517
  • Additional info:
    • Updating xphyle will fix bugs in testing: #1058448
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xphyle.html
    • autopkgtest for xphyle/4.4.4-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zigpy (0.60.2-1 to 0.60.4-1)
  • Migration status for zigpy (0.60.2-1 to 0.60.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zigpy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zzzeeksphinx (1.4.0-1 to 1.4.0-2)
  • Migration status for zzzeeksphinx (1.4.0-1 to 1.4.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zzzeeksphinx.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• androguard (3.4.0~a1-7 to 3.4.0~a1-8)
  • Migration status for androguard (3.4.0~a1-7 to 3.4.0~a1-8): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/androguard.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• annexremote (1.6.0-1 to 1.6.4-2)
  • Migration status for annexremote (1.6.0-1 to 1.6.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating annexremote will fix bugs in testing: #1058105
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/annexremote.html
    • autopkgtest for annexremote/1.6.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• base-installer (1.216 to 1.217)
  • Migration status for base-installer (1.216 to 1.217): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bepasty (1.1.0-1 to 1.2.0-1)
  • Migration status for bepasty (1.1.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bepasty/1.2.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bepasty.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bibtexparser (1.1.0+ds-5.1 to 1.1.0+ds-5.2)
  • Migration status for bibtexparser (1.1.0+ds-5.1 to 1.1.0+ds-5.2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bibtexparser.html
    • autopkgtest for bibtexparser/1.1.0+ds-5.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• bifrost (- to 1.3.1-1)
  • Migration status for bifrost (- to 1.3.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bifrost.html
    • autopkgtest for bifrost/1.3.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• blessings (1.7-1 to 1.7-2)
  • Migration status for blessings (1.7-1 to 1.7-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blessings.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bluez-firmware (1.2-9 to 1.2-11)
  • Migration status for bluez-firmware (1.2-9 to 1.2-11): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• bolt (- to 0.9.6-2)
  • Migration status for bolt (- to 0.9.6-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bolt.html
    • autopkgtest for bolt/0.9.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• bzip3 (1.3.2-1 to 1.4.0-1)
  • Migration status for bzip3 (1.3.2-1 to 1.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bzip3.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• calibre (7.2.0+ds-1 to 7.3.0+ds-1)
  • Migration status for calibre (7.2.0+ds-1 to 7.3.0+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calibre.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for calibre/7.3.0+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ccid (1.5.4-1 to 1.5.5-1)
  • Migration status for ccid (1.5.4-1 to 1.5.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccid.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cdebconf-entropy (0.52 to 0.53)
  • Migration status for cdebconf-entropy (0.52 to 0.53): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cdo (2.3.0-1 to 2.3.0-2)
  • Migration status for cdo (2.3.0-1 to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): cdo -> patchelf/0.14.3-1+b1/mips64el
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): cdo eccodes
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdo.html
    • autopkgtest for cdo/2.3.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cfgrib (- to 0.9.10.4-3)
  • Migration status for cfgrib (- to 0.9.10.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cfgrib would introduce bugs in testing: #1055848
    • autopkgtest for cfgrib/0.9.10.4-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , ppc64el: Regression or new test ♻
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): cfgrib eccodes
    • Build-Depends(-Arch): cfgrib python-xarray
    • Depends: cfgrib eccodes
    • Depends: cfgrib python-xarray
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cfgrib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cherrypy3 (18.9.0-1 to 18.9.0-2)
  • Migration status for cherrypy3 (18.9.0-1 to 18.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cherrypy3/18.9.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for sabnzbdplus/4.1.0+dfsg-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cherrypy3.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• choqok (1.7.0-1 to 1.7.0-2)
  • Migration status for choqok (1.7.0-1 to 1.7.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/choqok.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• civicrm (5.53.0+dfsg1-1 to 5.68.1+dfsg1-1)
  • Migration status for civicrm (5.53.0+dfsg1-1 to 5.68.1+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/civicrm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• codraft (- to 2.2.1-3)
  • Migration status for codraft (- to 2.2.1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codraft.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for codraft/2.2.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• colord (1.4.6-4 to 1.4.6-5)
  • Migration status for colord (1.4.6-4 to 1.4.6-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/colord.html
    • autopkgtest for colord/1.4.6-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• dask.distributed (2023.8.0+ds.1-1 to 2023.12.1+ds-3)
  • Migration status for dask.distributed (2023.8.0+ds.1-1 to 2023.12.1+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): dask.distributed dask
    • Build-Depends(-Arch): dask.distributed jupyter-server
    • Depends: dask.distributed dask
  • Additional info:
    • Updating dask.distributed will fix bugs in testing: #1057950
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dask.distributed.html
    • autopkgtest for dask.distributed/2023.12.1+ds-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• davmail (6.2.0.3464-1 to 6.2.1.3496-1)
  • Migration status for davmail (6.2.0.3464-1 to 6.2.1.3496-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/davmail.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for davmail/6.2.1.3496-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• debootstrap (1.0.133 to 1.0.134)
  • Migration status for debootstrap (1.0.133 to 1.0.134): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debootstrap.html
    • autopkgtest for debootstrap/1.0.134: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• dh-fortran-mod (0.32 to 0.33)
  • Migration status for dh-fortran-mod (0.32 to 0.33): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-fortran-mod.html
    • autopkgtest for dh-fortran-mod/0.33: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• fdb (5.11.94-1 to 5.11.98-1)
  • Migration status for fdb (5.11.94-1 to 5.11.98-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): fdb eccodes
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flask-dance (7.0.0-1 to 7.0.1-1)
  • Migration status for flask-dance (7.0.0-1 to 7.0.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating flask-dance will fix bugs in testing: #1060020
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-dance.html
    • autopkgtest for flask-dance/7.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• fpc (3.2.2+dfsg-23 to 3.2.2+dfsg-32)
  • Migration status for fpc (3.2.2+dfsg-23 to 3.2.2+dfsg-32): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fpc.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for fpc/3.2.2+dfsg-32: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• gambas3 (3.18.4-2 to 3.18.4-3)
  • Migration status for gambas3 (3.18.4-2 to 3.18.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gambas3.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gdnsd (3.8.1-2 to 3.8.2-1)
  • Migration status for gdnsd (3.8.1-2 to 3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdnsd.html
    • autopkgtest for gdnsd/3.8.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• glab (1.33.0-1 to 1.36.0-1)
  • Migration status for glab (1.33.0-1 to 1.36.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): glab golang-k8s-client-go (not considered)
    • Built-Using: glab golang-k8s-client-go (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Build-Depends(-Arch): glab golang-github-xanzy-go-gitlab
    • Build-Depends(-Arch): glab golang-k8s-apimachinery
    • Built-Using: glab golang-github-xanzy-go-gitlab
    • Built-Using: glab golang-golang-x-oauth2
    • Built-Using: glab golang-k8s-apimachinery
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glab.html
    • autopkgtest for glab/1.36.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• glibc-doc-reference (2.37-1 to 2.38-1)
  • Migration status for glibc-doc-reference (2.37-1 to 2.38-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• golang-github-emersion-go-pgpmail (0.2.0-2 to 0.2.1-1)
  • Migration status for golang-github-emersion-go-pgpmail (0.2.0-2 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-emersion-go-pgpmail.html
    • autopkgtest for golang-github-emersion-go-pgpmail/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-xanzy-go-gitlab (0.90.0-1 to 0.94.0-1)
  • Migration status for golang-github-xanzy-go-gitlab (0.90.0-1 to 0.94.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-xanzy-go-gitlab.html
    • autopkgtest for golang-github-xanzy-go-gitlab/0.94.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-google-api (0.61.0-1 to 0.61.0-4)
  • Migration status for golang-google-api (0.61.0-1 to 0.61.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating golang-google-api will fix bugs in testing: #1058532
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-google-api.html
    • autopkgtest for golang-google-api/0.61.0-4: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• grep (3.11-3 to 3.11-4)
  • Migration status for grep (3.11-3 to 3.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dpdk/23.11-1: amd64: Ignored failure, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for grep/3.11-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for haveged/1.9.14-1: amd64: Failed (not a regression), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for util-linux/2.39.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grep.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• grub-installer (1.197 to 1.198)
  • Migration status for grub-installer (1.197 to 1.198): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gst-omx (1.22.7-1 to 1.22.8-1)
  • Migration status for gst-omx (1.22.7-1 to 1.22.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gst-omx.html
    • autopkgtest for gst-omx/1.22.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• haskell-simple-sendfile (0.2.32-1 to 0.2.32-2)
  • Migration status for haskell-simple-sendfile (0.2.32-1 to 0.2.32-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-simple-sendfile-dev/0.2.32-2/amd64 to testing makes libghc-warp-dev/3.3.25-1/amd64 uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/amd64 to testing makes libghc-warp-prof/3.3.25-1/amd64 uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/arm64 to testing makes libghc-warp-dev/3.3.25-1/arm64 uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/arm64 to testing makes libghc-warp-prof/3.3.25-1/arm64 uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/armel to testing makes libghc-warp-dev/3.3.25-1/armel uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/armel to testing makes libghc-warp-prof/3.3.25-1/armel uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/armhf to testing makes libghc-warp-dev/3.3.25-1/armhf uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/armhf to testing makes libghc-warp-prof/3.3.25-1/armhf uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/i386 to testing makes libghc-warp-dev/3.3.25-1/i386 uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/i386 to testing makes libghc-warp-prof/3.3.25-1/i386 uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/mips64el to testing makes libghc-warp-dev/3.3.25-1/mips64el uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/mips64el to testing makes libghc-warp-prof/3.3.25-1/mips64el uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/ppc64el to testing makes libghc-warp-dev/3.3.25-1/ppc64el uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/ppc64el to testing makes libghc-warp-prof/3.3.25-1/ppc64el uninstallable
    • migrating libghc-simple-sendfile-dev/0.2.32-2/s390x to testing makes libghc-warp-dev/3.3.25-1/s390x uninstallable
    • migrating libghc-simple-sendfile-prof/0.2.32-2/s390x to testing makes libghc-warp-prof/3.3.25-1/s390x uninstallable
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-simple-sendfile.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-snap-templates (- to 1.0.0.2-5)
  • Migration status for haskell-snap-templates (- to 1.0.0.2-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-snap-templates.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hasktags (- to 0.72.0-2)
  • Migration status for hasktags (- to 0.72.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hasktags.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hwdata (0.377-2-1 to 0.378-1)
  • Migration status for hwdata (0.377-2-1 to 0.378-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hwdata.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• inn (1:1.7.2q-48 to 1:1.7.2q-49)
  • Migration status for inn (1:1.7.2q-48 to 1:1.7.2q-49): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/inn.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• intake (- to 0.6.6-3)
  • Migration status for intake (- to 0.6.6-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on ppc64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for intake/0.6.6-3: arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kmod (30+20230601-2.1 to 31-1)
  • Migration status for kmod (30+20230601-2.1 to 31-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmod.html
    • autopkgtest for dkms/3.0.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kraptor (0.0.20040403+ds-2 to 0.0.20040403+ds-3)
  • Migration status for kraptor (0.0.20040403+ds-2 to 0.0.20040403+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kraptor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lexicon (3.11.7-1 to 3.11.7-2)
  • Migration status for lexicon (3.11.7-1 to 3.11.7-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lexicon.html
    • autopkgtest for lexicon/3.11.7-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libcgi-application-plugin-authentication-perl (- to 0.23+~cs0.5-4)
  • Migration status for libcgi-application-plugin-authentication-perl (- to 0.23+~cs0.5-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcgi-application-plugin-authentication-perl.html
    • autopkgtest for libcgi-application-plugin-authentication-perl/0.23+~cs0.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libseccomp (2.5.4-2 to 2.5.5-1)
  • Migration status for libseccomp (2.5.4-2 to 2.5.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libseccomp.html
    • autopkgtest for libseccomp/2.5.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libspreadsheet-parsexlsx-perl (0.27-3 to 0.29-1)
  • Migration status for libspreadsheet-parsexlsx-perl (0.27-3 to 0.29-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libspreadsheet-parsexlsx-perl.html
    • autopkgtest for libspreadsheet-parsexlsx-perl/0.29-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libthai (0.1.29-1 to 0.1.29-2)
  • Migration status for libthai (0.1.29-1 to 0.1.29-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libthai.html
    • autopkgtest for libthai/0.1.29-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• logrotate (3.21.0-1 to 3.21.0-2)
  • Migration status for logrotate (3.21.0-1 to 3.21.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for logrotate/3.21.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for swift/2.32.0-2: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/logrotate.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lomiri-thumbnailer (3.0.2-2 to 3.0.2-3)
  • Migration status for lomiri-thumbnailer (3.0.2-2 to 3.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating lomiri-thumbnailer will fix bugs in testing: #1059174
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-thumbnailer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mariadb (1:10.11.6-1 to 1:10.11.6-2)
  • Migration status for mariadb (1:10.11.6-1 to 1:10.11.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for isc-kea/2.4.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libreoffice/4:7.6.4~rc1-1: amd64: Pass, arm64: Test in progress, armhf: Pass
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for mariadb/1:10.11.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress, s390x: Pass
    • autopkgtest for w1retap/1.4.6-1.1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mariadb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• media-retriever (1.57 to 1.58)
  • Migration status for media-retriever (1.57 to 1.58): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mediawiki2latex (7.52-1 to 8.0-1)
  • Migration status for mediawiki2latex (7.52-1 to 8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki2latex.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mesa (23.2.1-1 to 23.3.2-2)
  • Migration status for mesa (23.2.1-1 to 23.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mesa unsatisfiable Build-Depends(-Arch) on mips64el: llvm-17-dev [amd64 arm64 armel armhf i386 loong64 mips64el powerpc ppc64 ppc64el riscv64 s390x sparc64 x32]
    • mesa unsatisfiable Build-Depends(-Arch) on mips64el: libclang-17-dev [amd64 arm64 armel armhf i386 loong64 mips64el powerpc ppc64 ppc64el riscv64 s390x sparc64 x32]
    • mesa unsatisfiable Build-Depends(-Arch) on mips64el: libclang-cpp17-dev [amd64 arm64 armel armhf i386 loong64 mips64el powerpc ppc64 ppc64el riscv64 s390x sparc64 x32]
    • mesa unsatisfiable Build-Depends(-Arch) on mips64el: llvm-spirv-17 [amd64 arm64 armel armhf i386 loong64 mips64el powerpc ppc64 ppc64el riscv64 s390x x32]
    • mesa unsatisfiable Build-Depends(-Arch) on mips64el: libllvmspirvlib-17-dev [amd64 arm64 armel armhf i386 loong64 mips64el powerpc ppc64 ppc64el riscv64 s390x x32]
    • missing build on armel
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for forge/1.0.1-3: amd64: Pass, arm64: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mesa/23.3.2-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating mesa will fix bugs in testing: #1058405
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mesa.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
• mpc (0.34-1 to 0.35-1)
  • Migration status for mpc (0.34-1 to 0.35-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• msolve (0.6.1-1 to 0.6.3-2)
  • Migration status for msolve (0.6.1-1 to 0.6.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: msolve flint
  • Additional info:
    • Updating msolve will fix bugs in testing: #1058557
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msolve.html
    • autopkgtest for msolve/0.6.3-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• multipath-tools (0.9.4-7 to 0.9.7-2)
  • Migration status for multipath-tools (0.9.4-7 to 0.9.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for multipath-tools/0.9.7-2: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multipath-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mwrap (1.1.1-1 to 1.1.1-2)
  • Migration status for mwrap (1.1.1-1 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mwrap.html
    • autopkgtest for mwrap/1.1.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• network-console (1.93 to 1.94)
  • Migration status for network-console (1.93 to 1.94): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nihstro (- to 0.0~git20211107.e924e21-2)
  • Migration status for nihstro (- to 0.0~git20211107.e924e21-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nihstro.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-help-me (4.2.0-1 to 5.0.0-1)
  • Migration status for node-help-me (4.2.0-1 to 5.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-help-me.html
    • autopkgtest for node-help-me/5.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• node-js-sdsl (4.1.4-2 to 4.1.4-3)
  • Migration status for node-js-sdsl (4.1.4-2 to 4.1.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 7 days old
  • Additional info:
    • Updating node-js-sdsl will fix bugs in testing: #1058553
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-js-sdsl.html
    • autopkgtest for node-js-sdsl/4.1.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• orthanc-dicomweb (1.15+dfsg-2 to 1.16+dfsg-1)
  • Migration status for orthanc-dicomweb (1.15+dfsg-2 to 1.16+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-dicomweb.html
    • autopkgtest for orthanc-dicomweb/1.16+dfsg-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• orthanc-gdcm (1.5-1 to 1.6+dfsg-1)
  • Migration status for orthanc-gdcm (1.5-1 to 1.6+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-gdcm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• partman-auto-crypto (35 to 36)
  • Migration status for partman-auto-crypto (35 to 36): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• partman-auto-raid (51 to 52)
  • Migration status for partman-auto-raid (51 to 52): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• partman-crypto (121 to 122)
  • Migration status for partman-crypto (121 to 122): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• partman-iscsi (76 to 77)
  • Migration status for partman-iscsi (76 to 77): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• partman-partitioning (150 to 151)
  • Migration status for partman-partitioning (150 to 151): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• petsc4py (3.18.5-1 to 3.19.6-3)
  • Migration status for petsc4py (3.18.5-1 to 3.19.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for fenics-dolfinx/1:0.7.2-2: arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for petsc4py/3.19.6-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): petsc4py petsc
    • Depends: petsc4py petsc
    • Implicit dependency: petsc4py dolfin
    • Implicit dependency: petsc4py fenics-dolfinx
    • Implicit dependency: petsc4py slepc4py
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petsc4py.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• phosh-mobile-settings (0.34.0-1 to 0.35.0-1)
  • Migration status for phosh-mobile-settings (0.34.0-1 to 0.35.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phosh-mobile-settings.html
    • autopkgtest for phosh-mobile-settings/0.35.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• phosh-osk-stub (0.34.0-1 to 0.35.0-1)
  • Migration status for phosh-osk-stub (0.34.0-1 to 0.35.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phosh-osk-stub.html
    • autopkgtest for phosh-osk-stub/0.35.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pipewire (1.0.0-1 to 1.0.0-3)
  • Migration status for pipewire (1.0.0-1 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pipewire.html
    • autopkgtest for pipewire/1.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pokrok (0.2.0-4 to 0.2.0-5)
  • Migration status for pokrok (0.2.0-4 to 0.2.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating pokrok will fix bugs in testing: #1058108
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pokrok.html
    • autopkgtest for pokrok/0.2.0-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pspp (1.6.2-2 to 2.0.0-3)
  • Migration status for pspp (1.6.2-2 to 2.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: pspp spread-sheet-widget
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pspp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pv (1.8.0-3 to 1.8.5-2)
  • Migration status for pv (1.8.0-3 to 1.8.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating pv will fix bugs in testing: #1059222
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pv.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pygresql (1:5.1.2-2 to 1:6.0-1)
  • Migration status for pygresql (1:5.1.2-2 to 1:6.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pygresql.html
    • autopkgtest for pygresql/1:6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pykeepass (4.0.6-1 to 4.0.6-2)
  • Migration status for pykeepass (4.0.6-1 to 4.0.6-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pykeepass.html
    • autopkgtest for pykeepass/4.0.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pylast (4.1.0-2 to 5.2.0-1)
  • Migration status for pylast (4.1.0-2 to 5.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pylast.html
    • autopkgtest for pylast/5.2.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-absl (0.15.0-2 to 2.0.0-1)
  • Migration status for python-absl (0.15.0-2 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-absl/2.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-ml-collections/0.1.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-absl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-dnslib (0.9.23-1 to 0.9.24-1)
  • Migration status for python-dnslib (0.9.23-1 to 0.9.24-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dnslib.html
    • autopkgtest for python-dnslib/0.9.24-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-exchangelib (5.1.0-1 to 5.1.0-2)
  • Migration status for python-exchangelib (5.1.0-1 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-exchangelib.html
    • autopkgtest for python-exchangelib/5.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-geopandas (0.14.1-1 to 0.14.2-1)
  • Migration status for python-geopandas (0.14.1-1 to 0.14.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-geopandas.html
    • autopkgtest for python-geopandas/0.14.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-internetarchive (3.3.0-1 to 3.5.0-1)
  • Migration status for python-internetarchive (3.3.0-1 to 3.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-internetarchive.html
    • autopkgtest for python-internetarchive/3.5.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-laspy (2.5.1-3 to 2.5.2-1)
  • Migration status for python-laspy (2.5.1-3 to 2.5.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-laspy.html
    • autopkgtest for python-laspy/2.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-libusb1 (2.0.1-0.1 to 2.0.1+ds-1)
  • Migration status for python-libusb1 (2.0.1-0.1 to 2.0.1+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating python-libusb1 will fix bugs in testing: #1058093
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libusb1.html
    • autopkgtest for python-libusb1/2.0.1+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-mechanicalsoup (- to 1.3.0-1)
  • Migration status for python-mechanicalsoup (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-mechanicalsoup/1.3.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mechanicalsoup.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-telegram-bot (13.15-1 to 20.7-1)
  • Migration status for python-telegram-bot (13.15-1 to 20.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-telegram-bot.html
    • autopkgtest for python-telegram-bot/20.7-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-tenacity (8.2.1-1 to 8.2.3-2)
  • Migration status for python-tenacity (8.2.1-1 to 8.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ceilometer/blocked-on-ci-infra: i386: Ignored failure
    • autopkgtest for designate/1:17.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-tenacity/8.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends-Indep: python-tenacity python-typeguard
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tenacity.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-urwidtrees (1.0.3.dev0-2 to 1.0.3.dev0-3)
  • Migration status for python-urwidtrees (1.0.3.dev0-2 to 1.0.3.dev0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-urwidtrees.html
    • autopkgtest for python-urwidtrees/1.0.3.dev0-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qemu (1:8.1.2+ds-1 to 1:8.2.0+ds-4)
  • Migration status for qemu (1:8.1.2+ds-1 to 1:8.2.0+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debvm/0.2.13: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for qemu/1:8.2.0+ds-4: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for sbuild/0.85.4: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for systemd/255.2-3: amd64: Test in progress, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rescue (1.93 to 1.94)
  • Migration status for rescue (1.93 to 1.94): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rhythmbox (3.4.7-1 to 3.4.7-2)
  • Migration status for rhythmbox (3.4.7-1 to 3.4.7-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: rhythmbox lirc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rhythmbox.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• robber (1.1.5-2 to 1.1.5-3)
  • Migration status for robber (1.1.5-2 to 1.1.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/robber.html
    • autopkgtest for robber/1.1.5-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ros-class-loader (2.6.0-1 to 2.7.0-1)
  • Migration status for ros-class-loader (2.6.0-1 to 2.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros-class-loader.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-google-cloud-core (1.2.0-2 to 1.6.1-1)
  • Migration status for ruby-google-cloud-core (1.2.0-2 to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by abhijith@openmailbox.org, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-google-cloud-core.html
    • autopkgtest for ruby-google-cloud-core/1.6.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-askama (- to 0.12.1-2)
  • Migration status for rust-askama (- to 0.12.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: rust-askama rust-comrak
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-askama.html
    • autopkgtest for rust-askama/0.12.1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-comrak (- to 0.20.0-2)
  • Migration status for rust-comrak (- to 0.20.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-comrak would introduce bugs in testing: #1057056
    • Too young, only 2 of 5 days old
    • Depends: rust-comrak rust-emojis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-comrak.html
    • autopkgtest for rust-comrak/0.20.0-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-eza (- to 0.17.0-1)
  • Migration status for rust-eza (- to 0.17.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-eza rust-timeago (not considered)
    • Depends: rust-eza rust-timeago (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-eza rust-percent-encoding
    • Depends: rust-eza rust-percent-encoding
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-eza.html
    • autopkgtest for rust-eza/0.17.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-percent-encoding (2.3.0-1 to 2.3.1-1)
  • Migration status for rust-percent-encoding (2.3.0-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-percent-encoding.html
    • autopkgtest for rust-percent-encoding/2.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-rstest-test (- to 0.11.0-2)
  • Migration status for rust-rstest-test (- to 0.11.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rstest-test.html
    • autopkgtest for rust-rstest-test/0.11.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-zoxide (0.4.3-6 to 0.9.2-1)
  • Migration status for rust-zoxide (0.4.3-6 to 0.9.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-zoxide rust-askama
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zoxide.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• slepc (3.18.3+dfsg1-1 to 3.19.2+dfsg1-2)
  • Migration status for slepc (3.18.3+dfsg1-1 to 3.19.2+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for fenics-dolfinx/1:0.7.2-2: arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for slepc/3.19.2+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): slepc petsc
    • Depends: slepc petsc
    • Implicit dependency: slepc dolfin
    • Implicit dependency: slepc fenics-dolfinx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slepc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sqlmap (1.7.12-1 to 1.8-1)
  • Migration status for sqlmap (1.7.12-1 to 1.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlmap.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• strawberry (1.0.22-1 to 1.0.22-2)
  • Migration status for strawberry (1.0.22-1 to 1.0.22-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/strawberry.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• stress-ng (0.17.03-2 to 0.17.04-1)
  • Migration status for stress-ng (0.17.03-2 to 0.17.04-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stress-ng.html
    • autopkgtest for stress-ng/0.17.04-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• switcheroo-control (2.6-1 to 2.6-2)
  • Migration status for switcheroo-control (2.6-1 to 2.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/switcheroo-control.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• typecatcher (0.3-1.2 to 0.4-0.1)
  • Migration status for typecatcher (0.3-1.2 to 0.4-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/typecatcher.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tzsetup (1:0.122 to 1:0.123)
  • Migration status for tzsetup (1:0.122 to 1:0.123): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• usbutils (1:015-1 to 1:017-3)
  • Migration status for usbutils (1:015-1 to 1:017-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for umockdev/0.17.18-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/usbutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• user-setup (1.95 to 1.96)
  • Migration status for user-setup (1.95 to 1.96): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/user-setup.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xcb-imdkit (1.0.5-1 to 1.0.6-1)
  • Migration status for xcb-imdkit (1.0.5-1 to 1.0.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb-imdkit.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xsar (- to 2023.09.0-2)
  • Migration status for xsar (- to 2023.09.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xsar python-xarray (not considered)
    • Depends: xsar python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xsar xarray-datatree
    • Build-Depends(-Arch): xsar xarray-safe-rcm
    • Build-Depends(-Arch): xsar xarray-safe-s1
    • Build-Depends(-Arch): xsar xradarsat2
    • Depends: xsar python-rioxarray
    • Depends: xsar xarray-datatree
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsar.html
    • autopkgtest for xsar/2023.09.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• yoyo (8.2.0+dfsg1-1 to 8.2.0+dfsg1-2)
  • Migration status for yoyo (8.2.0+dfsg1-1 to 8.2.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yoyo.html
    • autopkgtest for yoyo/8.2.0+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• zipl-installer (0.0.46 to 0.0.47)
  • Migration status for zipl-installer (0.0.46 to 0.0.47): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• alsa-ucm-conf-asahi (4-1 to 5-1)
  • Migration status for alsa-ucm-conf-asahi (4-1 to 5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alsa-ucm-conf-asahi.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• apvlv (0.5.0+repack-1 to 0.5.0+repack-2)
  • Migration status for apvlv (0.5.0+repack-1 to 0.5.0+repack-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apvlv.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bcachefs-tools (24+really1.3.4-1 to 24+really1.3.4-2)
  • Migration status for bcachefs-tools (24+really1.3.4-1 to 24+really1.3.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bcachefs-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• benchmark (1.7.1-1 to 1.8.3-3)
  • Migration status for benchmark (1.7.1-1 to 1.8.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for benchmark/1.8.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytorch/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pytorch-cuda/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for ros2-ament-cmake/2.3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating benchmark will fix bugs in testing: #1056202
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/benchmark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bino (- to 2.1-1)
  • Migration status for bino (- to 2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bino.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• birdfont (2.33.1-2 to 2.33.1-3)
  • Migration status for birdfont (2.33.1-2 to 2.33.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/birdfont.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• chromium (120.0.6099.129-1 to 120.0.6099.199-1)
  • Migration status for chromium (120.0.6099.129-1 to 120.0.6099.199-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sabnzbdplus/4.1.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromium.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 3 days old (needed 2 days)
• dask (2023.8.0+dfsg-2 to 2023.12.1+dfsg-2)
  • Migration status for dask (2023.8.0+dfsg-2 to 2023.12.1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): dask dask.distributed
  • Additional info:
    • Updating dask will fix bugs in testing: #1056239
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dask.html
    • autopkgtest for dask/2023.12.1+dfsg-2: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debian-multimedia (- to 0.11)
  • Migration status for debian-multimedia (- to 0.11): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-multimedia.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• debianutils (5.14 to 5.16)
  • Migration status for debianutils (5.14 to 5.16): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for debianutils/5.16: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for thunderbird/1:115.6.0-1: amd64: Pass, arm64: Pass, i386: Test in progress, s390x: Pass
    • autopkgtest for thunderbird/blocked-on-ci-infra: ppc64el: Ignored failure
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debianutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dolfin (2019.2.0~legacy20230609.8b85e9d.ar-5 to 2019.2.0~legacy20230609.8b85e9d.ar-8)
  • Migration status for dolfin (2019.2.0~legacy20230609.8b85e9d.ar-5 to 2019.2.0~legacy20230609.8b85e9d.ar-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dolfin slepc (not considered)
    • Invalidated by dependency
    • Depends: dolfin petsc
    • Depends: dolfin petsc4py
    • Depends: dolfin slepc4py
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolfin.html
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• e17 (0.25.4-2 to 0.26.0-2)
  • Migration status for e17 (0.25.4-2 to 0.26.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): e17 efl
    • Depends: e17 efl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/e17.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• extrepo-data (1.0.3 to 1.0.4)
  • Migration status for extrepo-data (1.0.3 to 1.0.4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extrepo-data.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fenics-dolfinx (1:0.7.2-2 to 1:0.7.3-3)
  • Migration status for fenics-dolfinx (1:0.7.2-2 to 1:0.7.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfinx-mpc/0.7.0.post1-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for fenics-dolfinx/1:0.7.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
    • Depends: fenics-dolfinx petsc
    • Depends: fenics-dolfinx petsc4py
    • Depends: fenics-dolfinx slepc
    • Depends: fenics-dolfinx slepc4py
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics-dolfinx.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fonts-spleen (2.0.1-1 to 2.0.2-1)
  • Migration status for fonts-spleen (2.0.1-1 to 2.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-spleen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-power-manager (43.0-1 to 43.0-2)
  • Migration status for gnome-power-manager (43.0-1 to 43.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-power-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-lucas-clemente-quic-go (0.37.4-1 to 0.38.2-1)
  • Migration status for golang-github-lucas-clemente-quic-go (0.37.4-1 to 0.38.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-lucas-clemente-quic-go.html
    • autopkgtest for golang-github-lucas-clemente-quic-go/0.38.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gravitation (3+dfsg1-5 to 3+dfsg1-6)
  • Migration status for gravitation (3+dfsg1-5 to 3+dfsg1-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gravitation.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• grimripper (3.0.2-2 to 3.0.2-3)
  • Migration status for grimripper (3.0.2-2 to 3.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grimripper.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gtextfsm (1.1.0-3 to 1.1.3-1)
  • Migration status for gtextfsm (1.1.0-3 to 1.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtextfsm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-pandoc (3.0.1-4 to 3.1.3-1)
  • Migration status for haskell-pandoc (3.0.1-4 to 3.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-pandoc haskell-typst
    • Build-Depends-Indep: haskell-pandoc haskell-typst
    • Depends: haskell-pandoc haskell-typst
    • Implicit dependency: haskell-pandoc gitit/amd64
    • Implicit dependency: haskell-pandoc gitit/arm64
    • Implicit dependency: haskell-pandoc gitit/armel
    • Implicit dependency: haskell-pandoc gitit/armhf
    • Implicit dependency: haskell-pandoc gitit/i386
    • Implicit dependency: haskell-pandoc gitit/mips64el
    • Implicit dependency: haskell-pandoc gitit/ppc64el
    • Implicit dependency: haskell-pandoc gitit/s390x
    • Implicit dependency: haskell-pandoc haskell-hakyll/amd64
    • Implicit dependency: haskell-pandoc haskell-hakyll/arm64
    • Implicit dependency: haskell-pandoc haskell-hakyll/armel
    • Implicit dependency: haskell-pandoc haskell-hakyll/armhf
    • Implicit dependency: haskell-pandoc haskell-hakyll/i386
    • Implicit dependency: haskell-pandoc haskell-hakyll/mips64el
    • Implicit dependency: haskell-pandoc haskell-hakyll/ppc64el
    • Implicit dependency: haskell-pandoc haskell-hakyll/s390x
    • Implicit dependency: haskell-pandoc haskell-pandoc-lua-engine
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/amd64
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/arm64
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/armel
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/armhf
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/i386
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/mips64el
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/ppc64el
    • Implicit dependency: haskell-pandoc haskell-pandoc-server/s390x
    • Implicit dependency: haskell-pandoc pandoc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-pandoc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-pandoc-lua-engine (0.1-2 to 0.2.0.1-1)
  • Migration status for haskell-pandoc-lua-engine (0.1-2 to 0.2.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-pandoc-lua-engine haskell-hslua-repl
    • Build-Depends(-Arch): haskell-pandoc-lua-engine haskell-pandoc
    • Build-Depends-Indep: haskell-pandoc-lua-engine haskell-hslua-repl
    • Depends: haskell-pandoc-lua-engine haskell-hslua-repl
    • Depends: haskell-pandoc-lua-engine haskell-pandoc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-pandoc-lua-engine.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-yesod-bin (- to 1.6.2.2-2)
  • Migration status for haskell-yesod-bin (- to 1.6.2.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-yesod-bin.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hiredis (0.14.1-4 to 1.2.0-5)
  • Migration status for hiredis (0.14.1-4 to 1.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hiredis would introduce bugs in testing: #1060096
    • missing build on amd64
    • missing build on i386
    • missing build on ppc64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for hiredis/1.2.0-5: arm64: Pass, armel: Pass, armhf: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hiredis.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• imapfilter (1:2.8.1-1.1 to 1:2.8.2-1)
  • Migration status for imapfilter (1:2.8.1-1.1 to 1:2.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imapfilter.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ipmitool (1.8.19-6 to 1.8.19-7)
  • Migration status for ipmitool (1.8.19-6 to 1.8.19-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipmitool.html
    • autopkgtest for ceilometer/1:21.0.0-2: amd64: Ignored failure, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for ceilometer/blocked-on-ci-infra: i386: Ignored failure
    • autopkgtest for ipmitool/1.8.19-7: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• irqbalance (1.9.3-1 to 1.9.3-2)
  • Migration status for irqbalance (1.9.3-1 to 1.9.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irqbalance.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• keepassxc (2.7.4+dfsg.1-2 to 2.7.6+dfsg.1-1)
  • Migration status for keepassxc (2.7.4+dfsg.1-2 to 2.7.6+dfsg.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keepassxc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libmongocrypt (1.8.2-1 to 1.8.4-1)
  • Migration status for libmongocrypt (1.8.2-1 to 1.8.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmongocrypt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libxml-security-java (2.1.7-3 to 2.1.8-1)
  • Migration status for libxml-security-java (2.1.7-3 to 2.1.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: libxml-security-java libcommons-codec-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxml-security-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mdevctl (1.2.0-5 to 1.2.0-6)
  • Migration status for mdevctl (1.2.0-5 to 1.2.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating mdevctl will fix bugs in testing: #1059036
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdevctl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mongo-c-driver (1.25.2-1 to 1.25.4-1)
  • Migration status for mongo-c-driver (1.25.2-1 to 1.25.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-c-driver.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• olive-editor (20221024+ds-1 to 20230614+ds-1)
  • Migration status for olive-editor (20221024+ds-1 to 20230614+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/olive-editor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• openjade (1.4devel1-22 to 1.4devel1-23)
  • Migration status for openjade (1.4devel1-22 to 1.4devel1-23): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjade.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pandoc (3.0.1+ds-3 to 3.1.3+ds-1)
  • Migration status for pandoc (3.0.1+ds-3 to 3.1.3+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: pandoc haskell-pandoc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandoc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• paraview (5.11.2+dfsg-4 to 5.11.2+dfsg-5)
  • Migration status for paraview (5.11.2+dfsg-4 to 5.11.2+dfsg-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: paraview gmsh
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paraview.html
    • autopkgtest for paraview/5.11.2+dfsg-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• passwordmaker-cli (- to 1.5+dfsg-6)
  • Migration status for passwordmaker-cli (- to 1.5+dfsg-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/passwordmaker-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• podget (0.9.1-1 to 0.9.3-1)
  • Migration status for podget (0.9.1-1 to 0.9.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/podget.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyreadstat (1.2.2-1 to 1.2.6-1)
  • Migration status for pyreadstat (1.2.2-1 to 1.2.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyreadstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-firehose (- to 0.5-1)
  • Migration status for python-firehose (- to 0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-firehose.html
    • autopkgtest for python-firehose/0.5-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-pattern (2.6+git20180818-4 to 2.6+git20180818-4.1)
  • Migration status for python-pattern (2.6+git20180818-4 to 2.6+git20180818-4.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pattern.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-schwifty (2023.09.0+dfsg-2 to 2023.11.2+dfsg-1)
  • Migration status for python-schwifty (2023.09.0+dfsg-2 to 2023.11.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating python-schwifty will fix bugs in testing: #1058271
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-schwifty.html
    • autopkgtest for python-schwifty/2023.11.2+dfsg-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-tuspy (1.0.0-2 to 1.0.3-0.1)
  • Migration status for python-tuspy (1.0.0-2 to 1.0.3-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tuspy.html
    • autopkgtest for python-tuspy/1.0.3-0.1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-werkzeug (2.2.2-3 to 2.3.8-1)
  • Migration status for python-werkzeug (2.2.2-3 to 2.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ceilometer/blocked-on-ci-infra: i386: Ignored failure
    • autopkgtest for flask-dance/7.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-werkzeug/2.3.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating python-werkzeug will fix bugs in testing: #1058318
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-werkzeug.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qosmic (1.6.0+git20210807.9f63288-6 to 1.6.0+v20210807-7)
  • Migration status for qosmic (1.6.0+git20210807.9f63288-6 to 1.6.0+v20210807-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qosmic.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qt6ct (0.9-1 to 0.9-2)
  • Migration status for qt6ct (0.9-1 to 0.9-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt6ct.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qtkeychain (0.14.1-1 to 0.14.2-1)
  • Migration status for qtkeychain (0.14.1-1 to 0.14.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtkeychain.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• raft (0.18.3-1 to 0.19.1-1)
  • Migration status for raft (0.18.3-1 to 0.19.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raft.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rime-cantonese (0.0~git20230911.e3c6b17-1 to 0.0~git20240101.e2e088e-1)
  • Migration status for rime-cantonese (0.0~git20230911.e3c6b17-1 to 0.0~git20240101.e2e088e-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rime-cantonese.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ros2-colcon-metadata (0.2.5-2 to 0.2.5-3)
  • Migration status for ros2-colcon-metadata (0.2.5-2 to 0.2.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating ros2-colcon-metadata will fix bugs in testing: #1058343
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-colcon-metadata.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ros2-rcpputils (2.8.1-1 to 2.9.0-1)
  • Migration status for ros2-rcpputils (2.8.1-1 to 2.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-rcpputils.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ros2-rcutils (6.4.1-1 to 6.5.0-1)
  • Migration status for ros2-rcutils (6.4.1-1 to 6.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-rcutils.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-semver-dialects (1.2.1-2 to 1.5.0-1)
  • Migration status for ruby-semver-dialects (1.2.1-2 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): ruby-semver-dialects ruby-deb-version
    • Build-Depends(-Arch): ruby-semver-dialects ruby-thor
    • Depends: ruby-semver-dialects ruby-deb-version
    • Depends: ruby-semver-dialects ruby-thor
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-semver-dialects.html
    • autopkgtest for ruby-semver-dialects/1.5.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-thor (1.2.2-1 to 1.3.0-1)
  • Migration status for ruby-thor (1.2.2-1 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-thor/1.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for schleuder/4.0.3-9: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-thor.html
    • Waiting for reproducibility test results on i386 - info ♻
• rust-rustyline (9.1.2-1 to 13.0.0-1)
  • Migration status for rust-rustyline (9.1.2-1 to 13.0.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustyline.html
    • autopkgtest for rust-rustyline/13.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• sdl-ball (1.02-2 to 1.04+dfsg-1)
  • Migration status for sdl-ball (1.02-2 to 1.04+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdl-ball.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• setuptools-scm (7.1.0-4 to 8.0.4-2)
  • Migration status for setuptools-scm (7.1.0-4 to 8.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for setuptools-scm/8.0.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for setuptools-scm-git-archive/1.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/setuptools-scm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• spread-sheet-widget (0.8-1 to 0.10-3)
  • Migration status for spread-sheet-widget (0.8-1 to 0.10-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spread-sheet-widget.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sudo (1.9.15p4-2 to 1.9.15p5-1)
  • Migration status for sudo (1.9.15p4-2 to 1.9.15p5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for firejail/0.9.72-2: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for osk-sdl/0.67.1-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for sudo/1.9.15p5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sudo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• thumbor-plugins-gifv (- to 0.1.4-1)
  • Migration status for thumbor-plugins-gifv (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by metal, a new source-only upload is needed to allow migration
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thumbor-plugins-gifv.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• uxplay (1.67-1 to 1.68.1-1)
  • Migration status for uxplay (1.67-1 to 1.68.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uxplay.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• weasyprint (59.0-1 to 60.2-1)
  • Migration status for weasyprint (59.0-1 to 60.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/weasyprint.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wike (2.0.1-3 to 2.1.0-1)
  • Migration status for wike (2.0.1-3 to 2.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wike.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xarchiver (1:0.5.4.21-2 to 1:0.5.4.22-1)
  • Migration status for xarchiver (1:0.5.4.21-2 to 1:0.5.4.22-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarchiver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xinv3d (1.3.6-7 to 1.31-1)
  • Migration status for xinv3d (1.3.6-7 to 1.31-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xinv3d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xterm (388-1 to 389-1)
  • Migration status for xterm (388-1 to 389-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spyder-unittest/0.6.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for xterm/389-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bluez (5.70-1.1 to 5.71-1)
  • Migration status for bluez (5.70-1.1 to 5.71-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluez.html
    • autopkgtest for gnome-bluetooth3/42.7-1: amd64: No tests, superficial or marked flaky, arm64: No tests, superficial or marked flaky, armel: No tests, superficial or marked flaky, armhf: No tests, superficial or marked flaky, i386: No tests, superficial or marked flaky, ppc64el: No tests, superficial or marked flaky, s390x: No tests, superficial or marked flaky
    • autopkgtest for python-dbusmock/0.30.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• commons-beanutils (1.9.4-1 to 1.9.4-2)
  • Migration status for commons-beanutils (1.9.4-1 to 1.9.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/commons-beanutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• coq-elpi (1.17.1-1 to 1.19.3-2)
  • Migration status for coq-elpi (1.17.1-1 to 1.19.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-elpi/1.19.3-2/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-elpi/1.19.3-2/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-elpi/1.19.3-2/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-elpi/1.19.3-2/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-elpi/1.19.3-2/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-elpi/1.19.3-2/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-elpi/1.19.3-2/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-elpi/1.19.3-2/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): coq-elpi elpi
    • Depends: coq-elpi coq
    • Depends: coq-elpi elpi
    • Implicit dependency: coq-elpi coq-hierarchy-builder
    • Implicit dependency: coq-elpi mathcomp-algebra-tactics
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-elpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• coreutils (9.1-1 to 9.4-3)
  • Migration status for coreutils (9.1-1 to 9.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by mstone
    • Too young, only 4 of 10 days old
  • Additional info:
    • Updating coreutils will fix bugs in testing: #1058630
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coreutils.html
    • autopkgtest for datefudge/1.24: amd64: Pass, arm64: Pass, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• damo (2.1.0-1 to 2.1.5-1)
  • Migration status for damo (2.1.0-1 to 2.1.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/damo.html
    • autopkgtest for damo/2.1.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deja-dup (45.1-1 to 45.2-1)
  • Migration status for deja-dup (45.1-1 to 45.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deja-dup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• diod (1.0.24-5 to 1.0.24-5.1)
  • Migration status for diod (1.0.24-5 to 1.0.24-5.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diod.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ecmwflibs (2:0.5.7-1 to 2:0.5.7-3)
  • Migration status for ecmwflibs (2:0.5.7-1 to 2:0.5.7-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): ecmwflibs eccodes
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecmwflibs.html
    • autopkgtest for ecmwflibs/2:0.5.7-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ectrans (1.1.0-4 to 1.2.0-2)
  • Migration status for ectrans (1.1.0-4 to 1.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ectrans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• efl (1.26.3-2 to 1.27.0-1)
  • Migration status for efl (1.26.3-2 to 1.27.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/efl.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• erc (- to 5.5+dfsg-2)
  • Migration status for erc (- to 5.5+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• exaile (4.1.3+dfsg-1 to 4.1.3+dfsg-2)
  • Migration status for exaile (4.1.3+dfsg-1 to 4.1.3+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exaile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fail2ban (1.0.2-2 to 1.0.2-3)
  • Migration status for fail2ban (1.0.2-2 to 1.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating fail2ban will fix bugs in testing: #1037437, #770171
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fail2ban.html
    • autopkgtest for freedombox/23.21: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flit-scm (1.6.2-1 to 1.7.0-0.1)
  • Migration status for flit-scm (1.6.2-1 to 1.7.0-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flit-scm.html
    • autopkgtest for flit-scm/1.7.0-0.1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flowblade (2.12-1 to 2.12.0.2-1)
  • Migration status for flowblade (2.12-1 to 2.12.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flowblade.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• forensic-artifacts (20230723-1 to 20230928-1)
  • Migration status for forensic-artifacts (20230723-1 to 20230928-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forensic-artifacts.html
    • autopkgtest for forensic-artifacts/20230928-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• frogr (1.7-1 to 1.8.1-1)
  • Migration status for frogr (1.7-1 to 1.8.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frogr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-nibbles (1:4.0~rc2-1 to 1:4.0.1-2)
  • Migration status for gnome-nibbles (1:4.0~rc2-1 to 1:4.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-nibbles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-settings-daemon (45.0-2 to 45.1-1)
  • Migration status for gnome-settings-daemon (45.0-2 to 45.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-settings-daemon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnote (45.0-1 to 45.1-1)
  • Migration status for gnote (45.0-1 to 45.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnote.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-k8s-api (- to 0.29.0-1)
  • Migration status for golang-k8s-api (- to 0.29.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-k8s-api golang-k8s-apimachinery
    • Depends: golang-k8s-api golang-k8s-apimachinery
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-api.html
    • autopkgtest for golang-k8s-api/0.29.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• golang-k8s-apimachinery (- to 0.29.0-1)
  • Migration status for golang-k8s-apimachinery (- to 0.29.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-apimachinery.html
    • autopkgtest for golang-k8s-apimachinery/0.29.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• golang-k8s-client-go (- to 0.29.0-1)
  • Migration status for golang-k8s-client-go (- to 0.29.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-k8s-client-go golang-k8s-api
    • Build-Depends(-Arch): golang-k8s-client-go golang-k8s-apimachinery
    • Depends: golang-k8s-client-go golang-k8s-api
    • Depends: golang-k8s-client-go golang-k8s-apimachinery
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-client-go.html
    • autopkgtest for golang-k8s-client-go/0.29.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• gsasl (2.2.0-2 to 2.2.1-1)
  • Migration status for gsasl (2.2.0-2 to 2.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for gsasl/2.2.1-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsasl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-hslua-repl (- to 0.1.1-2)
  • Migration status for haskell-hslua-repl (- to 0.1.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): haskell-hslua-repl haskell-isocline
    • Build-Depends-Indep: haskell-hslua-repl haskell-isocline
    • Depends: haskell-hslua-repl haskell-isocline
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hslua-repl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-isocline (- to 1.0.9-2)
  • Migration status for haskell-isocline (- to 1.0.9-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-isocline.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-typst (- to 0.1.0.0-2)
  • Migration status for haskell-typst (- to 0.1.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-typst.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hedgewars (1.0.2-6 to 1.0.2-9)
  • Migration status for hedgewars (1.0.2-6 to 1.0.2-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hedgewars.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• heimdal (7.8.git20221117.28daf24+dfsg-3 to 7.8.git20221117.28daf24+dfsg-4)
  • Migration status for heimdal (7.8.git20221117.28daf24+dfsg-3 to 7.8.git20221117.28daf24+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heimdal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ixo-usb-jtag (0.0.1-2 to 0.0.1-4)
  • Migration status for ixo-usb-jtag (0.0.1-2 to 0.0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ixo-usb-jtag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kgeotag (1.4.0-1 to 1.5.0-1)
  • Migration status for kgeotag (1.4.0-1 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kgeotag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• khronos-opencl-headers (3.0~2023.04.17-1 to 3.0~2023.12.14-1)
  • Migration status for khronos-opencl-headers (3.0~2023.04.17-1 to 3.0~2023.12.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for khronos-opencl-clhpp/3.0~2023.04.17-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for khronos-opencl-headers/3.0~2023.12.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ocl-icd/2.3.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Test in progress, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opencl-headers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• labelme (5.3.1-1 to 5.4.0-1)
  • Migration status for labelme (5.3.1-1 to 5.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labelme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libcommons-codec-java (1.15-1 to 1.16.0-1)
  • Migration status for libcommons-codec-java (1.15-1 to 1.16.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommons-codec-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libcommons-compress-java (1.24.0-1 to 1.25.0-1)
  • Migration status for libcommons-compress-java (1.24.0-1 to 1.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommons-compress-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libjson-schema-modern-perl (0.577-1 to 0.578-1)
  • Migration status for libjson-schema-modern-perl (0.577-1 to 0.578-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libjson-schema-modern-perl/0.578-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjson-schema-modern-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libmath-bigint-gmp-perl (1.6013-1 to 1.7000-1)
  • Migration status for libmath-bigint-gmp-perl (1.6013-1 to 1.7000-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libmath-bigint-gmp-perl/1.7000-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): libmath-bigint-gmp-perl libmath-bigint-perl
    • Depends: libmath-bigint-gmp-perl libmath-bigint-perl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmath-bigint-gmp-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libpng1.6 (1.6.40-2 to 1.6.40-3)
  • Migration status for libpng1.6 (1.6.40-2 to 1.6.40-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for imagemagick/8:6.9.12.98+dfsg1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for uqm/0.8.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for xfig/1:3.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpng1.6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• librandom123 (1.14.0+dfsg-4 to 1.14.0+dfsg-5)
  • Migration status for librandom123 (1.14.0+dfsg-4 to 1.14.0+dfsg-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librandom123.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsdl2 (2.28.5+dfsg-2 to 2.28.5+dfsg-3)
  • Migration status for libsdl2 (2.28.5+dfsg-2 to 2.28.5+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for ffmpeg/7:6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libde265/1.0.15-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libsdl2/2.28.5+dfsg-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libsdl2-image/2.8.1+dfsg-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Test in progress, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libsdl2-ttf/2.20.2+dfsg-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Test in progress, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsdl2-image (2.8.1+dfsg-1 to 2.8.2+dfsg-1)
  • Migration status for libsdl2-image (2.8.1+dfsg-1 to 2.8.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2-image.html
    • autopkgtest for libsdl2-image/2.8.2+dfsg-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsecret (0.21.1-1 to 0.21.2-1)
  • Migration status for libsecret (0.21.1-1 to 0.21.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsecret.html
    • autopkgtest for libsecret/0.21.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libssh2 (1.11.0-3 to 1.11.0-4)
  • Migration status for libssh2 (1.11.0-3 to 1.11.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cargo/0.70.1+ds1-1: amd64: Pass, arm64: No tests, superficial or marked flaky, armel: No tests, superficial or marked flaky, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky, s390x: Pass
    • autopkgtest for curl/8.5.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libssh2/1.11.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libssh2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libtickit-widgets-perl (0.38-1 to 0.39-1)
  • Migration status for libtickit-widgets-perl (0.38-1 to 0.39-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libcircle-fe-term-perl/0.232470-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for libtickit-console-perl/0.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libtickit-widgets-perl/0.39-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtickit-widgets-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libwebsockets (4.3.2-4 to 4.3.3-1)
  • Migration status for libwebsockets (4.3.2-4 to 4.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libwebsockets/4.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mosquitto/2.0.18-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwebsockets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lirc (0.10.1-7.4 to 0.10.2-0.2)
  • Migration status for lirc (0.10.1-7.4 to 0.10.2-0.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lirc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lwip (2.2.0+dfsg1-4 to 2.2.0+dfsg1-5)
  • Migration status for lwip (2.2.0+dfsg1-4 to 2.2.0+dfsg1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lwip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mkvtoolnix (81.0-1 to 82.0-1)
  • Migration status for mkvtoolnix (81.0-1 to 82.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkvtoolnix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mpi4py-fft (2.0.5-1 to 2.0.5-2)
  • Migration status for mpi4py-fft (2.0.5-1 to 2.0.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating mpi4py-fft will fix bugs in testing: #1056822
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpi4py-fft.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mumble (1.3.4-4 to 1.5.517-1)
  • Migration status for mumble (1.3.4-4 to 1.5.517-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mumble/1.5.517-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): mumble poco
    • Depends: mumble poco
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mumble.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• netsurf (3.10-3.1 to 3.11-1)
  • Migration status for netsurf (3.10-3.1 to 3.11-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netsurf.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nom (0.1.5-3 to 0.1.5-4)
  • Migration status for nom (0.1.5-3 to 0.1.5-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• okteta (5:0.26.14-1 to 5:0.26.15-1)
  • Migration status for okteta (5:0.26.14-1 to 5:0.26.15-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/okteta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• parmed (- to 4.2.2+dfsg-3)
  • Migration status for parmed (- to 4.2.2+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): parmed rdkit (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parmed.html
    • autopkgtest for parmed/4.2.2+dfsg-3: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• pegsolitaire (0.3-1 to 0.3-2)
  • Migration status for pegsolitaire (0.3-1 to 0.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pegsolitaire.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-http-httplug (2.3.0-2 to 2.4.0-2)
  • Migration status for php-http-httplug (2.3.0-2 to 2.4.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-httplug.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-http-message-factory (1.0.2-3 to 1.1.0-2)
  • Migration status for php-http-message-factory (1.0.2-3 to 1.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-message-factory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• picom (10.2-2 to 10.2-3)
  • Migration status for picom (10.2-2 to 10.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picom.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• proxychains-ng (4.16-3 to 4.16-4)
  • Migration status for proxychains-ng (4.16-3 to 4.16-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proxychains-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyalsaaudio (0.8.4-1.1 to 0.10.0-0.1)
  • Migration status for pyalsaaudio (0.8.4-1.1 to 0.10.0-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating pyalsaaudio will fix bugs in testing: #1055564
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyalsaaudio.html
    • autopkgtest for pyalsaaudio/0.10.0-0.1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pytest (7.4.3-2 to 7.4.4-1)
  • Migration status for pytest (7.4.3-2 to 7.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for astropy/5.3.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for crmsh/4.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for cwltest/2.3.20230825125225-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for debugpy/1.8.0+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for einsteinpy/0.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for freedombox/23.21: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for h5py/3.9.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for hiro/1.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ipyparallel/7.1.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for joblib/1.3.2-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for jupyter-client/7.4.9-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for jupyter-notebook/6.4.12-2.2: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for lektor/3.3.7-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for py-rnp/0.1.0+git20221014.01b7129-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyensembl/2.2.8+ds-1: amd64: No tests, superficial or marked flaky, arm64: No tests, superficial or marked flaky, armel: No tests, superficial or marked flaky, armhf: No tests, superficial or marked flaky, i386: No tests, superficial or marked flaky, ppc64el: No tests, superficial or marked flaky, s390x: No tests, superficial or marked flaky
    • autopkgtest for pyspread/2.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytango/9.4.2-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pytest/7.4.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-apeye/1.4.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-arabic-reshaper/2.1.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-bleach/6.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-boolean.py/4.0-4: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-bumps/n/a: arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-cai/1.0.2-4: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-can/4.3.1-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-channels-redis/4.1.0-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-cluster/n/a: arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-cmarkgfm/0.8.0-3: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-cooler/0.9.1-1: amd64: Pass, arm64: Test in progress, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-dbusmock/0.30.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-fakeredis/1.9.0-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Pass
    • autopkgtest for python-graphviz/0.20.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-ipmi/0.4.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-libtmux/0.25.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-msrest/0.6.21-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-pyotp/2.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-schema-salad/8.4.20230808163024-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ros2-ament-cmake/2.3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for snakemake/7.32.4-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for sphinx/7.2.6-3: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for spyder-line-profiler/0.3.2-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for sqlitedict/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for terminado/0.17.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for tmuxp/1.34.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for tpm2-pytss/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for vsts-cd-manager/1.0.2-4: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for weresync/1.1.5-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-cramjam (- to 2.7.0.1+ds1-1)
  • Migration status for python-cramjam (- to 2.7.0.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-cramjam/2.7.0.1+ds1-1: amd64: Regression or new test ♻
    • python-cramjam unsatisfiable Build-Depends(-Arch) on amd64: librust-lz4-dev
    • Not built on buildd: arch amd64 binaries uploaded by lolando
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): python-cramjam python-maturin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cramjam.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-django (3:4.2.8-1 to 3:4.2.9-1)
  • Migration status for python-django (3:4.2.8-1 to 3:4.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-picklefield/3.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for django-rq/2.9.0-1: amd64: No tests, superficial or marked flaky, arm64: No tests, superficial or marked flaky, armel: No tests, superficial or marked flaky, armhf: No tests, superficial or marked flaky, i386: No tests, superficial or marked flaky, ppc64el: No tests, superficial or marked flaky, s390x: No tests, superficial or marked flaky
    • autopkgtest for freedombox/23.21: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for graphite-web/1.1.10-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-django/3:4.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-hiredis (1.0.1-2 to 2.3.2-1)
  • Migration status for python-hiredis (1.0.1-2 to 2.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-hiredis will fix bugs in testing: #1055557
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hiredis.html
    • autopkgtest for python-hiredis/2.3.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-invoke (2.0.0-1 to 2.0.0-1.2)
  • Migration status for python-invoke (2.0.0-1 to 2.0.0-1.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-invoke.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-multidict (6.0.4-1 to 6.0.4-1.1)
  • Migration status for python-multidict (6.0.4-1 to 6.0.4-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-multidict will fix bugs in testing: #1055717
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-multidict.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-pubchempy (- to 1.0.4-2)
  • Migration status for python-pubchempy (- to 1.0.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pubchempy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-typeguard (2.2.2-2 to 4.1.5-1)
  • Migration status for python-typeguard (2.2.2-2 to 4.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-tenacity/8.2.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-typeguard/4.1.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-typeguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-deb-version (- to 1.0.2-1)
  • Migration status for ruby-deb-version (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-deb-version.html
    • autopkgtest for ruby-deb-version/1.0.2-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-devise (4.9.2-1 to 4.9.3-1)
  • Migration status for ruby-devise (4.9.2-1 to 4.9.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for ruby-devise/4.9.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-async-zip (- to 0.0.16-1)
  • Migration status for rust-async-zip (- to 0.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-zip/0.0.16-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-zip.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sdl12-compat (1.2.68-1 to 1.2.68-2)
  • Migration status for sdl12-compat (1.2.68-1 to 1.2.68-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdl12-compat.html
    • autopkgtest for sdl12-compat/1.2.68-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sugarjar (1.0.0-1 to 1.1.0-1)
  • Migration status for sugarjar (1.0.0-1 to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sugarjar.html
    • autopkgtest for sugarjar/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• swayimg (1.12-1 to 2.0-1)
  • Migration status for swayimg (1.12-1 to 2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swayimg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tellico (3.5.2-1 to 3.5.3-1)
  • Migration status for tellico (3.5.2-1 to 3.5.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tellico.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• toulbar2 (1.1.1+dfsg-1 to 1.2.1+dfsg-0.1)
  • Migration status for toulbar2 (1.1.1+dfsg-1 to 1.2.1+dfsg-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toulbar2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• urwid (2.1.2-4 to 2.1.2-4.2)
  • Migration status for urwid (2.1.2-4 to 2.1.2-4.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating urwid will fix bugs in testing: #1055547, #1058250
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urwid.html
    • autopkgtest for urwid/2.1.2-4.2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• velocity (1.7-6 to 1.7-7)
  • Migration status for velocity (1.7-6 to 1.7-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/velocity.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vips (8.15.0-2 to 8.15.1-1)
  • Migration status for vips (8.15.0-2 to 8.15.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating vips will fix bugs in testing: #1057347
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vte2.91 (0.74.1-1 to 0.74.2-1)
  • Migration status for vte2.91 (0.74.1-1 to 0.74.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vte2.91.html
    • autopkgtest for vte2.91/0.74.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xdiskusage (1.60-2 to 1.60-3)
  • Migration status for xdiskusage (1.60-2 to 1.60-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdiskusage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ycmd (0+20230611+git3392251+ds-2 to 0+20231230+git9e43034+ds-1)
  • Migration status for ycmd (0+20230611+git3392251+ds-2 to 0+20231230+git9e43034+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vim-youcompleteme/0+20230612+git49ced5a+ds-3: arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ycmd/0+20231230+git9e43034+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ycmd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• asahi-audio (- to 1.6-1)
  • Migration status for asahi-audio (- to 1.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asahi-audio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• astropy-iers-data (0.2023.11.06.00.31.16-1 to 0.2024.01.01.00.33.39-1)
  • Migration status for astropy-iers-data (0.2023.11.06.00.31.16-1 to 0.2024.01.01.00.33.39-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astropy-iers-data.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• bankstown-lv2 (1.0.3-2 to 1.1.0-1)
  • Migration status for bankstown-lv2 (1.0.3-2 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bankstown-lv2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• cinnamon (5.8.4-3 to 5.8.4-4)
  • Migration status for cinnamon (5.8.4-3 to 5.8.4-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating cinnamon will fix bugs in testing: #1057391
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cinnamon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• debdelta (0.69 to 0.70)
  • Migration status for debdelta (0.69 to 0.70): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debdelta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• eccodes (2.33.0-2 to 2.33.0-3)
  • Migration status for eccodes (2.33.0-2 to 2.33.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eccodes.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• eg25-manager (0.4.6-2 to 0.4.6-3)
  • Migration status for eg25-manager (0.4.6-2 to 0.4.6-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eg25-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• fiat-ecmwf (1.2.0-1 to 1.2.0-3)
  • Migration status for fiat-ecmwf (1.2.0-1 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fiat-ecmwf.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• fish (3.6.4-1 to 3.7.0-1)
  • Migration status for fish (3.6.4-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fish.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• gitinspector (0.4.4+dfsg-13 to 0.4.4+dfsg-14)
  • Migration status for gitinspector (0.4.4+dfsg-13 to 0.4.4+dfsg-14): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitinspector.html
    • autopkgtest for gitinspector/0.4.4+dfsg-14: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• gnuradio (3.10.8.0-1 to 3.10.9.1-1)
  • Migration status for gnuradio (3.10.8.0-1 to 3.10.9.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuradio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• grapefruit (0.1~a4+dfsg-1 to 0.1~a4+dfsg-2)
  • Migration status for grapefruit (0.1~a4+dfsg-1 to 0.1~a4+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grapefruit.html
    • autopkgtest for grapefruit/0.1~a4+dfsg-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• jupyter-server (1.23.3-1 to 1.23.3-2)
  • Migration status for jupyter-server (1.23.3-1 to 1.23.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-server.html
    • autopkgtest for jupyter-server/1.23.3-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• lazarus (3.0+dfsg1-3 to 3.0+dfsg1-5)
  • Migration status for lazarus (3.0+dfsg1-3 to 3.0+dfsg1-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: lazarus fpc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lazarus.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for lazarus/3.0+dfsg1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• libeuclid-java (2.6-2 to 2.7-1)
  • Migration status for libeuclid-java (2.6-2 to 2.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libeuclid-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libexttextcat (3.4.6-1 to 3.4.7-1)
  • Migration status for libexttextcat (3.4.6-1 to 3.4.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libexttextcat.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• libmath-bigint-perl (2.002001-1 to 2.003001-1)
  • Migration status for libmath-bigint-perl (2.002001-1 to 2.003001-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libmath-bigint-gmp-perl/1.6013-1: arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for libmath-bigint-perl/2.003001-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmath-bigint-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• libxcrypt (1:4.4.36-2 to 1:4.4.36-4)
  • Migration status for libxcrypt (1:4.4.36-2 to 1:4.4.36-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cockpit/307-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ecflow/5.11.4-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for glibc/2.37-12: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for gsequencer/6.2.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for inn2/2.7.2~20230917-1: amd64: No tests, superficial or marked flaky, arm64: No tests, superficial or marked flaky, armel: No tests, superficial or marked flaky, armhf: No tests, superficial or marked flaky, i386: No tests, superficial or marked flaky, ppc64el: No tests, superficial or marked flaky, s390x: No tests, superficial or marked flaky
    • autopkgtest for libxcrypt/1:4.4.36-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mariadb/1:10.11.6-1: amd64: Failed (not a regression), arm64: Pass, armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, s390x: Failed (not a regression)
    • autopkgtest for python3.12/3.12.1-2: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for screen/4.9.1-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for squid/6.5-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for systemd/255.2-2: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for toybox/0.8.9+dfsg-1: amd64: Failed (not a regression), arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for x11vnc/0.9.16-9: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxcrypt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• linux (6.5.13-1 to 6.6.9-1)
  • Migration status for linux (6.5.13-1 to 6.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dkms/3.0.12-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for glibc/2.37-12: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for linux/6.6.9-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Implicit dependency: linux linux
    • Implicit dependency: linux linux-signed-amd64
    • Implicit dependency: linux linux-signed-arm64
  • Additional info:
    • Updating linux will fix bugs in testing: #1032104, #1055021
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• linux-signed-amd64 (6.5.13+1 to 6.6.9+1)
  • Migration status for linux-signed-amd64 (6.5.13+1 to 6.6.9+1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): linux-signed-amd64 linux (not considered)
    • Built-Using: linux-signed-amd64 linux (not considered)
    • Depends: linux-signed-amd64 linux (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
    • Reproducible on amd64 - info ♻
    • 5 days old (needed 5 days)
• linux-signed-arm64 (6.5.13+1 to 6.6.9+1)
  • Migration status for linux-signed-arm64 (6.5.13+1 to 6.6.9+1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): linux-signed-arm64 linux (not considered)
    • Built-Using: linux-signed-arm64 linux (not considered)
    • Depends: linux-signed-arm64 linux (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• minizinc (2.6.4+dfsg1-1 to 2.8.2+dfsg1-1)
  • Migration status for minizinc (2.6.4+dfsg1-1 to 2.8.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minizinc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• minizinc-ide (2.6.3-1 to 2.8.2-1)
  • Migration status for minizinc-ide (2.6.3-1 to 2.8.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minizinc-ide.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• modemmanager (1.22.0-1 to 1.22.0-2)
  • Migration status for modemmanager (1.22.0-1 to 1.22.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating modemmanager will fix bugs in testing: #1057269
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modemmanager.html
    • autopkgtest for fwupd/1.9.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• mpi4py (3.1.5-1 to 3.1.5-3)
  • Migration status for mpi4py (3.1.5-1 to 3.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.7.2-2: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for h5py/3.9.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mpi4py/3.1.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating mpi4py will fix bugs in testing: #1056820
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpi4py.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• mrbuild (1.7-1 to 1.8-1)
  • Migration status for mrbuild (1.7-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrbuild.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• norm (1.5.9+dfsg-2 to 1.5.9+dfsg-3)
  • Migration status for norm (1.5.9+dfsg-2 to 1.5.9+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/norm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• octave-arduino (0.11.0-1 to 0.12.0-1)
  • Migration status for octave-arduino (0.11.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-arduino.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for octave-arduino/0.12.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• opengnb (1.4.5.a-1 to 1.4.5.b-2)
  • Migration status for opengnb (1.4.5.a-1 to 1.4.5.b-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opengnb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• openmpi (4.1.6-1 to 4.1.6-5)
  • Migration status for openmpi (4.1.6-1 to 4.1.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios/1.13.1-33: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for adios2/2.9.2+dfsg1-3: arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for h5py/3.9.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for openmpi/4.1.6-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating openmpi will fix bugs in testing: #1058526
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • 5 days old (needed 5 days)
• protection-domain-mapper (1.0-4 to 1.0-5)
  • Migration status for protection-domain-mapper (1.0-4 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/protection-domain-mapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• python-lzstring (1.0.4-2 to 1.0.4-3)
  • Migration status for python-lzstring (1.0.4-2 to 1.0.4-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating python-lzstring will fix bugs in testing: #1058085
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lzstring.html
    • autopkgtest for python-lzstring/1.0.4-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• python-rsa (4.8-1 to 4.9-1)
  • Migration status for python-rsa (4.8-1 to 4.9-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rsa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• python-scruffy (0.3.3-3 to 0.3.8.2-1)
  • Migration status for python-scruffy (0.3.3-3 to 0.3.8.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating python-scruffy will fix bugs in testing: #1058129
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-scruffy.html
    • autopkgtest for python-scruffy/0.3.8.2-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• python-sparse (- to 0.14.0-2)
  • Migration status for python-sparse (- to 0.14.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-sparse/0.14.0-2: amd64: Pass, arm64: Regression or new test ♻ , armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sparse.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• python-traitsui (8.0.0-1 to 8.0.0-2)
  • Migration status for python-traitsui (8.0.0-1 to 8.0.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-traitsui.html
    • autopkgtest for python-traitsui/8.0.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• qrtr (1.0-2 to 1.0-3)
  • Migration status for qrtr (1.0-2 to 1.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qrtr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• railway-gtk (- to 2.2.0-1)
  • Migration status for railway-gtk (- to 2.2.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/railway-gtk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rmtfs (1.0-2 to 1.0-3)
  • Migration status for rmtfs (1.0-2 to 1.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rmtfs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• ruby-apollo-upload-server (2.1.0-1 to 2.1.5-1)
  • Migration status for ruby-apollo-upload-server (2.1.0-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-apollo-upload-server.html
    • autopkgtest for ruby-apollo-upload-server/2.1.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-ascii-canvas (2.0.0-2 to 3.0.0-1)
  • Migration status for rust-ascii-canvas (2.0.0-2 to 3.0.0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): rust-ascii-canvas rust-term
    • Depends: rust-ascii-canvas rust-term
    • Implicit dependency: rust-ascii-canvas rust-lalrpop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ascii-canvas.html
    • autopkgtest for rust-ascii-canvas/3.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-cargo-auditable (0.6.1-2 to 0.6.1-3)
  • Migration status for rust-cargo-auditable (0.6.1-2 to 0.6.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-cargo-auditable rust-ahash-0.7 (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-cargo-auditable rust-pico-args
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-auditable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-just (- to 1.14.0-1)
  • Migration status for rust-just (- to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-just-dev/amd64 has unsatisfiable dependency
    • rust-just unsatisfiable Build-Depends(-Arch) on amd64: librust-strum-0.24+default-dev
    • rust-just unsatisfiable Build-Depends(-Arch) on amd64: librust-strum-0.24+derive-dev
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-just.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-lalrpop (0.20.0-2 to 0.20.0-3)
  • Migration status for rust-lalrpop (0.20.0-2 to 0.20.0-3): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): rust-lalrpop rust-ascii-canvas
    • Build-Depends(-Arch): rust-lalrpop rust-pico-args
    • Build-Depends(-Arch): rust-lalrpop rust-term
    • Depends: rust-lalrpop rust-ascii-canvas
    • Depends: rust-lalrpop rust-pico-args
    • Depends: rust-lalrpop rust-term
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lalrpop.html
    • autopkgtest for rust-lalrpop/0.20.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-pico-args (0.4.2-1 to 0.5.0-1)
  • Migration status for rust-pico-args (0.4.2-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: rust-pico-args rust-lalrpop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pico-args.html
    • autopkgtest for rust-pico-args/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-prettytable-rs (0.10.0-1 to 0.10.0-2)
  • Migration status for rust-prettytable-rs (0.10.0-1 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): rust-prettytable-rs rust-term
    • Depends: rust-prettytable-rs rust-term
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prettytable-rs.html
    • autopkgtest for rust-prettytable-rs/0.10.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-slog-term (2.6.0-1 to 2.9.0-1)
  • Migration status for rust-slog-term (2.6.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): rust-slog-term rust-term
    • Depends: rust-slog-term rust-term
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-slog-term.html
    • autopkgtest for rust-slog-term/2.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-term (0.5.2-5 to 0.7.0-1)
  • Migration status for rust-term (0.5.2-5 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: rust-term rust-ascii-canvas
    • Implicit dependency: rust-term rust-lalrpop
    • Implicit dependency: rust-term rust-prettytable-rs
    • Implicit dependency: rust-term rust-slog-term
    • Implicit dependency: rust-term rustup
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-term.html
    • autopkgtest for rust-term/0.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-wasmtime (10.0.1+dfsg-7 to 16.0.0+dfsg-2)
  • Migration status for rust-wasmtime (10.0.1+dfsg-7 to 16.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating rust-wasmtime will fix bugs in testing: #1059555
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wasmtime.html
    • autopkgtest for rust-wasmtime/16.0.0+dfsg-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rustup (1.26.0-1 to 1.26.0-3)
  • Migration status for rustup (1.26.0-1 to 1.26.0-3): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): rustup rust-term
    • Depends: rustup rust-term
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rustup.html
    • autopkgtest for rustup/1.26.0-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• stomper (0.4.3-2 to 0.4.3-3)
  • Migration status for stomper (0.4.3-2 to 0.4.3-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stomper.html
    • autopkgtest for stomper/0.4.3-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• tqftpserv (1.0-4 to 1.0-5)
  • Migration status for tqftpserv (1.0-4 to 1.0-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tqftpserv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• tzdata (2023c-11 to 2023d-1)
  • Migration status for tzdata (2023c-11 to 2023d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for chrony/4.5-1: amd64: Test in progress, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mmdebstrap/1.4.0-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for partd/1.3.0-1: i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for systemd/255.2-2: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for tzdata/2023d-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tzdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• uthash (2.3.0-1 to 2.3.0-2)
  • Migration status for uthash (2.3.0-1 to 2.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uthash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wordpress (6.3.2+dfsg1-1 to 6.4.2+dfsg1-1)
  • Migration status for wordpress (6.3.2+dfsg1-1 to 6.4.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating wordpress will fix bugs in testing: #1058810
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wordpress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• wsjtx (2.7.0~rc2+repack-2 to 2.7.0~rc3+repack-1)
  • Migration status for wsjtx (2.7.0~rc2+repack-2 to 2.7.0~rc3+repack-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wsjtx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• xaos (4.3.1-1 to 4.3.1-2)
  • Migration status for xaos (4.3.1-1 to 4.3.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xaos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• xfce4-cpugraph-plugin (1.2.8-1 to 1.2.10-1)
  • Migration status for xfce4-cpugraph-plugin (1.2.8-1 to 1.2.10-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-cpugraph-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• cpuinfo (0.0~git20220819.8ec7bd9-3 to 0.0~git20230113.6481e8b-2)
  • Migration status for cpuinfo (0.0~git20220819.8ec7bd9-3 to 0.0~git20230113.6481e8b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cpuinfo/0.0~git20230113.6481e8b-2: amd64: Pass, arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for pytorch-cuda/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpuinfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• edk2 (2023.11-2 to 2023.11-3)
  • Migration status for edk2 (2023.11-2 to 2023.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by dannf, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edk2.html
    • autopkgtest for edk2/2023.11-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility reference results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• elpi (1.17.0-1 to 1.17.4-3)
  • Migration status for elpi (1.17.0-1 to 1.17.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: elpi coq-elpi (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• gcc-snapshot (- to 1:20240101-1)
  • Migration status for gcc-snapshot (- to 1:20240101-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-snapshot would introduce bugs in testing: #321449, #651291
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for gcc-snapshot/1:20240101-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Impossible Build-Depends(-Arch): gcc-snapshot -> gnat-13/13.2.0-5/mips64el
    • missing build on armel
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• gloo (0.0~git20230117.1090929-2 to 0.0~git20230519.597accf-2)
  • Migration status for gloo (0.0~git20230117.1090929-2 to 0.0~git20230519.597accf-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gloo/0.0~git20230519.597accf-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytorch/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gloo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• ideep (0.0~git20230213.7bc3e12-2 to 0.0~git20230825.6f4d653-2)
  • Migration status for ideep (0.0~git20230213.7bc3e12-2 to 0.0~git20230825.6f4d653-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ideep onednn (not considered)
    • Depends: ideep onednn (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ideep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• kgb-bot (1.59-1 to 1.60-1)
  • Migration status for kgb-bot (1.59-1 to 1.60-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating kgb-bot will fix bugs in testing: #1057932
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kgb-bot.html
    • autopkgtest for kgb-bot/1.60-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• node-html5-qrcode (- to 2.3.8+repack-3)
  • Migration status for node-html5-qrcode (- to 2.3.8+repack-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-html5-qrcode would introduce bugs in testing: #1059829
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-html5-qrcode.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• numba (0.57.1+dfsg-1 to 0.58.1+dfsg-1)
  • Migration status for numba (0.57.1+dfsg-1 to 0.58.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for numba/0.58.1+dfsg-1: arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for numba/blocked-on-ci-infra: amd64: Failed (not a regression), ppc64el: Failed (not a regression)
  • Additional info:
    • Updating numba will fix bugs in testing: #1057461, #1058301
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numba.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• onednn (2.7.4-2 to 3.1.1-2)
  • Migration status for onednn (2.7.4-2 to 3.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for onednn/3.1.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytorch/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytorch-cuda/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onednn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• onnx (1.13.1-3 to 1.14.1-2)
  • Migration status for onnx (1.13.1-3 to 1.14.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for onnx/1.14.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytorch/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pytorch-cuda/2.0.1+dfsg-5: amd64: Regression or new test ♻ (reference ♻), ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onnx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• open3d (- to 0.17.0+ds-9)
  • Migration status for open3d (- to 0.17.0+ds-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): open3d embree (not considered)
    • Depends: open3d embree (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open3d.html
    • autopkgtest for open3d/0.17.0+ds-9: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• pytables (3.7.0-10 to 3.9.2-1)
  • Migration status for pytables (3.7.0-10 to 3.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/1.5.3+dfsg-10: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for pytables/3.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • pytables unsatisfiable Build-Depends(-Arch) on s390x: libblosc2-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): pytables c-blosc2
    • Depends: pytables c-blosc2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytables.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• rsyslog (8.2312.0-1 to 8.2312.0-2)
  • Migration status for rsyslog (8.2312.0-1 to 8.2312.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsyslog.html
    • autopkgtest for rsyslog/8.2312.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• yt-dlp (2023.11.16-1 to 2023.12.30-1)
  • Migration status for yt-dlp (2023.11.16-1 to 2023.12.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for yt-dlp/2023.12.30-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yt-dlp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• blender (- to 4.0.2+dfsg-1)
  • Migration status for blender (- to 4.0.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): blender embree (not considered)
    • Depends: blender embree (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blender.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• c-blosc2 (- to 2.12.0+ds-1)
  • Migration status for c-blosc2 (- to 2.12.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): c-blosc2 grok (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/c-blosc2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• courier (- to 1.0.16-3.2)
  • Migration status for courier (- to 1.0.16-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating courier would introduce bugs in testing: #1000053
    • Build-Depends(-Arch): courier courier-authlib
    • Depends: courier courier-authlib
    • Depends: courier maildrop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier.html
    • autopkgtest for courier/1.0.16-3.2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• debian-edu-doc (2.12.20 to 2.12.21)
  • Migration status for debian-edu-doc (2.12.20 to 2.12.21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debian-edu-doc/2.12.21: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-edu-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• django-sitetree (1.17.3+dfsg-1 to 1.18.0+dfsg-1)
  • Migration status for django-sitetree (1.17.3+dfsg-1 to 1.18.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-sitetree.html
    • autopkgtest for django-sitetree/1.18.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 7 days)
• dolfinx-mpc (0.7.0.post1-1 to 0.7.1-1)
  • Migration status for dolfinx-mpc (0.7.0.post1-1 to 0.7.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dolfinx-mpc petsc (not considered)
    • Invalidated by dependency
    • Depends: dolfinx-mpc fenics-dolfinx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolfinx-mpc.html
    • autopkgtest for dolfinx-mpc/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• gitlab (- to 16.4.4+ds2-4)
  • Migration status for gitlab (- to 16.4.4+ds2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gitlab/amd64 has unsatisfiable dependency
    • gitlab/arm64 has unsatisfiable dependency
    • Updating gitlab would introduce bugs in testing: #1009942, #983915
    • autopkgtest for gitlab/16.4.4+ds2-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): gitlab gitaly
    • Built-Using: gitlab gitaly
    • Built-Using: gitlab golang-golang-x-oauth2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Reproducible on armhf - info ♻
    • 7 days old (needed 5 days)
• golang-golang-x-tools (1:0.15.0+ds-1 to 1:0.16.1+ds-1)
  • Migration status for golang-golang-x-tools (1:0.15.0+ds-1 to 1:0.16.1+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for golang-github-shurcool-httpfs/0.0~git20230704.f1e31cf-1: amd64: Pass, arm64: Test in progress, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for golang-golang-x-tools/1:0.16.1+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for vim-youcompleteme/0+20230612+git49ced5a+ds-3: arm64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-golang-x-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• hugo (0.120.4-1 to 0.121.1-1)
  • Migration status for hugo (0.120.4-1 to 0.121.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): hugo golang-golang-x-tools (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hugo.html
    • autopkgtest for hugo/0.121.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• libuv1 (1.46.0-2 to 1.46.0-3)
  • Migration status for libuv1 (1.46.0-2 to 1.46.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nodejs/18.19.0+dfsg-6: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating libuv1 will fix bugs in testing: #1058743
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libuv1.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• mapclassify (- to 2.6.1-3)
  • Migration status for mapclassify (- to 2.6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mapclassify would introduce bugs in testing: #1057383
    • Build-Depends(-Arch): mapclassify libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mapclassify.html
    • autopkgtest for mapclassify/2.6.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• oxigraph (- to 0.3.22-3)
  • Migration status for oxigraph (- to 0.3.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for oxigraph/0.3.22-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oxigraph.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• python-hypothesis (6.92.1-1 to 6.92.2-1)
  • Migration status for python-hypothesis (6.92.1-1 to 6.92.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mdanalysis/2.5.0+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for python-fakeredis/1.9.0-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Pass
    • autopkgtest for python-hypothesis/6.92.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hypothesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• devicexlib (0.1.0-2 to 0.8.2-1)
  • Migration status for devicexlib (0.1.0-2 to 0.8.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Updating devicexlib will fix bugs in testing: #1059878
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devicexlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• fortunes-it (2.2-1 to 2.2-2)
  • Migration status for fortunes-it (2.2-1 to 2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tiposchi@tiscali.it, a new source-only upload is needed to allow migration
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortunes-it.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• graph-tool (2.58+ds-1 to 2.58+ds-2)
  • Migration status for graph-tool (2.58+ds-1 to 2.58+ds-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for graph-tool/2.58+ds-2: amd64: Pass, arm64: Pass, s390x: Pass
  • Additional info:
    • Updating graph-tool will fix bugs in testing: #1056079
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graph-tool.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• libgridxc (- to 2.0.1-1)
  • Migration status for libgridxc (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgridxc would introduce bugs in testing: #1055110
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgridxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• obs-studio (29.1.3+dfsg-2 to 30.0.2+dfsg-1)
  • Migration status for obs-studio (29.1.3+dfsg-2 to 30.0.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-studio would introduce bugs in testing: #1059799
    • obs-studio unsatisfiable Build-Depends(-Arch) on ppc64el: libluajit-5.1-dev
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating obs-studio will fix bugs in testing: #1057587
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-studio.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• python-refurb (1.24.0-1 to 1.26.0-1)
  • Migration status for python-refurb (1.24.0-1 to 1.26.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-refurb fastapi (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-refurb.html
    • autopkgtest for python-refurb/1.26.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 7 days)
• python-xapian-haystack (2.1.1-1 to 3.1.0-1)
  • Migration status for python-xapian-haystack (2.1.1-1 to 3.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xapian-haystack.html
    • autopkgtest for python-xapian-haystack/3.1.0-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rdkit (- to 202309.3-1)
  • Migration status for rdkit (- to 202309.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rdkit/202309.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdkit.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• ruby-re2 (1.7.0-1 to 2.5.0-2)
  • Migration status for ruby-re2 (1.7.0-1 to 2.5.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for ruby-re2/2.5.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-re2.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-ahash (- to 0.8.7-1)
  • Migration status for rust-ahash (- to 0.8.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ahash would introduce bugs in testing: #1059675
    • autopkgtest for rust-ahash/0.8.7-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ahash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-ahash-0.7 (0.7.6-13 to 0.7.7-1)
  • Migration status for rust-ahash-0.7 (0.7.6-13 to 0.7.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ahash-0.7/0.7.7-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ahash-0.7.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-microformats (- to 0.6.1-1)
  • Migration status for rust-microformats (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-microformats would introduce bugs in testing: #1050087
    • autopkgtest for rust-microformats/0.6.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-microformats.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• zsh-antidote (1.9.3-1 to 1.9.4-1)
  • Migration status for zsh-antidote (1.9.3-1 to 1.9.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zsh-antidote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dbi (1.1.3-1 to 1.2.0-1)
  • Migration status for dbi (1.1.3-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-dbitest/1.7.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 9 days old (needed 5 days)
• git-credential-oauth (0.8.0-1 to 0.11.0-1)
  • Migration status for git-credential-oauth (0.8.0-1 to 0.11.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): git-credential-oauth golang-golang-x-oauth2 (not considered)
    • Built-Using: git-credential-oauth golang-golang-x-oauth2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-credential-oauth.html
    • autopkgtest for git-credential-oauth/0.11.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• golang-github-hanwen-go-fuse (2.1.0+git20220822.58a7e14-1 to 2.4.2-1)
  • Migration status for golang-github-hanwen-go-fuse (2.1.0+git20220822.58a7e14-1 to 2.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-containerd-stargz-snapshotter/0.12.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hanwen-go-fuse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 10 days old (needed 5 days)
• odr-dabmux (- to 4.4.1+ds-1)
  • Migration status for odr-dabmux (- to 4.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odr-dabmux would introduce bugs in testing: #1033126
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odr-dabmux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 10 days old (needed 10 days)
• python-geotiepoints (- to 1.7.1-1)
  • Migration status for python-geotiepoints (- to 1.7.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-geotiepoints python-xarray (not considered)
    • Depends: python-geotiepoints python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): python-geotiepoints pyresample
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-geotiepoints.html
    • autopkgtest for python-geotiepoints/1.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• astropy (5.3.4-2 to 6.0.0-1)
  • Migration status for astropy (5.3.4-2 to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for astropy/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for gavodachs/2.8+dfsg-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astropy.html
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• coqeal (1.1.3-1 to 2.0.0-1)
  • Migration status for coqeal (1.1.3-1 to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coqeal ssreflect (not considered)
    • Invalidated by dependency
    • Depends: coqeal coq
    • Depends: coqeal coq-bignums
    • Depends: coqeal mathcomp-real-closed
    • Depends: coqeal paramcoq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coqeal.html
    • autopkgtest for coqeal/2.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• dune-common (2.9.0-3 to 2.9.0-6)
  • Migration status for dune-common (2.9.0-3 to 2.9.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: dune-common doxygen (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dune-common.html
    • autopkgtest for dune-common/2.9.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• jupyterlab (- to 4.0.9+ds1-1)
  • Migration status for jupyterlab (- to 4.0.9+ds1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): jupyterlab jupyter-events
    • Build-Depends(-Arch): jupyterlab node-corepack
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/j/jupyterlab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• libheif (1.17.4-1 to 1.17.6-1)
  • Migration status for libheif (1.17.4-1 to 1.17.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-libheif-sys/1.16.2-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libheif.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• lxml (4.9.3-1 to 4.9.4-1)
  • Migration status for lxml (4.9.3-1 to 4.9.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxml.html
    • autopkgtest for ceilometer/blocked-on-ci-infra: i386: Ignored failure
    • autopkgtest for xmds2/blocked-on-ci-infra: amd64: Ignored failure, ppc64el: Ignored failure
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• lyskom-elisp-client (0.48+git.20200923.ec349ff4-3 to 0.48+git.20231226.364902c3-1)
  • Migration status for lyskom-elisp-client (0.48+git.20200923.ec349ff4-3 to 0.48+git.20231226.364902c3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Ignoring piuparts failure (Not a regression) - https://piuparts.debian.org/sid/source/l/lyskom-elisp-client.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• meson (1.2.3-1 to 1.3.1-1)
  • Migration status for meson (1.2.3-1 to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for meson/1.3.1-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating meson will fix bugs in testing: #1059223
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meson.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• prometheus-flask-exporter (- to 0.23.0-1)
  • Migration status for prometheus-flask-exporter (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-flask-exporter.html
    • autopkgtest for prometheus-flask-exporter/0.23.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• stellarium (23.3-1 to 23.4-1)
  • Migration status for stellarium (23.3-1 to 23.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • stellarium unsatisfiable Build-Depends(-Arch) on armel: qtwebengine5-dev (>= 5.15)
    • stellarium unsatisfiable Build-Depends(-Arch) on ppc64el: qtwebengine5-dev (>= 5.15)
    • stellarium unsatisfiable Build-Depends(-Arch) on s390x: qtwebengine5-dev (>= 5.15)
    • missing build on armel
    • missing build on ppc64el
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stellarium.html
    • Reproducible on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 11 days old (needed 5 days)
• coq-extructures (0.3.1-4 to 0.4.0-1)
  • Migration status for coq-extructures (0.3.1-4 to 0.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-extructures ssreflect (not considered)
    • Invalidated by dependency
    • Depends: coq-extructures coq
    • Depends: coq-extructures coq-deriving
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-extructures.html
    • autopkgtest for coq-extructures/0.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• coq-interval (4.8.0-1 to 4.9.0-1)
  • Migration status for coq-interval (4.8.0-1 to 4.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-interval ssreflect (not considered)
    • Invalidated by dependency
    • Depends: coq-interval coq
    • Depends: coq-interval coq-bignums
    • Depends: coq-interval coquelicot
    • Depends: coq-interval flocq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-interval.html
    • autopkgtest for coq-interval/4.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• cron (3.0pl1-181 to 3.0pl1-182)
  • Migration status for cron (3.0pl1-181 to 3.0pl1-182): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cron.html
    • autopkgtest for cron/3.0pl1-182: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• golang-github-songgao-water (- to 0.0~git20200317.2b4b6d7-1)
  • Migration status for golang-github-songgao-water (- to 0.0~git20200317.2b4b6d7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kapouer@melix.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-songgao-water.html
    • autopkgtest for golang-github-songgao-water/0.0~git20200317.2b4b6d7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• mathcomp-algebra-tactics (1.1.1-2 to 1.2.2-1)
  • Migration status for mathcomp-algebra-tactics (1.1.1-2 to 1.2.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-algebra-tactics ssreflect (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): mathcomp-algebra-tactics coq-elpi
    • Depends: mathcomp-algebra-tactics coq-elpi
    • Depends: mathcomp-algebra-tactics mathcomp-zify
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-algebra-tactics.html
    • autopkgtest for mathcomp-algebra-tactics/1.2.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• mathcomp-multinomials (1.6.0-3 to 2.1.0-1)
  • Migration status for mathcomp-multinomials (1.6.0-3 to 2.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-multinomials ssreflect (not considered)
    • Invalidated by dependency
    • Depends: mathcomp-multinomials mathcomp-bigenough
    • Depends: mathcomp-multinomials mathcomp-finmap
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-multinomials.html
    • autopkgtest for mathcomp-multinomials/2.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• mathcomp-real-closed (1.1.4-2 to 2.0.0-1)
  • Migration status for mathcomp-real-closed (1.1.4-2 to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-real-closed ssreflect (not considered)
    • Invalidated by dependency
    • Depends: mathcomp-real-closed mathcomp-bigenough
    • Implicit dependency: mathcomp-real-closed coqeal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-real-closed.html
    • autopkgtest for mathcomp-real-closed/2.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• mdns-reflector (- to 0.0.1+git20230914.4b4cd3b-1)
  • Migration status for mdns-reflector (- to 0.0.1+git20230914.4b4cd3b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mdns-reflector would introduce bugs in testing: #1035719
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mdns-reflector.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• openjdk-11 (- to 11.0.22~6ea-1)
  • Migration status for openjdk-11 (- to 11.0.22~6ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-11 would introduce bugs in testing: #1023237
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for munin/2.0.74-2: amd64: Pass
    • autopkgtest for openjdk-11/blocked-on-ci-infra: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• pyregion (2.2.0-1 to 2.2.0-2)
  • Migration status for pyregion (2.2.0-1 to 2.2.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyregion.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-expectrl (- to 0.7.1-1)
  • Migration status for rust-expectrl (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-expectrl/0.7.1-1: amd64: Regression or new test ♻ , arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ , s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-expectrl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-h3 (- to 0.0.3-1)
  • Migration status for rust-h3 (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-h3/0.0.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-h3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-secret-service (- to 3.0.1-1)
  • Migration status for rust-secret-service (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-secret-service-dev/amd64 has unsatisfiable dependency
    • librust-secret-service-dev/arm64 has unsatisfiable dependency
    • librust-secret-service-dev/armel has unsatisfiable dependency
    • librust-secret-service-dev/armhf has unsatisfiable dependency
    • librust-secret-service-dev/i386 has unsatisfiable dependency
    • librust-secret-service-dev/mips64el has unsatisfiable dependency
    • librust-secret-service-dev/ppc64el has unsatisfiable dependency
    • librust-secret-service-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-secret-service.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-x11rb-protocol (- to 0.13.0-1)
  • Migration status for rust-x11rb-protocol (- to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-x11rb-protocol/0.13.0-1: amd64: Pass, arm64: Regression or new test ♻ , armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-x11rb-protocol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 12 days old (needed 5 days)
• box64 (0.2.4+dfsg-1 to 0.2.6+dfsg-2)
  • Migration status for box64 (0.2.4+dfsg-1 to 0.2.6+dfsg-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for box64/0.2.6+dfsg-2: arm64: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • 13 days old (needed 5 days)
• coq-deriving (0.1.1-1 to 0.2.0-1)
  • Migration status for coq-deriving (0.1.1-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-deriving ssreflect (not considered)
    • Invalidated by dependency
    • Depends: coq-deriving coq
    • Implicit dependency: coq-deriving coq-extructures
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-deriving.html
    • autopkgtest for coq-deriving/0.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• coq-quickchick (2.0-2 to 2.0.1-1)
  • Migration status for coq-quickchick (2.0-2 to 2.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-quickchick ssreflect (not considered)
    • Invalidated by dependency
    • Depends: coq-quickchick coq
    • Depends: coq-quickchick coq-ext-lib
    • Depends: coq-quickchick coq-simple-io
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-quickchick.html
    • autopkgtest for coq-quickchick/2.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• coq-reglang (1.1.3-4 to 1.2.0-1)
  • Migration status for coq-reglang (1.1.3-4 to 1.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-reglang ssreflect (not considered)
    • Invalidated by dependency
    • Depends: coq-reglang coq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-reglang.html
    • autopkgtest for coq-reglang/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• coq-relation-algebra (1.7.9-1 to 1.7.9-2)
  • Migration status for coq-relation-algebra (1.7.9-1 to 1.7.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-relation-algebra ssreflect (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): coq-relation-algebra coq
    • Depends: coq-relation-algebra aac-tactics
    • Depends: coq-relation-algebra coq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-relation-algebra.html
    • autopkgtest for coq-relation-algebra/1.7.9-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• coquelicot (3.3.1-1 to 3.4.0-1)
  • Migration status for coquelicot (3.3.1-1 to 3.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coquelicot/3.4.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Depends: coquelicot ssreflect
    • Implicit dependency: coquelicot coq-interval
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coquelicot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• mathcomp-bigenough (1.0.1-10 to 1.0.1-12)
  • Migration status for mathcomp-bigenough (1.0.1-10 to 1.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-bigenough/1.0.1-12/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • Depends: mathcomp-bigenough ssreflect
    • Implicit dependency: mathcomp-bigenough mathcomp-multinomials
    • Implicit dependency: mathcomp-bigenough mathcomp-real-closed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-bigenough.html
    • autopkgtest for mathcomp-bigenough/1.0.1-12: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• mathcomp-finmap (1.5.2-3 to 2.0.0-1)
  • Migration status for mathcomp-finmap (1.5.2-3 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-mathcomp-finmap/2.0.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-finmap/2.0.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • autopkgtest for mathcomp-finmap/2.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Depends: mathcomp-finmap ssreflect
    • Implicit dependency: mathcomp-finmap mathcomp-multinomials
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-finmap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• mathcomp-zify (1.3.0+1.12+8.13-1 to 1.5.0+2.0+8.16-1)
  • Migration status for mathcomp-zify (1.3.0+1.12+8.13-1 to 1.5.0+2.0+8.16-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-zify ssreflect (not considered)
    • Invalidated by dependency
    • Implicit dependency: mathcomp-zify mathcomp-algebra-tactics
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-zify.html
    • autopkgtest for mathcomp-zify/1.5.0+2.0+8.16-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• pmacct (1.7.7-1 to 1.7.8-1)
  • Migration status for pmacct (1.7.7-1 to 1.7.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pmacct unsatisfiable Build-Depends(-Arch) on s390x: libndpi-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmacct.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• squeezelite (1.9.9-1414+git20221121.dbe69eb-1 to 1.9.9-1449+git20230814.8581aba-1)
  • Migration status for squeezelite (1.9.9-1414+git20221121.dbe69eb-1 to 1.9.9-1449+git20230814.8581aba-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: squeezelite lirc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeezelite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• cmake (3.27.9-1 to 3.28.1-1)
  • Migration status for cmake (3.27.9-1 to 3.28.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cmake/3.28.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for dolfin/2019.2.0~legacy20230609.8b85e9d.ar-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for libsdl2/2.28.5+dfsg-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libthrust/blocked-on-ci-infra: amd64: Ignored failure, arm64: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for llvm-toolchain-17/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for ros2-ament-cmake/2.3.1-2: ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmake.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• coq-corn (8.16.0-3 to 8.18.0-1)
  • Migration status for coq-corn (8.16.0-3 to 8.18.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-corn coq-bignums (not considered)
    • Invalidated by dependency
    • Depends: coq-corn coq
    • Depends: coq-corn coq-math-classes
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-corn.html
    • autopkgtest for coq-corn/8.18.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• magit-forge-el (- to 0.3.2-2)
  • Migration status for magit-forge-el (- to 0.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): magit-forge-el closql-el (not considered)
    • Depends: magit-forge-el closql-el (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magit-forge-el.html
    • autopkgtest for magit-forge-el/0.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• openjdk-22 (22~22ea-1 to 22~29ea-1)
  • Migration status for openjdk-22 (22~22ea-1 to 22~29ea-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-22/22~29ea-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Updating openjdk-22 will fix bugs in testing: #1058889
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-22.html
    • Waiting for reproducibility reference results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 14 days old (needed 5 days)
• r-cran-emmeans (1.8.9+dfsg-1 to 1.9.0+dfsg-1)
  • Migration status for r-cran-emmeans (1.8.9+dfsg-1 to 1.9.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-emmeans/1.9.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for r-cran-ggeffects/1.3.2+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-emmeans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• ruby-arr-pm (- to 0.0.12-1)
  • Migration status for ruby-arr-pm (- to 0.0.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): ruby-arr-pm ruby-flores
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arr-pm.html
    • autopkgtest for ruby-arr-pm/0.0.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• ruby-dry-cli (- to 1.0.0-1)
  • Migration status for ruby-dry-cli (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dry-cli.html
    • autopkgtest for ruby-dry-cli/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• ruby-flores (- to 0.0.8-1)
  • Migration status for ruby-flores (- to 0.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-flores.html
    • autopkgtest for ruby-flores/0.0.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• ssreflect (1.17.0-1 to 2.1.0-1)
  • Migration status for ssreflect (1.17.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-mathcomp-algebra/2.1.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-algebra/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-field/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-fingroup/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-solvable/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-mathcomp-ssreflect/2.1.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • autopkgtest for coquelicot/3.3.1-1: arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for coquelicot/3.4.0-1: amd64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mathcomp-finmap/1.5.2-3: i386: Regression or new test ♻ (reference ♻)
    • autopkgtest for mathcomp-finmap/2.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ssreflect/2.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): ssreflect coq-hierarchy-builder
    • Depends: ssreflect coq
    • Depends: ssreflect coq-hierarchy-builder
    • Implicit dependency: ssreflect coq-deriving
    • Implicit dependency: ssreflect coq-extructures
    • Implicit dependency: ssreflect coq-interval
    • Implicit dependency: ssreflect coq-quickchick
    • Implicit dependency: ssreflect coq-reglang
    • Implicit dependency: ssreflect coq-relation-algebra
    • Implicit dependency: ssreflect coqeal
    • Implicit dependency: ssreflect coquelicot
    • Implicit dependency: ssreflect mathcomp-algebra-tactics
    • Implicit dependency: ssreflect mathcomp-bigenough
    • Implicit dependency: ssreflect mathcomp-finmap
    • Implicit dependency: ssreflect mathcomp-multinomials
    • Implicit dependency: ssreflect mathcomp-real-closed
    • Implicit dependency: ssreflect mathcomp-zify
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssreflect.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 14 days old (needed 5 days)
• virt-firmware (- to 23.11-1)
  • Migration status for virt-firmware (- to 23.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for virt-firmware/23.11-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by dannf, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virt-firmware.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 14 days old (needed 5 days)
• xarray-datatree (- to 0.0.13-2)
  • Migration status for xarray-datatree (- to 0.0.13-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xarray-datatree python-xarray (not considered)
    • Depends: xarray-datatree python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarray-datatree.html
    • autopkgtest for xarray-datatree/0.0.13-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• bfh-metapackages (- to 20211009-24)
  • Migration status for bfh-metapackages (- to 20211009-24): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bfh-metapackages netdata (not considered)
    • Invalidated by dependency
    • Depends: bfh-metapackages gnome-shell-extension-bluetooth-quick-connect
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bfh-metapackages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• boost-defaults (1.74.0.3 to 1.83.0.2)
  • Migration status for boost-defaults (1.74.0.3 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating boost-defaults will fix bugs in testing: #1028104
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boost-defaults.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• coq-equations (1.3-8.17-2 to 1.3-8.18-1)
  • Migration status for coq-equations (1.3-8.17-2 to 1.3-8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-equations coq (not considered)
    • Invalidated by dependency
    • Depends: coq-equations coq-hott
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-equations.html
    • autopkgtest for coq-equations/1.3-8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coq-gappa (1.5.3-1 to 1.5.4-1)
  • Migration status for coq-gappa (1.5.3-1 to 1.5.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-gappa flocq (not considered)
    • Invalidated by dependency
    • Depends: coq-gappa coq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-gappa.html
    • autopkgtest for coq-gappa/1.5.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coq-hierarchy-builder (1.4.0-6 to 1.6.0-1)
  • Migration status for coq-hierarchy-builder (1.4.0-6 to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-hierarchy-builder/1.6.0-1/amd64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/amd64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/arm64 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/arm64 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/i386 to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/i386 to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/i386 uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/ppc64el to testing makes libcoq-mathcomp-analysis/0.6.4-3+b3/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.6.0-1/ppc64el to testing makes libcoq-mathcomp-classical/0.6.4-3+b3/ppc64el uninstallable
    • Build-Depends(-Arch): coq-hierarchy-builder coq-elpi
    • Build-Depends(-Arch): coq-hierarchy-builder elpi
    • Depends: coq-hierarchy-builder coq-elpi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-hierarchy-builder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• coq-iris (4.0.0-4 to 4.1.0-1)
  • Migration status for coq-iris (4.0.0-4 to 4.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): coq-iris coq (not considered)
    • Invalidated by build-dependency
    • Depends: coq-iris coq-stdpp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-iris.html
    • autopkgtest for coq-iris/4.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coq-math-classes (8.17.0-1 to 8.18.0-1)
  • Migration status for coq-math-classes (8.17.0-1 to 8.18.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-math-classes coq-bignums (not considered)
    • Invalidated by dependency
    • Depends: coq-math-classes coq
    • Implicit dependency: coq-math-classes coq-corn
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-math-classes.html
    • autopkgtest for coq-math-classes/8.18.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coq-mtac2 (1.4+8.17-1 to 1.4+8.18-1)
  • Migration status for coq-mtac2 (1.4+8.17-1 to 1.4+8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-mtac2 coq (not considered)
    • Invalidated by dependency
    • Depends: coq-mtac2 coq-unicoq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-mtac2.html
    • autopkgtest for coq-mtac2/1.4+8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coq-simple-io (1.8.0-3 to 1.8.0-4)
  • Migration status for coq-simple-io (1.8.0-3 to 1.8.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: coq-simple-io coq-quickchick (not considered)
    • Invalidated by implicit-dependency
    • Depends: coq-simple-io coq
    • Depends: coq-simple-io coq-ext-lib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-simple-io.html
    • autopkgtest for coq-simple-io/1.8.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coq-unimath (20230420-4 to 20231010-1)
  • Migration status for coq-unimath (20230420-4 to 20231010-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-unimath coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-unimath.html
    • autopkgtest for coq-unimath/20231010-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• coqprime (8.17-1 to 8.18-1)
  • Migration status for coqprime (8.17-1 to 8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coqprime coq-bignums (not considered)
    • Invalidated by dependency
    • Depends: coqprime coq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coqprime.html
    • autopkgtest for coqprime/8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• fprintd (- to 1.94.2-3)
  • Migration status for fprintd (- to 1.94.2-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fprintd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 15 days old (needed 5 days)
• gitaly (- to 16.4.4+ds1-4)
  • Migration status for gitaly (- to 16.4.4+ds1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gitlab-common/amd64 has unsatisfiable dependency
    • gitlab-common/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gitaly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• golang-github-cronokirby-saferith (- to 0.33.0-2)
  • Migration status for golang-github-cronokirby-saferith (- to 0.33.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-cronokirby-saferith/0.33.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cronokirby-saferith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• golang-github-henrybear327-go-proton-api (- to 1.0.0-3)
  • Migration status for golang-github-henrybear327-go-proton-api (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-henrybear327-go-proton-api/1.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-henrybear327-go-proton-api golang-github-protonmail-gluon
    • Build-Depends(-Arch): golang-github-henrybear327-go-proton-api golang-github-protonmail-go-srp
    • Depends: golang-github-henrybear327-go-proton-api golang-github-protonmail-gluon
    • Depends: golang-github-henrybear327-go-proton-api golang-github-protonmail-go-srp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-go-proton-api.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2)
  • Migration status for golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-henrybear327-proton-api-bridge/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-proton-api-bridge.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• golang-github-protonmail-gluon (- to 0.17.0-2)
  • Migration status for golang-github-protonmail-gluon (- to 0.17.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-gluon/0.17.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-gluon.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• golang-github-protonmail-go-srp (- to 0.0.7+ds-2)
  • Migration status for golang-github-protonmail-go-srp (- to 0.0.7+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-go-srp/0.0.7+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-protonmail-go-srp golang-github-cronokirby-saferith
    • Depends: golang-github-protonmail-go-srp golang-github-cronokirby-saferith
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-go-srp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• pm-utils (- to 1.4.1-20)
  • Migration status for pm-utils (- to 1.4.1-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by iwj, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pm-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• progress-linux-metapackages (- to 20221002-12)
  • Migration status for progress-linux-metapackages (- to 20221002-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: progress-linux-metapackages netdata (not considered)
    • Invalidated by dependency
    • Depends: progress-linux-metapackages gnome-shell-extension-bluetooth-quick-connect
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• qtilitools (- to 0.1.2-1)
  • Migration status for qtilitools (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtilitools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• satpy (- to 0.46.0-1)
  • Migration status for satpy (- to 0.46.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): satpy python-xarray (not considered)
    • Depends: satpy python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): satpy behave
    • Build-Depends(-Arch): satpy pint-xarray
    • Build-Depends(-Arch): satpy pycoast
    • Build-Depends(-Arch): satpy pydecorate
    • Build-Depends(-Arch): satpy pygac
    • Build-Depends(-Arch): satpy pyninjotiff
    • Build-Depends(-Arch): satpy pyorbital
    • Build-Depends(-Arch): satpy pyresample
    • Build-Depends(-Arch): satpy pyspectral
    • Build-Depends(-Arch): satpy python-geotiepoints
    • Build-Depends(-Arch): satpy python-rioxarray
    • Build-Depends(-Arch): satpy pytroll-schedule
    • Build-Depends(-Arch): satpy trollimage
    • Build-Depends(-Arch): satpy xarray-datatree
    • Depends: satpy pyorbital
    • Depends: satpy pyresample
    • Depends: satpy trollimage
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/satpy.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for satpy/0.46.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• slepc4py (3.18.3-1 to 3.19.2-1)
  • Migration status for slepc4py (3.18.3-1 to 3.19.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slepc4py slepc (not considered)
    • Depends: slepc4py slepc (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): slepc4py petsc
    • Build-Depends(-Arch): slepc4py petsc4py
    • Depends: slepc4py petsc
    • Depends: slepc4py petsc4py
    • Implicit dependency: slepc4py dolfin
    • Implicit dependency: slepc4py fenics-dolfinx
  • Additional info:
    • Updating slepc4py will fix bugs in testing: #1057863
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slepc4py.html
    • autopkgtest for slepc4py/3.19.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• yade (- to 2023.02a-8)
  • Migration status for yade (- to 2023.02a-8): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yade.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• aac-tactics (8.17.0-3 to 8.18.0-1)
  • Migration status for aac-tactics (8.17.0-3 to 8.18.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: aac-tactics coq-relation-algebra (not considered)
    • Invalidated by implicit-dependency
    • Depends: aac-tactics coq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aac-tactics.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• asterisk (- to 1:20.5.2~dfsg+~cs6.13.40431414-1)
  • Migration status for asterisk (- to 1:20.5.2~dfsg+~cs6.13.40431414-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk would introduce bugs in testing: #1031046, #1059303
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:20.5.2~dfsg+~cs6.13.40431414-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq (8.17.0+dfsg-1 to 8.18.0+dfsg-1)
  • Migration status for coq (8.17.0+dfsg-1 to 8.18.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coq/8.18.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for coquelicot/3.3.1-1: arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for coquelicot/3.4.0-1: amd64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mathcomp-analysis/0.6.4-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for mathcomp-finmap/1.5.2-3: i386: Regression or new test ♻ (reference ♻)
    • autopkgtest for mathcomp-finmap/2.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Implicit dependency: coq aac-tactics
    • Implicit dependency: coq coq-bignums
    • Implicit dependency: coq coq-corn
    • Implicit dependency: coq coq-deriving
    • Implicit dependency: coq coq-dpdgraph
    • Implicit dependency: coq coq-elpi
    • Implicit dependency: coq coq-equations
    • Implicit dependency: coq coq-ext-lib
    • Implicit dependency: coq coq-extructures
    • Implicit dependency: coq coq-gappa
    • Implicit dependency: coq coq-hammer
    • Implicit dependency: coq coq-hott
    • Implicit dependency: coq coq-interval
    • Implicit dependency: coq coq-libhyps
    • Implicit dependency: coq coq-math-classes
    • Implicit dependency: coq coq-menhirlib
    • Implicit dependency: coq coq-mtac2
    • Implicit dependency: coq coq-quickchick
    • Implicit dependency: coq coq-record-update
    • Implicit dependency: coq coq-reduction-effects
    • Implicit dependency: coq coq-reglang
    • Implicit dependency: coq coq-relation-algebra
    • Implicit dependency: coq coq-simple-io
    • Implicit dependency: coq coq-stdpp
    • Implicit dependency: coq coq-unicoq
    • Implicit dependency: coq coq-unimath
    • Implicit dependency: coq coqeal
    • Implicit dependency: coq coqprime
    • Implicit dependency: coq flocq
    • Implicit dependency: coq ott
    • Implicit dependency: coq paramcoq
    • Implicit dependency: coq ssreflect
  • Additional info:
    • Updating coq will fix bugs in testing: #1056062
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • No reference result, but not reproducibility on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • 16 days old (needed 5 days)
• coq-bignums (8.17.0-3 to 9.0.0+coq8.18-1)
  • Migration status for coq-bignums (8.17.0-3 to 9.0.0+coq8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: coq-bignums coqeal (not considered)
    • Invalidated by implicit-dependency
    • Depends: coq-bignums coq
    • Implicit dependency: coq-bignums coq-corn
    • Implicit dependency: coq-bignums coq-interval
    • Implicit dependency: coq-bignums coq-math-classes
    • Implicit dependency: coq-bignums coqprime
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-bignums.html
    • autopkgtest for coq-bignums/9.0.0+coq8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-dpdgraph (1.0+8.17-1 to 1.0+8.18-1)
  • Migration status for coq-dpdgraph (1.0+8.17-1 to 1.0+8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): coq-dpdgraph coq (not considered)
    • Depends: coq-dpdgraph coq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-dpdgraph.html
    • autopkgtest for coq-dpdgraph/1.0+8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-ext-lib (0.11.8-1 to 0.12.0-1)
  • Migration status for coq-ext-lib (0.11.8-1 to 0.12.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: coq-ext-lib coq-quickchick (not considered)
    • Invalidated by implicit-dependency
    • Depends: coq-ext-lib coq
    • Implicit dependency: coq-ext-lib coq-simple-io
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-ext-lib.html
    • autopkgtest for coq-ext-lib/0.12.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-hammer (1.3.2+8.17-1 to 1.3.2+8.18-1)
  • Migration status for coq-hammer (1.3.2+8.17-1 to 1.3.2+8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-hammer coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-hammer.html
    • autopkgtest for coq-hammer/1.3.2+8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-hott (8.18-1 to 8.18-3)
  • Migration status for coq-hott (8.18-1 to 8.18-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-hott coq (not considered)
    • Invalidated by dependency
    • Implicit dependency: coq-hott coq-equations
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-hott.html
    • autopkgtest for coq-hott/8.18-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-libhyps (2.0.6-3 to 2.0.8-1)
  • Migration status for coq-libhyps (2.0.6-3 to 2.0.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-libhyps coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-libhyps.html
    • autopkgtest for coq-libhyps/2.0.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-menhirlib (20230608+ds-1 to 20230608+ds-2)
  • Migration status for coq-menhirlib (20230608+ds-1 to 20230608+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-menhirlib coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-menhirlib.html
    • autopkgtest for coq-menhirlib/20230608+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-record-update (0.3.2-1 to 0.3.3-1)
  • Migration status for coq-record-update (0.3.2-1 to 0.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-record-update coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-record-update.html
    • autopkgtest for coq-record-update/0.3.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-reduction-effects (0.1.4-4 to 0.1.5-1)
  • Migration status for coq-reduction-effects (0.1.4-4 to 0.1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): coq-reduction-effects coq (not considered)
    • Depends: coq-reduction-effects coq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-reduction-effects.html
    • autopkgtest for coq-reduction-effects/0.1.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-stdpp (1.8.0-4 to 1.9.0-1)
  • Migration status for coq-stdpp (1.8.0-4 to 1.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): coq-stdpp coq (not considered)
    • Depends: coq-stdpp coq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: coq-stdpp coq-iris
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-stdpp.html
    • autopkgtest for coq-stdpp/1.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• coq-unicoq (1.6-8.17-1 to 1.6-8.18-1)
  • Migration status for coq-unicoq (1.6-8.17-1 to 1.6-8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): coq-unicoq coq (not considered)
    • Depends: coq-unicoq coq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: coq-unicoq coq-mtac2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-unicoq.html
    • autopkgtest for coq-unicoq/1.6-8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• firefox (- to 121.0-2)
  • Migration status for firefox (- to 121.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1017919, #817954, #992263, #993659
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 16 days old (needed 5 days)
• flocq (4.1.1-1 to 4.1.3-1)
  • Migration status for flocq (4.1.1-1 to 4.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: flocq coq-interval (not considered)
    • Invalidated by implicit-dependency
    • Depends: flocq coq
    • Implicit dependency: flocq coq-gappa
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flocq.html
    • autopkgtest for flocq/4.1.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• ohcount (- to 4.0.0-4)
  • Migration status for ohcount (- to 4.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ohcount would introduce bugs in testing: #1051900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohcount.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• ott (0.33+ds-1 to 0.33+ds-2)
  • Migration status for ott (0.33+ds-1 to 0.33+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ott coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ott.html
    • autopkgtest for ott/0.33+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• paramcoq (1.1.3+coq8.17-2 to 1.1.3+coq8.18-1)
  • Migration status for paramcoq (1.1.3+coq8.17-2 to 1.1.3+coq8.18-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: paramcoq coqeal (not considered)
    • Invalidated by implicit-dependency
    • Depends: paramcoq coq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paramcoq.html
    • autopkgtest for paramcoq/1.1.3+coq8.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• proftpd-mod-proxy (0.9.2-1 to 0.9.3-1)
  • Migration status for proftpd-mod-proxy (0.9.2-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-mod-proxy proftpd-dfsg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proftpd-mod-proxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 2 days)
• prometheus-blackbox-exporter (0.24.0-1 to 0.24.0-2)
  • Migration status for prometheus-blackbox-exporter (0.24.0-1 to 0.24.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: prometheus-blackbox-exporter golang-golang-x-oauth2 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Updating prometheus-blackbox-exporter will fix bugs in testing: #1058505
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-blackbox-exporter.html
    • autopkgtest for prometheus-blackbox-exporter/0.24.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• python-apt (2.7.0 to 2.7.4)
  • Migration status for python-apt (2.7.0 to 2.7.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-apt/2.7.4: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating python-apt will fix bugs in testing: #1058118
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-apt.html
    • Reproducible on armhf - info ♻
    • 16 days old (needed 5 days)
• r-cran-ggally (2.1.2-2 to 2.2.0-1)
  • Migration status for r-cran-ggally (2.1.2-2 to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-ggally would introduce bugs in testing: #1059385
    • autopkgtest for r-cran-ggally/2.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ggally.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• gmsh (4.8.4+ds2-3 to 4.11.1+ds1-1)
  • Migration status for gmsh (4.8.4+ds2-3 to 4.11.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gmsh/4.11.1+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pygmsh/7.1.17-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by gladky.anton@gmail.com
    • Not built on buildd: arch all binaries uploaded by gladky.anton@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmsh.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• golang-github-google-go-pkcs11 (- to 0.3.0+dfsg-1)
  • Migration status for golang-github-google-go-pkcs11 (- to 0.3.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-google-go-pkcs11/0.3.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by dparsons, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-go-pkcs11.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• mame (- to 0.261+dfsg.1-1)
  • Migration status for mame (- to 0.261+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mame would introduce bugs in testing: #983507
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mame.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• nitime (0.10.2-1 to 0.10.2-2)
  • Migration status for nitime (0.10.2-1 to 0.10.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nitime/0.10.2-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nitime.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 17 days old (needed 5 days)
• openstack-cluster-installer (- to 42.3.6)
  • Migration status for openstack-cluster-installer (- to 42.3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/openstack-cluster-installer.html
    • Depends: openstack-cluster-installer openstack-meta-packages
    • Depends: openstack-cluster-installer puppetserver
  • Additional info:
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 17 days old (needed 5 days)
• petsc (3.18.6+dfsg1-1 to 3.19.6+dfsg1-1)
  • Migration status for petsc (3.18.6+dfsg1-1 to 3.19.6+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: petsc slepc (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: petsc dolfin
    • Implicit dependency: petsc fenics-dolfinx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petsc.html
    • autopkgtest for petsc/3.19.6+dfsg1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• psychopy (- to 2023.2.4+dfsg-1)
  • Migration status for psychopy (- to 2023.2.4+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): psychopy python-questplus (not considered)
    • Depends: psychopy python-questplus (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psychopy.html
    • autopkgtest for psychopy/2023.2.4+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• virtualbox-ext-pack (- to 7.0.12-3)
  • Migration status for virtualbox-ext-pack (- to 7.0.12-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • virtualbox-ext-pack/arm64 has unsatisfiable dependency
    • Depends: virtualbox-ext-pack virtualbox
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 17 days old (needed 5 days)
• binutils-mingw-w64 (11+nmu1 to 11.2)
  • Migration status for binutils-mingw-w64 (11+nmu1 to 11.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating binutils-mingw-w64 will fix bugs in testing: #1057728
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-mingw-w64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• cmocka (1.1.5-2.1 to 1.1.7-2)
  • Migration status for cmocka (1.1.5-2.1 to 1.1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nss-wrapper/1.1.15-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for priv-wrapper/1.0.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for resolv-wrapper/1.1.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for uid-wrapper/1.3.0-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmocka.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• e-antic (1.3.0+ds1-1 to 2.0.0+ds1-2)
  • Migration status for e-antic (1.3.0+ds1-1 to 2.0.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for normaliz/3.10.1+ds-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Depends: e-antic flint
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/e-antic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• macaulay2 (1.22+ds-3 to 1.22+ds-5)
  • Migration status for macaulay2 (1.22+ds-3 to 1.22+ds-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: macaulay2 flint (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macaulay2.html
    • autopkgtest for macaulay2/1.22+ds-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 18 days old (needed 2 days)
• proftpd-dfsg (1.3.8.a+dfsg-1 to 1.3.8.b+dfsg-1)
  • Migration status for proftpd-dfsg (1.3.8.a+dfsg-1 to 1.3.8.b+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-autohost/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-case/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-clamav/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-counter/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-fsync/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-geoip2/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-kafka/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-msg/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-proxy
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-sftp-ldap/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-statsd/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-tar/s390x
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/amd64
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/arm64
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/armel
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/armhf
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/i386
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/mips64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/ppc64el
    • Implicit dependency: proftpd-dfsg proftpd-mod-vroot/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proftpd-dfsg.html
    • autopkgtest for proftpd-dfsg/1.3.8.b+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility reference results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • Required age is not allowed to drop below 2 days
    • 18 days old (needed 2 days)
• pyocd (0.13.1+dfsg-3 to 0.36.0-1)
  • Migration status for pyocd (0.13.1+dfsg-3 to 0.36.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for valinor/1.1.4-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyocd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• rust-heed (- to 0.20.0~alpha.9-1)
  • Migration status for rust-heed (- to 0.20.0~alpha.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-heed/0.20.0~alpha.9-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-heed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 18 days old (needed 5 days)
• elenv (- to 0.1.0+git20231106.e7619ff-1)
  • Migration status for elenv (- to 0.1.0+git20231106.e7619ff-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by happyaron.xu@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elenv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 19 days old (needed 5 days)
• endesive (- to 2.16+dfsg-1)
  • Migration status for endesive (- to 2.16+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sophieb, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endesive.html
    • autopkgtest for endesive/2.16+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• freecad (0.20.2+dfsg1-10 to 0.21.2+dfsg1-1)
  • Migration status for freecad (0.20.2+dfsg1-10 to 0.21.2+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for freecad/0.21.2+dfsg1-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecad.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 19 days old (needed 5 days)
• greenbone-security-assistant (- to 22.9.1-1)
  • Migration status for greenbone-security-assistant (- to 22.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating greenbone-security-assistant would introduce bugs in testing: #1029780
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 19 days old (needed 5 days)
• liquidsoap (- to 2.2.2-2)
  • Migration status for liquidsoap (- to 2.2.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): liquidsoap pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): liquidsoap ocaml-duppy
    • Build-Depends(-Arch): liquidsoap ocaml-lastfm
    • Build-Depends(-Arch): liquidsoap ocaml-mm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/liquidsoap.html
    • autopkgtest for liquidsoap/2.2.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• node-corepack (- to 0.19.0+dfsg+~cs4.2.0-2)
  • Migration status for node-corepack (- to 0.19.0+dfsg+~cs4.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-corepack/0.19.0+dfsg+~cs4.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-corepack.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 19 days old (needed 5 days)
• normaliz (3.10.1+ds-3 to 3.10.1+ds-4)
  • Migration status for normaliz (3.10.1+ds-3 to 3.10.1+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: normaliz flint (not considered)
    • Invalidated by dependency
    • Depends: normaliz e-antic
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/normaliz.html
    • autopkgtest for normaliz/3.10.1+ds-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• openvas-scanner (- to 22.7.9-1)
  • Migration status for openvas-scanner (- to 22.7.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openvas-scanner gvm-libs (not considered)
    • Depends: openvas-scanner gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvas-scanner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• python-asyncclick (- to 8.1.7.0+async-2)
  • Migration status for python-asyncclick (- to 8.1.7.0+async-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asyncclick.html
    • autopkgtest for python-asyncclick/8.1.7.0+async-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• rust-scraper (- to 0.18.1-1)
  • Migration status for rust-scraper (- to 0.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-scraper-dev/amd64 has unsatisfiable dependency
    • Updating rust-scraper would introduce bugs in testing: #1059034
    • rust-scraper unsatisfiable Build-Depends(-Arch) on amd64: librust-ego-tree-0.6+default-dev (>= 0.6.2-~~)
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
    • Build-Depends(-Arch): rust-scraper rust-ahash
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-scraper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 19 days old (needed 5 days)
• stlink (- to 1.7.0+ds-2)
  • Migration status for stlink (- to 1.7.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stlink would introduce bugs in testing: #1041060
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stlink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• xraylarch (- to 0.9.74+ds1-1)
  • Migration status for xraylarch (- to 0.9.74+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xraylarch python-mp-api (not considered)
    • Depends: xraylarch python-mp-api (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xraylarch pyfai
    • Build-Depends(-Arch): xraylarch pymatgen
    • Depends: xraylarch pyfai
    • Depends: xraylarch pymatgen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xraylarch.html
    • autopkgtest for xraylarch/0.9.74+ds1-1: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• hurd (- to 1:0.9.git20231217-1)
  • Migration status for hurd (- to 1:0.9.git20231217-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #650080, #838244, #943307
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
    • Not touching package due to block request by freeze (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.html
    • 20 days old (needed 5 days)
• appstream-generator (- to 0.9.1-1)
  • Migration status for appstream-generator (- to 0.9.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-generator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• bpfcc (0.26.0+ds-1 to 0.29.1+ds-1)
  • Migration status for bpfcc (0.26.0+ds-1 to 0.29.1+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpfcc.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 21 days old (needed 5 days)
• madfuload (1.2-4.2 to 1.2-5)
  • Migration status for madfuload (1.2-4.2 to 1.2-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 21 days old (needed 5 days)
• pymupdf (1.22.5+ds1-1 to 1.23.7+ds1-1)
  • Migration status for pymupdf (1.22.5+ds1-1 to 1.23.7+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for plakativ/0.5.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pymupdf/1.23.7+ds1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Updating pymupdf will fix bugs in testing: #1057402
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymupdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• python-pyaml-env (- to 1.2.1-1)
  • Migration status for python-pyaml-env (- to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyaml-env.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 21 days old (needed 5 days)
• rust-ntpd (- to 1.1.0-3)
  • Migration status for rust-ntpd (- to 1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ntpd/1.1.0-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-ntpd rust-ntp-os-clock
    • Build-Depends(-Arch): rust-ntpd rust-ntp-proto
    • Build-Depends(-Arch): rust-ntpd rust-ntp-udp
    • Depends: rust-ntpd rust-ntp-os-clock
    • Depends: rust-ntpd rust-ntp-proto
    • Depends: rust-ntpd rust-ntp-udp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntpd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• prometheus-nginx-exporter (0.11.0-1 to 1.0.0-1)
  • Migration status for prometheus-nginx-exporter (0.11.0-1 to 1.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: prometheus-nginx-exporter golang-golang-x-oauth2 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-nginx-exporter.html
    • autopkgtest for prometheus-nginx-exporter/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• pyferret (7.6.5-4 to 7.6.5-5)
  • Migration status for pyferret (7.6.5-4 to 7.6.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyferret would introduce bugs in testing: #1058888
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for pyferret/7.6.5-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Updating pyferret will fix bugs in testing: #1058030
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyferret.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 23 days old (needed 5 days)
• rust-ntp-os-clock (- to 1.1.0-1)
  • Migration status for rust-ntp-os-clock (- to 1.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ntp-os-clock rust-ntp-proto (not considered)
    • Depends: rust-ntp-os-clock rust-ntp-proto (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntp-os-clock.html
    • autopkgtest for rust-ntp-os-clock/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• rust-ntp-proto (- to 1.1.0-1)
  • Migration status for rust-ntp-proto (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ntp-proto/1.1.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntp-proto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• rust-ntp-udp (- to 1.1.0-1)
  • Migration status for rust-ntp-udp (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ntp-udp would introduce bugs in testing: #1056028
    • autopkgtest for rust-ntp-udp/1.1.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-ntp-udp rust-ntp-proto
    • Depends: rust-ntp-udp rust-ntp-proto
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntp-udp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• sarsen (- to 0.9.3+ds-3)
  • Migration status for sarsen (- to 0.9.3+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sarsen python-xarray (not considered)
    • Depends: sarsen python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): sarsen flox
    • Build-Depends(-Arch): sarsen python-rioxarray
    • Build-Depends(-Arch): sarsen xarray-sentinel
    • Depends: sarsen flox
    • Depends: sarsen python-rioxarray
    • Depends: sarsen xarray-sentinel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sarsen.html
    • autopkgtest for sarsen/0.9.3+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• xarray-safe-rcm (- to 2023.06.1-3)
  • Migration status for xarray-safe-rcm (- to 2023.06.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xarray-safe-rcm python-xarray (not considered)
    • Depends: xarray-safe-rcm python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xarray-safe-rcm python-rioxarray
    • Build-Depends(-Arch): xarray-safe-rcm xarray-datatree
    • Depends: xarray-safe-rcm python-rioxarray
    • Depends: xarray-safe-rcm xarray-datatree
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarray-safe-rcm.html
    • autopkgtest for xarray-safe-rcm/2023.06.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• xarray-sentinel (- to 0.9.5+ds-3)
  • Migration status for xarray-sentinel (- to 0.9.5+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xarray-sentinel python-xarray (not considered)
    • Depends: xarray-sentinel python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xarray-sentinel python-rioxarray
    • Depends: xarray-sentinel python-rioxarray
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarray-sentinel.html
    • autopkgtest for xarray-sentinel/0.9.5+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• xradarsat2 (- to 2023.06.13+ds-3)
  • Migration status for xradarsat2 (- to 2023.06.13+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xradarsat2 python-xarray (not considered)
    • Depends: xradarsat2 python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xradarsat2 python-rioxarray
    • Build-Depends(-Arch): xradarsat2 xarray-datatree
    • Depends: xradarsat2 python-rioxarray
    • Depends: xradarsat2 xarray-datatree
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xradarsat2.html
    • autopkgtest for xradarsat2/2023.06.13+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• redland-bindings (1.0.17.1+dfsg-4 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings (1.0.17.1+dfsg-4 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • removing python3-librdf/1.0.17.1+dfsg-4+b2/amd64 from testing makes mozilla-devscripts/0.54.2+nmu1/amd64 uninstallable
    • removing python3-librdf/1.0.17.1+dfsg-4+b2/arm64 from testing makes mozilla-devscripts/0.54.2+nmu1/arm64 uninstallable
  • Additional info:
    • Updating redland-bindings will fix bugs in testing: #1055550
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redland-bindings.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• terminado (0.17.1-1 to 0.18.0-1)
  • Migration status for terminado (0.17.1-1 to 0.18.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for terminado/0.18.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terminado.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• cinder (- to 2:23.0.0-4)
  • Migration status for cinder (- to 2:23.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cinder/2:23.0.0-4: amd64: Regression or new test ♻ , arm64: Pass, armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Depends: cinder thin-provisioning-tools
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cinder.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1)
  • Migration status for fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fapolicyd would introduce bugs in testing: #1037547
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fapolicyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• gitlab-shell (14.20.0+ds1-2 to 14.23.0+ds1-1)
  • Migration status for gitlab-shell (14.20.0+ds1-2 to 14.23.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gitlab-shell.html
    • Build-Depends(-Arch): gitlab-shell gitaly
    • Built-Using: gitlab-shell gitaly
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• i2pd (2.45.1-1 to 2.49.0-1)
  • Migration status for i2pd (2.45.1-1 to 2.49.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2pd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• mistune (2.0.4-2 to 3.0.2-1)
  • Migration status for mistune (2.0.4-2 to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mistune/3.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-schema-salad/8.4.20230808163024-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mistune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• prometheus-snmp-exporter (0.24.1-2 to 0.25.0-1)
  • Migration status for prometheus-snmp-exporter (0.24.1-2 to 0.25.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: prometheus-snmp-exporter golang-golang-x-oauth2 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-snmp-exporter.html
    • autopkgtest for prometheus-snmp-exporter/0.25.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 25 days old (needed 2 days)
• python-xarray (- to 2023.12.0-1)
  • Migration status for python-xarray (- to 2023.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-xarray/2023.12.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): python-xarray cfgrib
    • Build-Depends(-Arch): python-xarray python-sparse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xarray.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 days old (needed 5 days)
• takari-polyglot-maven (- to 0.4.11-3)
  • Migration status for takari-polyglot-maven (- to 0.4.11-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): takari-polyglot-maven jruby (not considered)
    • Depends: takari-polyglot-maven jruby (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): takari-polyglot-maven jruby-maven-plugins
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/takari-polyglot-maven.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• vitrage (11.0.0-1 to 11.0.0-2)
  • Migration status for vitrage (11.0.0-1 to 11.0.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating vitrage will fix bugs in testing: #1058159
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vitrage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• compyle (0.8.1-4 to 0.8.1-6)
  • Migration status for compyle (0.8.1-4 to 0.8.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for compyle/0.8.1-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pysph/1.0~b1-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating compyle will fix bugs in testing: #1060151
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/compyle.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• flint (2.9.0-5 to 3.0.1-1)
  • Migration status for flint (2.9.0-5 to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flint would introduce bugs in testing: #1058580
    • autopkgtest for antic/0.2.5+ds-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for flint/3.0.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Not built on buildd: arch amd64 binaries uploaded by julien.puydt@laposte.net
    • Not built on buildd: arch all binaries uploaded by julien.puydt@laposte.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flint.html
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 26 days old (needed 5 days)
• path.py (16.7.1-1 to 16.9.0-1)
  • Migration status for path.py (16.7.1-1 to 16.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for path.py/16.9.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/path.py.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• python-anyio (3.7.0-1 to 4.1.0-1)
  • Migration status for python-anyio (3.7.0-1 to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for httpx/0.23.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-anyio/4.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-watchgod/0.8.2-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anyio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• pytorch-geometric (- to 2.4.0-1)
  • Migration status for pytorch-geometric (- to 2.4.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): pytorch-geometric python-ase
    • Build-Depends(-Arch): pytorch-geometric rdkit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-geometric.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 26 days old (needed 5 days)
• pandoc-sidenote (- to 0.23.0-1)
  • Migration status for pandoc-sidenote (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pandoc-sidenote would introduce bugs in testing: #1055980
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandoc-sidenote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• ruby-sanitize (- to 6.0.2-1)
  • Migration status for ruby-sanitize (- to 6.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by abhijith@openmailbox.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-sanitize.html
    • autopkgtest for ruby-sanitize/6.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• aerc (0.15.2-2 to 0.16.0-1)
  • Migration status for aerc (0.15.2-2 to 0.16.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: aerc golang-golang-x-oauth2 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aerc.html
    • autopkgtest for aerc/0.16.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• clojure-mode (- to 5.18.1-1)
  • Migration status for clojure-mode (- to 5.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for clojure-mode/5.18.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clojure-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• flask-security (- to 5.3.2-1)
  • Migration status for flask-security (- to 5.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-flask-security/amd64 has unsatisfiable dependency
    • python3-flask-security/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/flask-security.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• libextractor (1:1.11-8 to 1:1.13-1)
  • Migration status for libextractor (1:1.11-8 to 1:1.13-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for libextractor/1:1.13-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libextractor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• maradns (- to 2.0.13-1.6)
  • Migration status for maradns (- to 2.0.13-1.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating maradns would introduce bugs in testing: #1024561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maradns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• mintpy (- to 1.5.3-2)
  • Migration status for mintpy (- to 1.5.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mintpy/1.5.3-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): mintpy pyfftw
    • Build-Depends(-Arch): mintpy pyresample
    • Depends: mintpy pyresample
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mintpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• pydecorate (- to 0.4.0-2)
  • Migration status for pydecorate (- to 0.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pydecorate trollimage (not considered)
    • Depends: pydecorate trollimage (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydecorate.html
    • autopkgtest for pydecorate/0.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• pyorbital (- to 1.8.0-3)
  • Migration status for pyorbital (- to 1.8.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyorbital python-xarray (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyorbital.html
    • autopkgtest for pyorbital/1.8.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• pyresample (- to 1.27.1-3)
  • Migration status for pyresample (- to 1.27.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyresample python-xarray (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyresample.html
    • autopkgtest for pyresample/1.27.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• pytroll-schedule (- to 0.7.0-3)
  • Migration status for pytroll-schedule (- to 0.7.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytroll-schedule pyresample (not considered)
    • Depends: pytroll-schedule pyresample (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): pytroll-schedule pyorbital
    • Depends: pytroll-schedule pyorbital
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytroll-schedule.html
    • autopkgtest for pytroll-schedule/0.7.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• emacs-posframe (1.1.7-3 to 1.4.2-1)
  • Migration status for emacs-posframe (1.1.7-3 to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by rul@kalgan.cc, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-posframe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• golang-github-inetaf-tcpproxy (- to 0.0~git20231102.2862066-1)
  • Migration status for golang-github-inetaf-tcpproxy (- to 0.0~git20231102.2862066-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by siretart, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by siretart
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-inetaf-tcpproxy.html
    • autopkgtest for golang-github-inetaf-tcpproxy/0.0~git20231102.2862066-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• jruby-mavengem (- to 2.0.1-1)
  • Migration status for jruby-mavengem (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lavamind, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): jruby-mavengem jruby
    • Build-Depends(-Arch): jruby-mavengem jruby-maven-plugins
    • Depends: jruby-mavengem jruby
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-mavengem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• os-autoinst (4.6.1674476646.0798a03c-6 to 4.6.1699947509.970d0609-1)
  • Migration status for os-autoinst (4.6.1674476646.0798a03c-6 to 4.6.1699947509.970d0609-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating os-autoinst will fix bugs in testing: #1054776
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/os-autoinst.html
    • 29 days old (needed 5 days)
• pint-xarray (- to 0.3-3)
  • Migration status for pint-xarray (- to 0.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pint-xarray python-xarray (not considered)
    • Depends: pint-xarray python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pint-xarray.html
    • autopkgtest for pint-xarray/0.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• pygac (- to 1.7.2-2)
  • Migration status for pygac (- to 1.7.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pygac python-geotiepoints (not considered)
    • Depends: pygac python-geotiepoints (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): pygac pyorbital
    • Depends: pygac pyorbital
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pygac.html
    • autopkgtest for pygac/1.7.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• pymap3d (- to 3.0.1-4)
  • Migration status for pymap3d (- to 3.0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pymap3d python-xarray (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymap3d.html
    • autopkgtest for pymap3d/3.0.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• pyninjotiff (- to 0.4.0-3)
  • Migration status for pyninjotiff (- to 0.4.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyninjotiff python-xarray (not considered)
    • Depends: pyninjotiff python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): pyninjotiff pyresample
    • Build-Depends(-Arch): pyninjotiff trollimage
    • Depends: pyninjotiff pyresample
    • Depends: pyninjotiff trollimage
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyninjotiff.html
    • autopkgtest for pyninjotiff/0.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• trafficserver (- to 9.2.3+ds-1+deb12u1)
  • Migration status for trafficserver (- to 9.2.3+ds-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: trafficserver -> libyaml-cpp0.7/0.7.0+dfsg-8+b1/amd64
    • Impossible Depends: trafficserver -> libyaml-cpp0.7/0.7.0+dfsg-8+b1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 29 days old (needed 5 days)
• xarray-safe-s1 (- to 2023.12.07-1)
  • Migration status for xarray-safe-s1 (- to 2023.12.07-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xarray-safe-s1 python-xarray (not considered)
    • Depends: xarray-safe-s1 python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xarray-safe-s1 python-rioxarray
    • Build-Depends(-Arch): xarray-safe-s1 xarray-datatree
    • Depends: xarray-safe-s1 python-rioxarray
    • Depends: xarray-safe-s1 xarray-datatree
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarray-safe-s1.html
    • autopkgtest for xarray-safe-s1/2023.12.07-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• doxygen (1.9.4-4 to 1.9.8+ds-2)
  • Migration status for doxygen (1.9.4-4 to 1.9.8+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for breathe/4.35.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for doxygen/1.9.8+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating doxygen will fix bugs in testing: #1053495
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doxygen.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • No reference result, but not reproducibility on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • 30 days old (needed 5 days)
• emacs-wgrep (3.0.0-1 to 3.0.0-2)
  • Migration status for emacs-wgrep (3.0.0-1 to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for emacs-wgrep/3.0.0-2: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
  • Additional info:
    • Updating emacs-wgrep will fix bugs in testing: #1057559
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-wgrep.html
    • 30 days old (needed 5 days)
• gbrowse (2.56+dfsg-11 to 2.56+dfsg-12)
  • Migration status for gbrowse (2.56+dfsg-11 to 2.56+dfsg-12): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for gbrowse/2.56+dfsg-12: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbrowse.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 30 days old (needed 5 days)
• php-symfony-mercure-bundle (- to 0.3.8-1)
  • Migration status for php-symfony-mercure-bundle (- to 0.3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-symfony-mercure-bundle php-lcobucci-jwt (not considered)
    • Depends: php-symfony-mercure-bundle php-lcobucci-jwt (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-symfony-mercure-bundle.html
    • autopkgtest for php-symfony-mercure-bundle/0.3.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• python-flake8 (5.0.4-4 to 6.1.0-1)
  • Migration status for python-flake8 (5.0.4-4 to 6.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-flake8 pyflakes (not considered)
    • Depends: python-flake8 pyflakes (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating python-flake8 will fix bugs in testing: #1057968
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flake8.html
    • autopkgtest for python-flake8/6.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• golang-golang-x-oauth2 (0.4.0-1 to 0.15.0-1)
  • Migration status for golang-golang-x-oauth2 (0.4.0-1 to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-golang-x-oauth2/0.15.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for golang-google-api/0.61.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-golang-x-oauth2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• pyflakes (2.5.0-1 to 3.1.0-1)
  • Migration status for pyflakes (2.5.0-1 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyflakes would introduce bugs in testing: #1058335
    • autopkgtest for pyflakes/3.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-apt/2.7.0: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating pyflakes will fix bugs in testing: #1042339
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyflakes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• ruby-pry-byebug (3.9.0-1 to 3.10.1-1)
  • Migration status for ruby-pry-byebug (3.9.0-1 to 3.10.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-pry-byebug pry (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating ruby-pry-byebug will fix bugs in testing: #1054737
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-pry-byebug.html
    • autopkgtest for ruby-pry-byebug/3.10.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 31 days old (needed 2 days)
• libei (1.1.0-1 to 1.2.0-1)
  • Migration status for libei (1.1.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libei would introduce bugs in testing: #1058218
    • missing build on amd64
    • missing build on i386
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for libei/1.2.0-1: arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating libei will fix bugs in testing: #1060147
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libei.html
    • Reproducible on arm64 - info ♻
    • 32 days old (needed 5 days)
• liblouis (3.27.0-1 to 3.28.0-1)
  • Migration status for liblouis (3.27.0-1 to 3.28.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for liblouis/3.28.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for liblouisutdml/2.12.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating liblouis will fix bugs in testing: #1060148
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblouis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 33 days old (needed 5 days)
• python-array-api-compat (- to 1.4-1)
  • Migration status for python-array-api-compat (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-array-api-compat.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 33 days old (needed 5 days)
• extrepo (0.11 to 0.12)
  • Migration status for extrepo (0.11 to 0.12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for extrepo/0.12: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating extrepo will fix bugs in testing: #1060149
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extrepo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• circlator (- to 1.5.6-11)
  • Migration status for circlator (- to 1.5.6-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): circlator canu (not considered)
    • Depends: circlator canu (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/circlator.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for circlator/1.5.6-11: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 35 days old (needed 2 days)
• flox (- to 0.8.5-1)
  • Migration status for flox (- to 0.8.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): flox python-xarray (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flox.html
    • autopkgtest for flox/0.8.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 35 days old (needed 2 days)
• mopac (22.0.6+dfsg-1 to 22.1.0-1)
  • Migration status for mopac (22.0.6+dfsg-1 to 22.1.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating mopac will fix bugs in testing: #1059876
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mopac.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 35 days old (needed 5 days)
• openmolcas (- to 23.10-1)
  • Migration status for openmolcas (- to 23.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openmolcas would introduce bugs in testing: #1042168
    • autopkgtest for openmolcas/23.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmolcas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 35 days old (needed 5 days)
• pyspectral (- to 0.13.0+ds-1)
  • Migration status for pyspectral (- to 0.13.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyspectral python-xarray (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): pyspectral python-geotiepoints
    • Depends: pyspectral python-geotiepoints
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyspectral.html
    • autopkgtest for pyspectral/0.13.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 35 days old (needed 2 days)
• python3-defaults (3.11.4-5 to 3.11.6-1)
  • Migration status for python3-defaults (3.11.4-5 to 3.11.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios2/2.9.2+dfsg1-8: amd64: Failed (not a regression), arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for aioquic/0.9.24-1: arm64: Pass
    • autopkgtest for azure-cli/2.50.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for azure-cosmos-table-python/1.0.5+git20191025-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for barbican/1:17.0.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for cctbx/2022.9+ds2+~3.11.2+ds1-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ceilometer/blocked-on-ci-infra: i386: Ignored failure
    • autopkgtest for celery/5.3.4-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for circuits/3.2.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for cython/3.0.7-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for cython-legacy/0.29.36-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for dask/2023.8.0+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for debugpy/1.8.0+ds-2: i386: Regression or new test ♻ (reference ♻)
    • autopkgtest for dpdk/23.11-1: amd64: Ignored failure, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Ignored failure, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for flask/2.2.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for flask-autoindex/0.6.6-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for fwupd/1.9.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for graphene/1.10.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for heat/1:21.0.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ipykernel/6.24.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ipython/8.14.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for jupyter-client/7.4.9-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for keystone/2:24.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for lazy-object-proxy/1.9.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for libsbml/5.20.2+dfsg-1: ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for llvm-toolchain-17/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for loguru/0.6.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for m2crypto/0.38.0-4.1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for manila/1:17.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mdp/3.6-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mistral/17.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mkdocstrings-python-handlers/1.7.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mkdocstrings-python-legacy/0.2.3-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for networking-sfc/17.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for neutron-dynamic-routing/2:23.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for nipy/0.5.0-8: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for numpy/1:1.24.2-2: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for numpydoc/1.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pivy/0.6.8-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for plakativ/0.5.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ponyorm/0.7.16+ds-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pycryptodome/3.11.0+dfsg1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pycxx/7.1.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pydevd/2.10.0+ds-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for pydocstyle/6.3.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyee/9.0.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyferret/7.6.5-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pygame/2.5.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pygobject/3.46.0-1: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for pylint/2.17.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyopengl/3.1.6+dfsg-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pysph/1.0~b1-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for pytango/9.4.2-1: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pytest-localserver/0.5.0-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-aioredlock/0.7.3-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-aiosmtpd/1.4.3-1.1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-boto/2.49.0-4.1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-bytecode/0.15.1-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for python-cassandra-driver/3.28.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-changelog/0.6.1-1: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-django-pgschemas/0.15.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-docformatter/1.7.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-duckpy/3.2.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-editor/1.0.3-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-executing/1.2.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-fabio/2023.6.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for python-fswrap/1.0.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-glanceclient/1:4.4.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-glyphsets/0.5.4-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-graphviz/0.20.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-hiredis/1.0.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-hug/2.6.0-2.4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-ibm-cloud-sdk-core/3.16.7-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-icecream/2.1.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-keystonemiddleware/10.4.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-loompy/3.0.7+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-lti/0.9.5-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-lzstring/1.0.4-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-mbed-host-tests/1.4.4-8: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-mbed-ls/1.6.2+dfsg-8: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-memory-profiler/0.61-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-mpegdash/0.3.1-1: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-msrest/0.6.21-2: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-nudatus/0.0.5-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-openstackclient/6.3.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-openstacksdk/1.5.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-pulp/2.7.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-py/1.11.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-pynndescent/0.5.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-sure/2.0.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-tornado/6.3.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-uinput/0.11.2-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-urllib3/1.26.18-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pythran/0.14.0+ds-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pytrainer/2.2.1-3: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for redland-bindings/1.0.17.1+dfsg-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for resampy/0.4.2+ds-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rich/13.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ropgadget/7.4+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sahara/1:19.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for scikit-fmm/2022.08.15-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for senlin/16.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sentry-python/1.9.10-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for silx/1.1.2+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for sip4/4.19.25+dfsg-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sphinx/7.2.6-3: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for sphinx-autoapi/2.0.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for spyder/5.5.0+ds-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for statsmodels/0.14.0+dfsg-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for swift/2.32.0-2: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for syndication-domination/1.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for trololio/1.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for vcr.py/5.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for xmds2/blocked-on-ci-infra: amd64: Ignored failure, ppc64el: Ignored failure
    • autopkgtest for xrayutilities/1.7.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-defaults.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• rjava (1.0-6-1 to 1.0-10-1)
  • Migration status for rjava (1.0-6-1 to 1.0-10-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating rjava will fix bugs in testing: #1059875
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rjava.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 35 days old (needed 5 days)
• rust-imara-diff (- to 0.1.5-1)
  • Migration status for rust-imara-diff (- to 0.1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-imara-diff rust-ahash (not considered)
    • Depends: rust-imara-diff rust-ahash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-imara-diff.html
    • autopkgtest for rust-imara-diff/0.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 35 days old (needed 2 days)
• pycoast (- to 1.7.0+dfsg-1)
  • Migration status for pycoast (- to 1.7.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pycoast pyresample (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycoast.html
    • autopkgtest for pycoast/1.7.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• r-bioc-tcgabiolinks (- to 2.30.0+dfsg-1)
  • Migration status for r-bioc-tcgabiolinks (- to 2.30.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-tcgabiolinks/2.30.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Regression or new test ♻ , s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tcgabiolinks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• slic3r-prusa (- to 2.6.1+dfsg-4.1)
  • Migration status for slic3r-prusa (- to 2.6.1+dfsg-4.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for slic3r-prusa/2.6.1+dfsg-4.1: amd64: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • 37 days old (needed 5 days)
• tracker-miners (3.4.6-1 to 3.4.6-2)
  • Migration status for tracker-miners (3.4.6-1 to 3.4.6-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating tracker-miners will fix bugs in testing: #1059788
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tracker-miners.html
    • 37 days old (needed 5 days)
• trollimage (- to 1.22.2-1)
  • Migration status for trollimage (- to 1.22.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): trollimage python-xarray (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): trollimage pyresample
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trollimage.html
    • autopkgtest for trollimage/1.22.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 37 days old (needed 2 days)
• xfce4-power-manager (4.18.2-1 to 4.18.3-1)
  • Migration status for xfce4-power-manager (4.18.2-1 to 4.18.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by corsac
    • Not built on buildd: arch all binaries uploaded by corsac, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating xfce4-power-manager will fix bugs in testing: #1059787
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-power-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• ruby-psych (- to 5.0.2-2)
  • Migration status for ruby-psych (- to 5.0.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-psych jruby (not considered)
    • Depends: ruby-psych jruby (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-psych.html
    • autopkgtest for ruby-psych/5.0.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 38 days old (needed 2 days)
• rust-axum (- to 0.6.20-5)
  • Migration status for rust-axum (- to 0.6.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-axum has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 38 days old (needed 5 days)
• django-invitations (2.0.0-2 to 2.1.0-1)
  • Migration status for django-invitations (2.0.0-2 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-invitations/2.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-invitations.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• nautilus (44.2.1-2 to 45.1-1)
  • Migration status for nautilus (44.2.1-2 to 45.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • nautilus/mips64el has unsatisfiable dependency
    • Updating nautilus would introduce bugs in testing: #1050733
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating nautilus will fix bugs in testing: #1053422
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• python-fastparquet (- to 2023.10.1-2)
  • Migration status for python-fastparquet (- to 2023.10.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): python-fastparquet python-cramjam
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fastparquet.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 40 days old (needed 5 days)
• ifscheme (- to 1.7-8)
  • Migration status for ifscheme (- to 1.7-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ifscheme would introduce bugs in testing: #981637
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifscheme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• jruby-maven-plugins (- to 3.0.1-2)
  • Migration status for jruby-maven-plugins (- to 3.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): jruby-maven-plugins jruby (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-maven-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• python-html-sanitizer (- to 2.2-1)
  • Migration status for python-html-sanitizer (- to 2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-html-sanitizer would introduce bugs in testing: #1008366
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-html-sanitizer.html
    • autopkgtest for python-html-sanitizer/2.2-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• python-jsonschema-specifications (- to 2023.11.1-2)
  • Migration status for python-jsonschema-specifications (- to 2023.11.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-jsonschema-specifications/arm64 has unsatisfiable dependency
    • Build-Depends-Indep: python-jsonschema-specifications referencing
    • Build-Depends-Indep: python-jsonschema-specifications rpds-py
    • Depends: python-jsonschema-specifications referencing
    • Depends: python-jsonschema-specifications rpds-py
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonschema-specifications.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 41 days old (needed 5 days)
• lsp-mode (- to 8.0.0-6)
  • Migration status for lsp-mode (- to 8.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lsp-mode would introduce bugs in testing: #1052939
    • autopkgtest for lsp-mode/8.0.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 42 days old (needed 5 days)
• metpy (- to 1.5.1+ds-4)
  • Migration status for metpy (- to 1.5.1+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): metpy python-xarray (not considered)
    • Depends: metpy python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metpy.html
    • autopkgtest for metpy/1.5.1+ds-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 42 days old (needed 2 days)
• gvm (- to 23.11.1)
  • Migration status for gvm (- to 23.11.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gvm openvas-scanner (not considered)
    • Invalidated by dependency
    • Depends: gvm gsad
    • Depends: gvm gvmd
    • Depends: gvm ospd-openvas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• rasdaemon (0.6.8-1.1 to 0.8.0-1)
  • Migration status for rasdaemon (0.6.8-1.1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rasdaemon would introduce bugs in testing: #1059484
    • autopkgtest for rasdaemon/0.8.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rasdaemon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• ccextractor (- to 0.94+ds1-3)
  • Migration status for ccextractor (- to 0.94+ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ccextractor gpac (not considered)
    • Depends: ccextractor gpac (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccextractor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• mysql-workbench (- to 8.0.32+dfsg-2)
  • Migration status for mysql-workbench (- to 8.0.32+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-workbench would introduce bugs in testing: #1000093
    • Depends: mysql-workbench mysql-connector-python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-workbench.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• python-crispy-bootstrap3 (- to 2022.1-1)
  • Migration status for python-crispy-bootstrap3 (- to 2022.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): python-crispy-bootstrap3 python-django-crispy-forms
    • Depends: python-crispy-bootstrap3 python-django-crispy-forms
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-crispy-bootstrap3.html
    • autopkgtest for python-crispy-bootstrap3/2022.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 44 days old (needed 2 days)
• python-django-ratelimit (- to 4.1.0-1)
  • Migration status for python-django-ratelimit (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ratelimit.html
    • autopkgtest for python-django-ratelimit/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 44 days old (needed 2 days)
• rust-datasize (- to 0.2.13-1)
  • Migration status for rust-datasize (- to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-datasize/0.2.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-datasize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• apt (2.7.6 to 2.7.7)
  • Migration status for apt (2.7.6 to 2.7.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for apt/2.7.7: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating apt will fix bugs in testing: #1059352
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 45 days old (needed 5 days)
• django-oauth-toolkit (2.3.0-1 to 2.3.0-2)
  • Migration status for django-oauth-toolkit (2.3.0-1 to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating django-oauth-toolkit will fix bugs in testing: #1059487
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-oauth-toolkit.html
    • autopkgtest for django-oauth-toolkit/2.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 45 days old (needed 2 days)
• node-wikibase-cli (- to 15.15.4-5)
  • Migration status for node-wikibase-cli (- to 15.15.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-wikibase-cli would introduce bugs in testing: #1056699, #1056708
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-wikibase-cli.html
    • autopkgtest for node-wikibase-cli/15.15.4-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 45 days old (needed 2 days)
• patool (1.12-5 to 2.0.0-1)
  • Migration status for patool (1.12-5 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for patool/2.0.0-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Not built on buildd: arch all binaries uploaded by abhijith@openmailbox.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating patool will fix bugs in testing: #1059477
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patool.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 45 days old (needed 5 days)
• django-phonenumber-field (- to 7.2.0-2)
  • Migration status for django-phonenumber-field (- to 7.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-phonenumber-field.html
    • autopkgtest for django-phonenumber-field/7.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 46 days old (needed 2 days)
• gvm-tools (- to 23.11.0-1)
  • Migration status for gvm-tools (- to 23.11.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gvm-tools python-gvm (not considered)
    • Depends: gvm-tools python-gvm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-tools.html
    • autopkgtest for gvm-tools/23.11.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 46 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-4)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-450 would introduce bugs in testing: #1014304
    • autopkgtest for nvidia-graphics-drivers-tesla-450/450.248.02-4: amd64: No tests, superficial or marked flaky ♻ , arm64: Regression or new test ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 46 days old (needed 5 days)
• gsad (- to 22.8.0-1)
  • Migration status for gsad (- to 22.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gsad gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• gvm-libs (- to 22.7.3-1)
  • Migration status for gvm-libs (- to 22.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gvm-libs would introduce bugs in testing: #986529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• gvmd (- to 23.1.0-1)
  • Migration status for gvmd (- to 23.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gvmd gvm-libs (not considered)
    • Depends: gvmd gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gvmd greenbone-feed-sync
    • Depends: gvmd ospd-openvas
    • Depends: gvmd pg-gvm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvmd.html
    • autopkgtest for gvmd/23.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• ospd-openvas (- to 22.6.2-1)
  • Migration status for ospd-openvas (- to 22.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ospd-openvas openvas-scanner (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ospd-openvas.html
    • autopkgtest for ospd-openvas/22.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• php-lcobucci-jwt (- to 5.2.0-1)
  • Migration status for php-lcobucci-jwt (- to 5.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-lcobucci-jwt php-lcobucci-clock (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-lcobucci-jwt.html
    • autopkgtest for php-lcobucci-jwt/5.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• pontos (- to 23.11.4-1)
  • Migration status for pontos (- to 23.11.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pontos would introduce bugs in testing: #1056447
    • Build-Depends(-Arch): pontos python-colorful
    • Depends: pontos python-colorful
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pontos.html
    • autopkgtest for pontos/23.11.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• python-gvm (- to 23.11.0-1)
  • Migration status for python-gvm (- to 23.11.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-gvm pontos (not considered)
    • Invalidated by build-dependency
    • Depends: python-gvm gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gvm.html
    • autopkgtest for python-gvm/23.11.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 47 days old (needed 5 days)
• vectorscan (5.4.10.1-1 to 5.4.11-1)
  • Migration status for vectorscan (5.4.10.1-1 to 5.4.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vectorscan/5.4.11-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating vectorscan will fix bugs in testing: #1059478
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vectorscan.html
    • Reproducibility regression on amd64 - info ♻
    • 47 days old (needed 5 days)
• virtuoso-opensource (- to 7.2.5.1+dfsg1-0.5)
  • Migration status for virtuoso-opensource (- to 7.2.5.1+dfsg1-0.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtuoso-opensource would introduce bugs in testing: #1036467, #999931
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtuoso-opensource.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 47 days old (needed 5 days)
• golang-github-jamesruan-go-rfc1924 (- to 0.0~git20170108.2767ca7-1)
  • Migration status for golang-github-jamesruan-go-rfc1924 (- to 0.0~git20170108.2767ca7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jamesruan-go-rfc1924.html
    • autopkgtest for golang-github-jamesruan-go-rfc1924/0.0~git20170108.2767ca7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• libimage-exiftool-perl (12.67+dfsg-1 to 12.70+dfsg-1)
  • Migration status for libimage-exiftool-perl (12.67+dfsg-1 to 12.70+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libimage-exiftool-perl.html
    • autopkgtest for libimage-exiftool-perl/12.70+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• pelican (4.8.0+dfsg-3 to 4.9.1+dfsg-1)
  • Migration status for pelican (4.8.0+dfsg-3 to 4.9.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pelican would introduce bugs in testing: #1057484
    • Build-Depends(-Arch): pelican pdm
  • Additional info:
    • Updating pelican will fix bugs in testing: #1059166
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pelican.html
    • Waiting for reproducibility reference results on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 48 days old (needed 5 days)
• ruby-rspec-parameterized-core (- to 1.0.0-1)
  • Migration status for ruby-rspec-parameterized-core (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-core.html
    • autopkgtest for ruby-rspec-parameterized-core/1.0.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• ruby-rspec-parameterized-table-syntax (- to 1.0.1-1)
  • Migration status for ruby-rspec-parameterized-table-syntax (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core
    • Depends: ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-table-syntax.html
    • autopkgtest for ruby-rspec-parameterized-table-syntax/1.0.1-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• rust-subversion (- to 0.0.3-1)
  • Migration status for rust-subversion (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-subversion/0.0.3-1: amd64: Regression or new test ♻
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
    • Build-Depends(-Arch): rust-subversion rust-apr/mips64el
    • Depends: rust-subversion rust-apr/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-subversion.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 48 days old (needed 5 days)
• singularity-container (- to 4.0.2+ds1-1)
  • Migration status for singularity-container (- to 4.0.2+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating singularity-container would introduce bugs in testing: #1029669
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• wine-development (- to 8.19~repack-1)
  • Migration status for wine-development (- to 8.19~repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wine-development would introduce bugs in testing: #988246
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 48 days old (needed 5 days)
• secsipidx (1.2.0-2 to 1.3.2-1)
  • Migration status for secsipidx (1.2.0-2 to 1.3.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for secsipidx/1.3.2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating secsipidx will fix bugs in testing: #1057350
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/secsipidx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 50 days old (needed 5 days)
• votca (- to 2023-1)
  • Migration status for votca (- to 2023-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): votca rdkit (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/votca.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 50 days old (needed 5 days)
• cryptojs (- to 3.1.2+dfsg-4)
  • Migration status for cryptojs (- to 3.1.2+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cryptojs would introduce bugs in testing: #1056014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptojs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
• python-django-celery-beat (- to 2.5.0-2)
  • Migration status for python-django-celery-beat (- to 2.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-celery-beat would introduce bugs in testing: #1056465
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-celery-beat.html
    • autopkgtest for python-django-celery-beat/2.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 51 days old (needed 2 days)
• jupyter-ydoc (- to 1.0.2-2)
  • Migration status for jupyter-ydoc (- to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-jupyter-ydoc/arm64 has unsatisfiable dependency
    • autopkgtest for jupyter-ydoc/1.0.2-2: amd64: Pass
    • Build-Depends(-Arch): jupyter-ydoc ypy
    • Depends: jupyter-ydoc ypy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-ydoc.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 52 days old (needed 5 days)
• python-crispy-bootstrap5 (- to 2023.10-1)
  • Migration status for python-crispy-bootstrap5 (- to 2023.10-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-crispy-bootstrap5 python-django-crispy-forms (not considered)
    • Depends: python-crispy-bootstrap5 python-django-crispy-forms (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-crispy-bootstrap5.html
    • autopkgtest for python-crispy-bootstrap5/2023.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 52 days old (needed 2 days)
• referencing (- to 0.31.0-1)
  • Migration status for referencing (- to 0.31.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-referencing/arm64 has unsatisfiable dependency
    • Build-Depends(-Arch): referencing rpds-py
    • Depends: referencing rpds-py
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/referencing.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 52 days old (needed 5 days)
• rust-isolang (- to 2.3.0-2)
  • Migration status for rust-isolang (- to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-isolang/2.3.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-isolang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 52 days old (needed 5 days)
• ypy (- to 0.7.0~a1-2)
  • Migration status for ypy (- to 0.7.0~a1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-lib0-dev
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-yrs-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): ypy python-maturin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 52 days old (needed 5 days)
• grub-efi-amd64-signed (1+2.06+13+deb13u1 to 1+2.12~rc1+12)
  • Migration status for grub-efi-amd64-signed (1+2.06+13+deb13u1 to 1+2.12~rc1+12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/grub-efi-amd64-signed.html
    • Build-Depends(-Arch): grub-efi-amd64-signed grub2
    • Built-Using: grub-efi-amd64-signed grub2
    • Depends: grub-efi-amd64-signed grub2
  • Additional info:
    • Reproducible on amd64 - info ♻
    • 53 days old (needed 5 days)
• grub-efi-arm64-signed (1+2.06+13+deb13u1 to 1+2.12~rc1+12)
  • Migration status for grub-efi-arm64-signed (1+2.06+13+deb13u1 to 1+2.12~rc1+12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): grub-efi-arm64-signed grub2 (not considered)
    • Built-Using: grub-efi-arm64-signed grub2 (not considered)
    • Depends: grub-efi-arm64-signed grub2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • 53 days old (needed 5 days)
• grub-efi-ia32-signed (1+2.06+13+deb13u1 to 1+2.12~rc1+12)
  • Migration status for grub-efi-ia32-signed (1+2.06+13+deb13u1 to 1+2.12~rc1+12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): grub-efi-ia32-signed grub2 (not considered)
    • Built-Using: grub-efi-ia32-signed grub2 (not considered)
    • Depends: grub-efi-ia32-signed grub2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-13)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-460 would introduce bugs in testing: #1027704
    • autopkgtest for nvidia-graphics-drivers-tesla-460/460.106.00-13: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 53 days old (needed 5 days)
• django-mailman3 (- to 1.3.11-1)
  • Migration status for django-mailman3 (- to 1.3.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-mailman3 would introduce bugs in testing: #1052786
    • Build-Depends(-Arch): django-mailman3 django-allauth
    • Depends: django-mailman3 django-allauth
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-mailman3.html
    • autopkgtest for django-mailman3/1.3.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 54 days old (needed 2 days)
• jupyter-events (- to 0.9.0-2)
  • Migration status for jupyter-events (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-jupyter-events/amd64 has unsatisfiable dependency
    • python3-jupyter-events/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/j/jupyter-events.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• python-diagrams (0.21.1-1 to 0.23.4-1)
  • Migration status for python-diagrams (0.21.1-1 to 0.23.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-diagrams/amd64 has unsatisfiable dependency
    • python3-diagrams/arm64 has unsatisfiable dependency
    • Updating python-diagrams would introduce bugs in testing: #1057174
  • Additional info:
    • Updating python-diagrams will fix bugs in testing: #1058811
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-diagrams.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• python-lsp-ruff (- to 1.5.3-1)
  • Migration status for python-lsp-ruff (- to 1.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lsp-ruff/1.5.3-1: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by viiru, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): python-lsp-ruff ruff
    • Depends: python-lsp-ruff ruff
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lsp-ruff.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 54 days old (needed 5 days)
• rpds-py (- to 0.12.0-2)
  • Migration status for rpds-py (- to 0.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-archery-dev
    • rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-rpds-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): rpds-py python-maturin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpds-py.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 54 days old (needed 5 days)
• django-allauth (0.51.0-1 to 0.58.2-2)
  • Migration status for django-allauth (0.51.0-1 to 0.58.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-allauth/0.58.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for django-invitations/2.0.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-allauth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-21)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #1016615, #1025280, #1033775, #1039679, #1055137, #973599, #979671, #987217, #991352
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-21: amd64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 55 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-6)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-390xx would introduce bugs in testing: #1006719, #1033776, #1039680, #1055138
    • autopkgtest for nvidia-graphics-drivers-legacy-390xx/390.157-6: amd64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻
    • Depends: nvidia-graphics-drivers-legacy-390xx nvidia-graphics-drivers-tesla-418
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 55 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-13)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xserver-xorg-video-nvidia-tesla-418/amd64 has unsatisfiable dependency
    • xserver-xorg-video-nvidia-tesla-418/ppc64el has unsatisfiable dependency
    • Updating nvidia-graphics-drivers-tesla-418 would introduce bugs in testing: #1005930, #1006718, #1011143, #1016617, #1025282, #1033777, #1039681, #1055139
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-13: i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 55 days old (needed 5 days)
• dxvk (- to 2.3-1)
  • Migration status for dxvk (- to 2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dxvk/arm64 has unsatisfiable dependency
    • Updating dxvk would introduce bugs in testing: #982159
    • autopkgtest for dxvk/2.3-1: amd64: Regression or new test ♻ , i386: Regression or new test ♻
    • Build-Depends(-Arch): dxvk wine-development
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxvk.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• django-assets (- to 2.0-3)
  • Migration status for django-assets (- to 2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-assets would introduce bugs in testing: #1056288
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-assets.html
    • 59 days old (needed 5 days)
• grub2 (2.06-13+deb13u1 to 2.12~rc1-12)
  • Migration status for grub2 (2.06-13+deb13u1 to 2.12~rc1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grub2 would introduce bugs in testing: #1056764
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub2.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 59 days old (needed 5 days)
• placement (- to 10.0.0-3)
  • Migration status for placement (- to 10.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: placement sphinxcontrib-actdiag (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/placement.html
    • autopkgtest for placement/10.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 59 days old (needed 2 days)
• r10k (3.15.4-1 to 4.0.0-1)
  • Migration status for r10k (3.15.4-1 to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r10k/4.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r10k will fix bugs in testing: #1058628
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r10k.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 days old (needed 5 days)
• ruff (- to 0.0.291+dfsg1-2)
  • Migration status for ruff (- to 0.0.291+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruff would introduce bugs in testing: #1055559
    • missing build on amd64
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): ruff python-maturin
    • Build-Depends(-Arch): ruff rust-imperative
    • Build-Depends(-Arch): ruff rust-rustpython-ast
    • Build-Depends(-Arch): ruff rust-rustpython-common
    • Build-Depends(-Arch): ruff rust-rustpython-parser
    • Build-Depends(-Arch): ruff rust-tikv-jemallocator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruff.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 60 days old (needed 5 days)
• dm-tree (- to 0.1.8-2)
  • Migration status for dm-tree (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dm-tree would introduce bugs in testing: #1055686
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dm-tree.html
    • autopkgtest for dm-tree/0.1.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 61 days old (needed 2 days)
• libpysal (- to 4.9.2-1)
  • Migration status for libpysal (- to 4.9.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libpysal python-xarray (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpysal.html
    • autopkgtest for libpysal/4.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 61 days old (needed 2 days)
• linuxcnc (- to 2.9.1-2)
  • Migration status for linuxcnc (- to 2.9.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linuxcnc would introduce bugs in testing: #1055493
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/l/linuxcnc.html
  • Additional info:
    • autopkgtest for linuxcnc/2.9.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 61 days old (needed 2 days)
• octave-ltfat (- to 2.6.0+dfsg-6)
  • Migration status for octave-ltfat (- to 2.6.0+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for octave-ltfat/2.6.0+dfsg-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-ltfat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 61 days old (needed 5 days)
• spaghetti (- to 1.7.4-3)
  • Migration status for spaghetti (- to 1.7.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spaghetti would introduce bugs in testing: #1054759
    • Build-Depends(-Arch): spaghetti esda
    • Build-Depends(-Arch): spaghetti libpysal
    • Depends: spaghetti esda
    • Depends: spaghetti libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spaghetti.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• python-django-ca (- to 1.25.0-2)
  • Migration status for python-django-ca (- to 1.25.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-django-ca/1.25.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): python-django-ca python-ocspbuilder
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ca.html
    • Reproducible on amd64 - info ♻
    • 63 days old (needed 5 days)
• genomicsdb (- to 1.5.0-2)
  • Migration status for genomicsdb (- to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgenomicsdb-java/arm64 has unsatisfiable dependency
    • autopkgtest for genomicsdb/1.5.0-2: amd64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genomicsdb.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 64 days old (needed 5 days)
• spopt (- to 0.5.0-4)
  • Migration status for spopt (- to 0.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spopt would introduce bugs in testing: #1054780
    • Build-Depends(-Arch): spopt libpysal
    • Build-Depends(-Arch): spopt mapclassify
    • Build-Depends(-Arch): spopt spaghetti
    • Depends: spopt libpysal
    • Depends: spopt spaghetti
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spopt.html
    • autopkgtest for spopt/0.5.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 64 days old (needed 2 days)
• datalad-next (- to 1.0.2-1)
  • Migration status for datalad-next (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for datalad-next/1.0.2-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by mih, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datalad-next.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 65 days old (needed 5 days)
• esda (- to 2.5.1-1)
  • Migration status for esda (- to 2.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating esda would introduce bugs in testing: #1054761
    • Build-Depends(-Arch): esda libpysal
    • Depends: esda libpysal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esda.html
    • autopkgtest for esda/2.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 65 days old (needed 2 days)
• golang-github-google-safetext (- to 0.0~git20230106.7156a76-1)
  • Migration status for golang-github-google-safetext (- to 0.0~git20230106.7156a76-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-safetext.html
    • autopkgtest for golang-github-google-safetext/0.0~git20230106.7156a76-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 65 days old (needed 2 days)
• mysql-8.0 (- to 8.0.35-1)
  • Migration status for mysql-8.0 (- to 8.0.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-8.0 would introduce bugs in testing: #853008
    • autopkgtest for mysql-8.0/8.0.35-1: amd64: Regression or new test ♻ , arm64: Pass, armhf: Regression or new test ♻ , i386: Pass, ppc64el: Regression or new test ♻ , s390x: Pass
    • Not touching package due to block request by pochu (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-8.0.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 66 days old (needed 5 days)
• netdata (- to 1.43.2-1)
  • Migration status for netdata (- to 1.43.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdata would introduce bugs in testing: #1042533, #1045145
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 67 days old (needed 5 days)
• rust-sqlx-mysql (- to 0.7.1-2)
  • Migration status for rust-sqlx-mysql (- to 0.7.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sqlx-mysql rust-sqlx-core (not considered)
    • Depends: rust-sqlx-mysql rust-sqlx-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-mysql.html
    • autopkgtest for rust-sqlx-mysql/0.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 67 days old (needed 2 days)
• gxneur (- to 0.20.0-2.2)
  • Migration status for gxneur (- to 0.20.0-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gxneur xneur (not considered)
    • Depends: gxneur xneur (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gxneur.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• hypercorn (0.14.4-1 to 0.15.0-1)
  • Migration status for hypercorn (0.14.4-1 to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hypercorn would introduce bugs in testing: #1058125
    • Build-Depends(-Arch): hypercorn node-mermaid
  • Additional info:
    • Updating hypercorn will fix bugs in testing: #1057351
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hypercorn.html
    • autopkgtest for hypercorn/0.15.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 68 days old (needed 2 days)
• rust-imperative (- to 1.0.5-1)
  • Migration status for rust-imperative (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-imperative-dev/amd64 has unsatisfiable dependency
    • rust-imperative unsatisfiable Build-Depends(-Arch) on amd64: librust-rust-stemmers-1+default-dev (>= 1.2.0-~~)
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-imperative.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 68 days old (needed 5 days)
• snakeyaml-engine (- to 2.7+ds-1)
  • Migration status for snakeyaml-engine (- to 2.7+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for snakeyaml-engine/2.7+ds-1: amd64: Regression or new test ♻ , arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by lavamind, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snakeyaml-engine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 70 days old (needed 5 days)
• plasma-thunderbolt (- to 5.27.9-1)
  • Migration status for plasma-thunderbolt (- to 5.27.9-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): plasma-thunderbolt bolt
    • Depends: plasma-thunderbolt bolt
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-thunderbolt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 71 days old (needed 5 days)
• guerillabackup (- to 0.5.0-1)
  • Migration status for guerillabackup (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guerillabackup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• vecgeom (- to 1.2.5+dfsg-1)
  • Migration status for vecgeom (- to 1.2.5+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vecgeom embree (not considered)
    • Depends: vecgeom embree (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vecgeom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• dogecoin (- to 1.14.6-4)
  • Migration status for dogecoin (- to 1.14.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dogecoin would introduce bugs in testing: #1034806, #1059133
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogecoin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 73 days old (needed 5 days)
• libpsml (- to 2.0.1-1)
  • Migration status for libpsml (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpsml-dev/amd64 has unsatisfiable dependency
    • libpsml unsatisfiable Build-Depends(-Arch) on amd64: libxmlf90-dev
    • Not built on buildd: arch amd64 binaries uploaded by mbanck
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libp/libpsml.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 73 days old (needed 5 days)
• python-certbot-dns-gandi (- to 1.4.3-2)
  • Migration status for python-certbot-dns-gandi (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-gandi would introduce bugs in testing: #1038920
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gandi.html
    • autopkgtest for python-certbot-dns-gandi/1.4.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 73 days old (needed 2 days)
• greenbone-feed-sync (- to 23.10.0-1)
  • Migration status for greenbone-feed-sync (- to 23.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sophieb, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): greenbone-feed-sync pontos
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/greenbone-feed-sync.html
    • autopkgtest for greenbone-feed-sync/23.10.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• orange-spectroscopy (- to 0.6.10-4)
  • Migration status for orange-spectroscopy (- to 0.6.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange-spectroscopy/0.6.10-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Depends: orange-spectroscopy orange3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange-spectroscopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• orange3 (- to 3.35.0+ds1-5)
  • Migration status for orange3 (- to 3.35.0+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange3/3.35.0+ds1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Depends: orange3 opentsne
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• pry (0.13.1-3 to 0.14.2-1)
  • Migration status for pry (0.13.1-3 to 0.14.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pry/0.14.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ruby-pry-byebug/3.9.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating pry will fix bugs in testing: #1056995
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pry.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• haskell-arithmoi (- to 0.12.1.0-2)
  • Migration status for haskell-arithmoi (- to 0.12.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-arithmoi haskell-integer-roots (not considered)
    • Build-Depends-Indep: haskell-arithmoi haskell-integer-roots (not considered)
    • Depends: haskell-arithmoi haskell-integer-roots (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-arithmoi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 75 days old (needed 5 days)
• haskell-cryptol (- to 3.0.0-1)
  • Migration status for haskell-cryptol (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-prof
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-cryptol haskell-arithmoi
    • Build-Depends-Indep: haskell-cryptol haskell-arithmoi
    • Depends: haskell-cryptol haskell-arithmoi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cryptol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 75 days old (needed 5 days)
• haskell-dhall (- to 1.41.2-1)
  • Migration status for haskell-dhall (- to 1.41.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-dhall haskell-cborg
    • Build-Depends(-Arch): haskell-dhall haskell-cborg-json
    • Build-Depends(-Arch): haskell-dhall haskell-serialise
    • Build-Depends-Indep: haskell-dhall haskell-cborg
    • Build-Depends-Indep: haskell-dhall haskell-cborg-json
    • Build-Depends-Indep: haskell-dhall haskell-serialise
    • Depends: haskell-dhall haskell-cborg
    • Depends: haskell-dhall haskell-cborg-json
    • Depends: haskell-dhall haskell-serialise
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-dhall.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 75 days old (needed 5 days)
• rust-octocrab (- to 0.31.2-1)
  • Migration status for rust-octocrab (- to 0.31.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-octocrab-dev/amd64 has unsatisfiable dependency
    • rust-octocrab unsatisfiable Build-Depends(-Arch) on amd64: librust-tower-http-0.4+default-dev
    • rust-octocrab unsatisfiable Build-Depends(-Arch) on amd64: librust-tower-http-0.4+follow-redirect-dev
    • rust-octocrab unsatisfiable Build-Depends(-Arch) on amd64: librust-tower-http-0.4+map-response-body-dev
    • rust-octocrab unsatisfiable Build-Depends(-Arch) on amd64: librust-tower-http-0.4+trace-dev
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
    • Build-Depends(-Arch): rust-octocrab rust-hyper-timeout
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-octocrab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 75 days old (needed 5 days)
• rust-temp-testdir (- to 0.2.3-1)
  • Migration status for rust-temp-testdir (- to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-temp-testdir/0.2.3-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-temp-testdir.html
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 days)
• rust-xflags-macros (- to 0.3.1-1)
  • Migration status for rust-xflags-macros (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-xflags-macros/0.3.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 days)
• openjdk-8 (- to 8u392-ga-1)
  • Migration status for openjdk-8 (- to 8u392-ga-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #989736
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-8/blocked-on-ci-infra: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-8.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 77 days old (needed 5 days)
• ring (- to 20230922.0~ds2-1)
  • Migration status for ring (- to 20230922.0~ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ring would introduce bugs in testing: #1057430, #1059307
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/amd64
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/arm64
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/armel
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/armhf
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/i386
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/mips64el
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/ppc64el
    • Impossible Depends: ring -> libgit2-1.5/1.5.1+ds-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ring.html
    • autopkgtest for ring/20230922.0~ds2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 77 days old (needed 2 days)
• canu (- to 2.2+dfsg-5)
  • Migration status for canu (- to 2.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for canu/2.2+dfsg-5: amd64: Pass, arm64: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 78 days old (needed 5 days)
• rust-tikv-jemalloc-ctl (- to 0.5.4-1)
  • Migration status for rust-tikv-jemalloc-ctl (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tikv-jemalloc-ctl/0.5.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-tikv-jemalloc-ctl rust-tikv-jemalloc-sys
    • Depends: rust-tikv-jemalloc-ctl rust-tikv-jemalloc-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tikv-jemalloc-ctl.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 79 days old (needed 5 days)
• python-aiortc (- to 1.5.0-3)
  • Migration status for python-aiortc (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiortc would introduce bugs in testing: #1056453
    • autopkgtest for python-aiortc/1.5.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • python-aiortc unsatisfiable Build-Depends(-Arch) on amd64: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on arm64: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on armel: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on armhf: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on i386: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on mips64el: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on ppc64el: python3-av (<< 11)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on s390x: python3-av (<< 11)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiortc.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 80 days old (needed 5 days)
• virtualbox (- to 7.0.12-dfsg-1)
  • Migration status for virtualbox (- to 7.0.12-dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #794466
    • autopkgtest for virtualbox/7.0.12-dfsg-1: amd64: No tests, superficial or marked flaky ♻ , i386: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 81 days old (needed 5 days)
• rust-xflags (- to 0.3.1-1)
  • Migration status for rust-xflags (- to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xflags rust-xflags-macros (not considered)
    • Depends: rust-xflags rust-xflags-macros (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags.html
    • autopkgtest for rust-xflags/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 82 days old (needed 2 days)
• golang-codeberg-gusted-mcaptcha (- to 0.0~git20220723.4f3072e-1)
  • Migration status for golang-codeberg-gusted-mcaptcha (- to 0.0~git20220723.4f3072e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by openarungeek@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-codeberg-gusted-mcaptcha.html
    • autopkgtest for golang-codeberg-gusted-mcaptcha/0.0~git20220723.4f3072e-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 83 days old (needed 2 days)
• golang-github-alecthomas-mango-kong (- to 0.1.0-1)
  • Migration status for golang-github-alecthomas-mango-kong (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sgmoore@kde.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alecthomas-mango-kong.html
    • autopkgtest for golang-github-alecthomas-mango-kong/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 83 days old (needed 2 days)
• golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1)
  • Migration status for golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jedisct1-go-hpke-compact.html
    • autopkgtest for golang-github-jedisct1-go-hpke-compact/0.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 83 days old (needed 2 days)
• procdump (- to 2.2-1)
  • Migration status for procdump (- to 2.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for procdump/2.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/procdump.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
• rust-libheif-rs (- to 0.20.0-4)
  • Migration status for rust-libheif-rs (- to 0.20.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-libheif-rs/0.20.0-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libheif-rs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
• ironic (- to 1:23.0.0-4)
  • Migration status for ironic (- to 1:23.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: ironic python-pycdlib (not considered)
    • Depends: ironic python-pycdlib (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends-Indep: ironic python-amqplib
    • Depends: ironic python-amqplib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ironic.html
    • autopkgtest for ironic/1:23.0.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 84 days old (needed 2 days)
• phppgadmin (- to 7.13.0+dfsg-3)
  • Migration status for phppgadmin (- to 7.13.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phppgadmin would introduce bugs in testing: #1053004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phppgadmin.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 84 days old (needed 5 days)
• slurm-wlm-contrib (- to 23.02.6-1)
  • Migration status for slurm-wlm-contrib (- to 23.02.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • slurm-wlm-nvml-plugin/amd64 has unsatisfiable dependency
    • slurm-wlm-nvml-plugin-dev/amd64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 85 days old (needed 5 days)
• kokkos (- to 3.7.01-2.1)
  • Migration status for kokkos (- to 3.7.01-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kokkos unsatisfiable Build-Depends(-Arch) on s390x: libmemkind-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kokkos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 87 days old (needed 5 days)
• openshot-qt (- to 3.1.1+dfsg1-1)
  • Migration status for openshot-qt (- to 3.1.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openshot-qt would introduce bugs in testing: #1042611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openshot-qt.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • autopkgtest for openshot-qt/3.1.1+dfsg1-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 87 days old (needed 5 days)
• octavia (- to 13.0.0-2)
  • Migration status for octavia (- to 13.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: octavia sphinxcontrib-nwdiag (not considered)
    • Invalidated by build-dependency (indep)
    • Build-Depends-Indep: octavia sphinxcontrib-actdiag
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octavia.html
    • autopkgtest for octavia/13.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 88 days old (needed 2 days)
• telegram-send (- to 0.37-1)
  • Migration status for telegram-send (- to 0.37-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-send would introduce bugs in testing: #1054663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-send.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• haskell-integer-roots (- to 1.0.2.0-2)
  • Migration status for haskell-integer-roots (- to 1.0.2.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-integer-roots.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 89 days old (needed 5 days)
• nova (- to 2:28.0.0-2)
  • Migration status for nova (- to 2:28.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nova python-amqplib (not considered)
    • Invalidated by dependency
    • Build-Depends-Indep: nova sphinxcontrib-actdiag
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nova.html
    • autopkgtest for nova/2:28.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 89 days old (needed 2 days)
• ironic-python-agent (- to 9.7.0-2)
  • Migration status for ironic-python-agent (- to 9.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ironic-python-agent/9.7.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ironic-python-agent.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• ocaml-duppy (- to 0.9.3-1)
  • Migration status for ocaml-duppy (- to 0.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocaml-duppy would introduce bugs in testing: #1042499
    • Build-Depends(-Arch): ocaml-duppy pcre-ocaml
    • Depends: ocaml-duppy pcre-ocaml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-duppy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• x2goserver (- to 4.1.0.6-1.1)
  • Migration status for x2goserver (- to 4.1.0.6-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2goserver x2gokdrive (not considered)
    • Invalidated by dependency
    • Depends: x2goserver x2godesktopsharing
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2goserver.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• rust-extprim (- to 1.7.1-2)
  • Migration status for rust-extprim (- to 1.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-extprim would introduce bugs in testing: #1053625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-extprim.html
    • autopkgtest for rust-extprim/1.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 91 days old (needed 2 days)
• haskell-cborg-json (- to 0.2.5.0-2)
  • Migration status for haskell-cborg-json (- to 0.2.5.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-cborg-json haskell-cborg
    • Build-Depends-Indep: haskell-cborg-json haskell-cborg
    • Depends: haskell-cborg-json haskell-cborg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cborg-json.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 92 days old (needed 5 days)
• haskell-serialise (- to 0.2.6.0-2)
  • Migration status for haskell-serialise (- to 0.2.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-serialise would introduce bugs in testing: #939323
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-serialise haskell-cborg
    • Build-Depends-Indep: haskell-serialise haskell-cborg
    • Depends: haskell-serialise haskell-cborg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-serialise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 92 days old (needed 5 days)
• haskell-cborg (- to 0.2.9.0-1)
  • Migration status for haskell-cborg (- to 0.2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-cborg would introduce bugs in testing: #1016062
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cborg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 93 days old (needed 5 days)
• networking-bagpipe (- to 19.0.0-1)
  • Migration status for networking-bagpipe (- to 19.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: networking-bagpipe sphinxcontrib-nwdiag (not considered)
    • Invalidated by build-dependency (indep)
    • Build-Depends-Indep: networking-bagpipe networking-bgpvpn
    • Build-Depends-Indep: networking-bagpipe sphinxcontrib-actdiag
    • Depends: networking-bagpipe networking-bgpvpn
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-bagpipe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• networking-bgpvpn (- to 19.0.0-1)
  • Migration status for networking-bgpvpn (- to 19.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: networking-bgpvpn networking-bagpipe (not considered)
    • Depends: networking-bgpvpn networking-bagpipe (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-bgpvpn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• octavia-dashboard (- to 12.0.0-1)
  • Migration status for octavia-dashboard (- to 12.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: octavia-dashboard octavia (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octavia-dashboard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• rust-rustpython-parser (- to 0.2.0-2)
  • Migration status for rust-rustpython-parser (- to 0.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rustpython-parser rust-rustpython-ast (not considered)
    • Depends: rust-rustpython-parser rust-rustpython-ast (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustpython-parser.html
    • autopkgtest for rust-rustpython-parser/0.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 95 days old (needed 2 days)
• ttyd (- to 1.7.4-1)
  • Migration status for ttyd (- to 1.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ttyd would introduce bugs in testing: #996042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ttyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• binoculars (- to 0.0.15-1)
  • Migration status for binoculars (- to 0.0.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): binoculars pyfai (not considered)
    • Depends: binoculars pyfai (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binoculars.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for binoculars/0.0.15-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 96 days old (needed 2 days)
• rust-axum-core (- to 0.3.4-1)
  • Migration status for rust-axum-core (- to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-axum-core-dev/amd64 has unsatisfiable dependency
    • librust-axum-core-dev/arm64 has unsatisfiable dependency
    • librust-axum-core-dev/armel has unsatisfiable dependency
    • librust-axum-core-dev/armhf has unsatisfiable dependency
    • librust-axum-core-dev/i386 has unsatisfiable dependency
    • librust-axum-core-dev/mips64el has unsatisfiable dependency
    • librust-axum-core-dev/ppc64el has unsatisfiable dependency
    • librust-axum-core-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-axum-core.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 96 days old (needed 5 days)
• rust-hyper-timeout (- to 0.4.1-1)
  • Migration status for rust-hyper-timeout (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-hyper-timeout/0.4.1-1: amd64: Regression or new test ♻ , arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyper-timeout.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 96 days old (needed 5 days)
• ghdl (- to 3.0.0+dfsg2-1)
  • Migration status for ghdl (- to 3.0.0+dfsg2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for ghdl/3.0.0+dfsg2-1: amd64: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghdl.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 98 days old (needed 5 days)
• kodi-game-libretro (- to 20.2.4-2)
  • Migration status for kodi-game-libretro (- to 20.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-game-libretro kodi (not considered)
    • Depends: kodi-game-libretro kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-game-libretro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 99 days old (needed 5 days)
• yosys-plugin-ghdl (- to 0.0~git20230419.5b64ccf-1)
  • Migration status for yosys-plugin-ghdl (- to 0.0~git20230419.5b64ccf-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on armel: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on ppc64el: ghdl-mcode (>= 3.0.0)
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for yosys-plugin-ghdl/0.0~git20230419.5b64ccf-1: amd64: Pass, i386: Pass
    • Build-Depends(-Arch): yosys-plugin-ghdl ghdl
    • Depends: yosys-plugin-ghdl ghdl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yosys-plugin-ghdl.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 99 days old (needed 5 days)
• bonnie++ (- to 2.00a+nmu2)
  • Migration status for bonnie++ (- to 2.00a+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bonnie++/2.00a+nmu2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bonnie++.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 100 days old (needed 5 days)
• clblas (- to 2.12-4)
  • Migration status for clblas (- to 2.12-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clblas would introduce bugs in testing: #949767
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clblas.html
    • autopkgtest for clblas/2.12-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 100 days old (needed 2 days)
• gnuastro (- to 0.20-1)
  • Migration status for gnuastro (- to 0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnuastro would introduce bugs in testing: #1052763
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuastro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 103 days old (needed 5 days)
• rust-sqlx-core (- to 0.7.1-3)
  • Migration status for rust-sqlx-core (- to 0.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sqlx-core/0.7.1-3: amd64: Regression or new test ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): rust-sqlx-core rust-ahash
    • Depends: rust-sqlx-core rust-ahash
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 103 days old (needed 5 days)
• rust-sqlx-sqlite (- to 0.7.1-2)
  • Migration status for rust-sqlx-sqlite (- to 0.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sqlx-sqlite/0.7.1-2: amd64: Regression or new test ♻ , arm64: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: Regression or new test ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): rust-sqlx-sqlite rust-sqlx-core
    • Depends: rust-sqlx-sqlite rust-sqlx-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-sqlite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 103 days old (needed 5 days)
• rust-sudo-rs (- to 0.2.1-1)
  • Migration status for rust-sudo-rs (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sudo-rs/0.2.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sudo-rs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 103 days old (needed 5 days)
• gcc-mingw-w64 (25.2 to 26.1)
  • Migration status for gcc-mingw-w64 (25.2 to 26.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): gcc-mingw-w64 -> gcc-13-source/13.2.0-5/mips64el
    • Impossible Build-Depends(-Arch): gcc-mingw-w64 -> gnat-13/13.2.0-5/mips64el
    • missing build on mips64el
  • Additional info:
    • Updating gcc-mingw-w64 will fix bugs in testing: #1052220, #1054336
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-mingw-w64.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 104 days old (needed 5 days)
• gpaw (- to 23.9.1-1)
  • Migration status for gpaw (- to 23.9.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gpaw python-ase (not considered)
    • Depends: gpaw python-ase (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpaw.html
    • autopkgtest for gpaw/23.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 104 days old (needed 2 days)
• mkdocs-section-index (- to 0.3.8-1)
  • Migration status for mkdocs-section-index (- to 0.3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mkdocs-section-index python-mechanicalsoup (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocs-section-index.html
    • autopkgtest for mkdocs-section-index/0.3.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 104 days old (needed 2 days)
• x2gokdrive (- to 0.0.0.2-1)
  • Migration status for x2gokdrive (- to 0.0.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating x2gokdrive would introduce bugs in testing: #1054800
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2gokdrive.html
    • 104 days old (needed 5 days)
• partman-hfs (- to 11)
  • Migration status for partman-hfs (- to 11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • partman-hfs/amd64 has unsatisfiable dependency
    • partman-hfs/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 105 days old (needed 5 days)
• lxdm (- to 0.5.3-5)
  • Migration status for lxdm (- to 0.5.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lxdm would introduce bugs in testing: #1053089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxdm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• python-colorful (- to 0.5.5-1)
  • Migration status for python-colorful (- to 0.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sophieb, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-colorful.html
    • autopkgtest for python-colorful/0.5.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 106 days old (needed 2 days)
• rust-sqlx (- to 0.7.1-1)
  • Migration status for rust-sqlx (- to 0.7.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-sqlite (not considered)
    • Depends: rust-sqlx rust-sqlx-sqlite (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-core
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-macros
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-mysql
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-postgres
    • Depends: rust-sqlx rust-sqlx-core
    • Depends: rust-sqlx rust-sqlx-macros
    • Depends: rust-sqlx rust-sqlx-mysql
    • Depends: rust-sqlx rust-sqlx-postgres
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx.html
    • autopkgtest for rust-sqlx/0.7.1-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• rust-sqlx-macros (- to 0.7.1-1)
  • Migration status for rust-sqlx-macros (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sqlx-macros/0.7.1-1: amd64: No tests, superficial or marked flaky ♻ , arm64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-sqlx-macros rust-sqlx-core
    • Build-Depends(-Arch): rust-sqlx-macros rust-sqlx-macros-core
    • Depends: rust-sqlx-macros rust-sqlx-core
    • Depends: rust-sqlx-macros rust-sqlx-macros-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• rust-test-strategy (- to 0.3.1-1)
  • Migration status for rust-test-strategy (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-test-strategy/0.3.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by microjoe@microjoe.org
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-test-strategy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• rust-sqlx-macros-core (- to 0.7.1-2)
  • Migration status for rust-sqlx-macros-core (- to 0.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-sqlx-macros-core-dev/armel has unsatisfiable dependency
    • autopkgtest for rust-sqlx-macros-core/0.7.1-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-sqlx-macros-core rust-sqlx-core
    • Depends: rust-sqlx-macros-core rust-sqlx-core
    • Depends: rust-sqlx-macros-core rust-sqlx-mysql
    • Depends: rust-sqlx-macros-core rust-sqlx-postgres
    • Depends: rust-sqlx-macros-core rust-sqlx-sqlite
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-macros-core.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 108 days old (needed 5 days)
• pg-gvm (- to 22.6.2-1)
  • Migration status for pg-gvm (- to 22.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pg-gvm gvm-libs (not considered)
    • Depends: pg-gvm gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-gvm.html
    • autopkgtest for pg-gvm/22.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 109 days old (needed 2 days)
• rust-sqlx-postgres (- to 0.7.1-1)
  • Migration status for rust-sqlx-postgres (- to 0.7.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sqlx-postgres rust-sqlx-core (not considered)
    • Depends: rust-sqlx-postgres rust-sqlx-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-postgres.html
    • autopkgtest for rust-sqlx-postgres/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 109 days old (needed 2 days)
• graftcp (- to 0.3.1+ds1-2)
  • Migration status for graftcp (- to 0.3.1+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graftcp would introduce bugs in testing: #981713
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graftcp.html
    • Reproducible on amd64 - info ♻
    • 110 days old (needed 5 days)
• mono-tools (- to 4.2-3.2)
  • Migration status for mono-tools (- to 4.2-3.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: mono-tools cecil (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mono-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 110 days old (needed 5 days)
• pgpcre (- to 0.20190509-6)
  • Migration status for pgpcre (- to 0.20190509-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgpcre would introduce bugs in testing: #1000001
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgpcre.html
    • autopkgtest for pgpcre/0.20190509-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 110 days old (needed 2 days)
• rust-mozim (- to 0.2.2-1)
  • Migration status for rust-mozim (- to 0.2.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-mozim rust-etherparse (not considered)
    • Depends: rust-mozim rust-etherparse (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-mozim.html
    • autopkgtest for rust-mozim/0.2.2-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 110 days old (needed 5 days)
• check-patroni (- to 1.0.0-1)
  • Migration status for check-patroni (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-patroni.html
    • autopkgtest for check-patroni/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 114 days old (needed 2 days)
• deal.ii (- to 9.5.1-1)
  • Migration status for deal.ii (- to 9.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by sramacher
    • Trying to remove package, not update it
    • Updating deal.ii would introduce bugs in testing: #1059349
    • Depends: deal.ii gmsh
    • Depends: deal.ii petsc
    • Depends: deal.ii slepc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deal.ii.html
    • autopkgtest for deal.ii/9.5.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 114 days old (needed 2 days)
    • Remove hint for (transitive) dependency: deal.ii
• rust-etherparse (- to 0.13.0-1)
  • Migration status for rust-etherparse (- to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-etherparse/0.13.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-etherparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 114 days old (needed 5 days)
• rust-rustpython-common (- to 0.2.0-1)
  • Migration status for rust-rustpython-common (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-rustpython-common/0.2.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustpython-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 114 days old (needed 5 days)
• gpac (- to 2.2.1+dfsg1-3)
  • Migration status for gpac (- to 2.2.1+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpac would introduce bugs in testing: #1034732, #1051740, #1051866, #1051955, #1056282, #1059056
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpac.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 115 days old (needed 5 days)
• ocamldap (- to 2.4.2-5)
  • Migration status for ocamldap (- to 2.4.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocamldap pcre-ocaml (not considered)
    • Depends: ocamldap pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamldap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 117 days old (needed 5 days)
• opentsne (- to 1.0.0-1)
  • Migration status for opentsne (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opentsne would introduce bugs in testing: #1004706, #1056827
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for opentsne/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentsne.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 117 days old (needed 5 days)
• pyfai (- to 2023.9.0-1)
  • Migration status for pyfai (- to 2023.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfai would introduce bugs in testing: #1056438
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfai.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for pyfai/2023.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 117 days old (needed 2 days)
• icingaweb2-module-nagvis (- to 1.1.1-4)
  • Migration status for icingaweb2-module-nagvis (- to 1.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating icingaweb2-module-nagvis would introduce bugs in testing: #1057075
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/i/icingaweb2-module-nagvis.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 118 days old (needed 5 days)
• sqlacodegen (- to 3.0.0~rc3-1)
  • Migration status for sqlacodegen (- to 3.0.0~rc3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sqlacodegen sqlmodel (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlacodegen.html
    • autopkgtest for sqlacodegen/3.0.0~rc3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 118 days old (needed 2 days)
• genx (- to 3.6.22-2)
  • Migration status for genx (- to 3.6.22-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-genx/ppc64el has unsatisfiable dependency
    • autopkgtest for genx/3.6.22-2: amd64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genx.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 119 days old (needed 5 days)
• golang-github-jesseduffield-go-git (- to 5.1.2+git20221018.fdd53fe-1)
  • Migration status for golang-github-jesseduffield-go-git (- to 5.1.2+git20221018.fdd53fe-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by openarungeek@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-go-git.html
    • autopkgtest for golang-github-jesseduffield-go-git/5.1.2+git20221018.fdd53fe-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 119 days old (needed 2 days)
• haskell-hsyaml-aeson (- to 0.2.0.1-2)
  • Migration status for haskell-hsyaml-aeson (- to 0.2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-hsyaml-aeson would introduce bugs in testing: #1054961
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): haskell-hsyaml-aeson haskell-hsyaml
    • Build-Depends-Indep: haskell-hsyaml-aeson haskell-hsyaml
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsyaml-aeson.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 119 days old (needed 5 days)
• ocaml-lastfm (- to 0.3.3-4)
  • Migration status for ocaml-lastfm (- to 0.3.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocaml-lastfm pcre-ocaml (not considered)
    • Depends: ocaml-lastfm pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-lastfm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• readpe (- to 0.82-3)
  • Migration status for readpe (- to 0.82-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pev/n/a: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for readpe/0.82-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/readpe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 120 days old (needed 5 days)
• rust-timeago (- to 0.4.1-1)
  • Migration status for rust-timeago (- to 0.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-timeago rust-isolang (not considered)
    • Depends: rust-timeago rust-isolang (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-timeago.html
    • autopkgtest for rust-timeago/0.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 120 days old (needed 2 days)
• ukwm (- to 1.2.0-2.1)
  • Migration status for ukwm (- to 1.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ukwm would introduce bugs in testing: #1051425
    • Depends: ukwm ukui-settings-daemon
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukwm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• falcosecurity-libs (- to 0.11.3+repack-6)
  • Migration status for falcosecurity-libs (- to 0.11.3+repack-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating falcosecurity-libs would introduce bugs in testing: #1034881, #1057449, #1059256
    • autopkgtest for falcosecurity-libs/0.11.3+repack-6: amd64: No tests, superficial or marked flaky ♻ , arm64: Regression or new test ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): falcosecurity-libs valijson
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/falcosecurity-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 122 days old (needed 5 days)
• nomacs (- to 3.17.2282+dfsg-2)
  • Migration status for nomacs (- to 3.17.2282+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomacs would introduce bugs in testing: #1014124, #974616
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomacs.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 122 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: vuls golang-github-go-redis-redis (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): vuls go-cve-dictionary
    • Build-Depends(-Arch): vuls go-exploitdb
    • Build-Depends(-Arch): vuls gost
    • Build-Depends(-Arch): vuls goval-dictionary
    • Built-Using: vuls go-cve-dictionary
    • Built-Using: vuls go-exploitdb
    • Built-Using: vuls gost
    • Built-Using: vuls goval-dictionary
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuls.html
    • autopkgtest for vuls/0.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 122 days old (needed 2 days)
• pytorch-vision (- to 0.15.2-1)
  • Migration status for pytorch-vision (- to 0.15.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytorch-vision would introduce bugs in testing: #1051811
    • autopkgtest for pytorch-vision/0.15.2-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-vision.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 123 days old (needed 5 days)
• clickhouse (- to 18.16.1+ds-7.4)
  • Migration status for clickhouse (- to 18.16.1+ds-7.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clickhouse would introduce bugs in testing: #1059261
    • Build-Depends(-Arch): clickhouse poco
    • Depends: clickhouse poco
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clickhouse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 124 days old (needed 5 days)
• prometheus-varnish-exporter (- to 1.6.1-2)
  • Migration status for prometheus-varnish-exporter (- to 1.6.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prometheus-varnish-exporter varnish (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-varnish-exporter.html
    • autopkgtest for prometheus-varnish-exporter/1.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 124 days old (needed 2 days)
• gnome-shell-extension-weather (- to 121-1)
  • Migration status for gnome-shell-extension-weather (- to 121-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-weather would introduce bugs in testing: #1052111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-weather.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 126 days old (needed 5 days)
• mailman3 (- to 3.3.8-3.1)
  • Migration status for mailman3 (- to 3.3.8-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailman3 flufl.i18n (not considered)
    • Depends: mailman3 flufl.i18n (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): mailman3 flufl.bounce
    • Depends: mailman3 flufl.bounce
    • Depends: mailman3 mailman-hyperkitty
    • Depends: mailman3 mailman-suite
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mailman3.html
    • autopkgtest for mailman3/3.3.8-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 127 days old (needed 2 days)
• ocaml-http (- to 0.1.6-2)
  • Migration status for ocaml-http (- to 0.1.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocaml-http pcre-ocaml (not considered)
    • Depends: ocaml-http pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-http.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 127 days old (needed 5 days)
• ocamlsdl (- to 0.9.1-4)
  • Migration status for ocamlsdl (- to 0.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocamlsdl would introduce bugs in testing: #1038076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlsdl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 127 days old (needed 5 days)
• rust-rustpython-ast (- to 0.2.0-1)
  • Migration status for rust-rustpython-ast (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-rustpython-ast rust-rustpython-common (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustpython-ast.html
    • autopkgtest for rust-rustpython-ast/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 127 days old (needed 2 days)
• frr (- to 8.4.4-1.1)
  • Migration status for frr (- to 8.4.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating frr would introduce bugs in testing: #1055852
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
    • autopkgtest for frr/8.4.4-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 128 days old (needed 2 days)
• gtsam (- to 4.2~9+dfsg-6)
  • Migration status for gtsam (- to 4.2~9+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtsam would introduce bugs in testing: #1055683, #1056078
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtsam.html
    • 128 days old (needed 5 days)
• ormar (- to 0.12.2-1)
  • Migration status for ormar (- to 0.12.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ormar fastapi (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ormar.html
    • autopkgtest for ormar/0.12.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 128 days old (needed 2 days)
• sqlmodel (- to 0.0.8-5)
  • Migration status for sqlmodel (- to 0.0.8-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sqlmodel fastapi (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlmodel.html
    • autopkgtest for sqlmodel/0.0.8-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 129 days old (needed 2 days)
• trocla (- to 0.5.1-2)
  • Migration status for trocla (- to 0.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): trocla ruby-moneta (not considered)
    • Depends: trocla ruby-moneta (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trocla.html
    • autopkgtest for trocla/0.5.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 129 days old (needed 2 days)
• docstring-parser (- to 0.15-3)
  • Migration status for docstring-parser (- to 0.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for docstring-parser/0.15-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docstring-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 130 days old (needed 5 days)
• napari (- to 0.5.0~a1-4)
  • Migration status for napari (- to 0.5.0~a1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): napari magicgui (not considered)
    • Depends: napari magicgui (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): napari docstring-parser
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • autopkgtest for napari/0.5.0~a1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 130 days old (needed 2 days)
• python-django-pgtrigger (- to 4.7.0-1)
  • Migration status for python-django-pgtrigger (- to 4.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-pgtrigger.html
    • autopkgtest for python-django-pgtrigger/4.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 130 days old (needed 2 days)
• docbook-defguide (- to 2.0.17+svn9912-3)
  • Migration status for docbook-defguide (- to 2.0.17+svn9912-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating docbook-defguide would introduce bugs in testing: #1031512
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docbook-defguide.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• x2goclient (- to 4.1.2.3-1)
  • Migration status for x2goclient (- to 4.1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating x2goclient would introduce bugs in testing: #1042816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2goclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• python-rioxarray (- to 0.15.0-4)
  • Migration status for python-rioxarray (- to 0.15.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-rioxarray python-xarray (not considered)
    • Depends: python-rioxarray python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rioxarray.html
    • autopkgtest for python-rioxarray/0.15.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 132 days old (needed 2 days)
• worker (- to 4.12.1-1)
  • Migration status for worker (- to 4.12.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): worker avfs (not considered)
    • Depends: worker avfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/worker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 132 days old (needed 5 days)
• repetier-host (- to 0.85+dfsg-5)
  • Migration status for repetier-host (- to 0.85+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): repetier-host opentk (not considered)
    • Depends: repetier-host opentk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/repetier-host.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 133 days old (needed 5 days)
• valijson (- to 1.0+repack-3)
  • Migration status for valijson (- to 1.0+repack-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): valijson poco (not considered)
    • Depends: valijson poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valijson.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 133 days old (needed 5 days)
• python3.10 (- to 3.10.13-1)
  • Migration status for python3.10 (- to 3.10.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • idle-python3.10/amd64 has unsatisfiable dependency
    • python3.10-full/amd64 has unsatisfiable dependency
    • python3.10-venv/amd64 has unsatisfiable dependency
    • idle-python3.10/arm64 has unsatisfiable dependency
    • python3.10-full/arm64 has unsatisfiable dependency
    • python3.10-venv/arm64 has unsatisfiable dependency
    • python3.10-full/armel has unsatisfiable dependency
    • python3.10-venv/armel has unsatisfiable dependency
    • python3.10-full/armhf has unsatisfiable dependency
    • python3.10-venv/armhf has unsatisfiable dependency
    • python3.10-full/i386 has unsatisfiable dependency
    • python3.10-venv/i386 has unsatisfiable dependency
    • python3.10-full/mips64el has unsatisfiable dependency
    • python3.10-venv/mips64el has unsatisfiable dependency
    • python3.10-full/ppc64el has unsatisfiable dependency
    • python3.10-venv/ppc64el has unsatisfiable dependency
    • python3.10-full/s390x has unsatisfiable dependency
    • python3.10-venv/s390x has unsatisfiable dependency
    • Updating python3.10 would introduce bugs in testing: #1030530, #1031969
    • Build-Depends(-Arch): python3.10 mpdecimal
    • Depends: python3.10 mpdecimal
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python3.10.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 135 days old (needed 5 days)
• bind-dyndb-ldap (- to 11.10-6)
  • Migration status for bind-dyndb-ldap (- to 11.10-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bind9-dyndb-ldap/amd64 has unsatisfiable dependency
    • bind9-dyndb-ldap/arm64 has unsatisfiable dependency
    • bind9-dyndb-ldap/armel has unsatisfiable dependency
    • bind9-dyndb-ldap/armhf has unsatisfiable dependency
    • bind9-dyndb-ldap/i386 has unsatisfiable dependency
    • bind9-dyndb-ldap/mips64el has unsatisfiable dependency
    • bind9-dyndb-ldap/ppc64el has unsatisfiable dependency
    • bind9-dyndb-ldap/s390x has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/bind-dyndb-ldap.html
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 136 days old (needed 5 days)
• emacs-jedi (- to 0.2.8+git20220410.81c5a42-1)
  • Migration status for emacs-jedi (- to 0.2.8+git20220410.81c5a42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-jedi would introduce bugs in testing: #994171
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-jedi.html
    • autopkgtest for emacs-jedi/0.2.8+git20220410.81c5a42-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 138 days old (needed 2 days)
• gnome-shell-extension-bluetooth-quick-connect (- to 36-2)
  • Migration status for gnome-shell-extension-bluetooth-quick-connect (- to 36-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-bluetooth-quick-connect would introduce bugs in testing: #1052090
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-bluetooth-quick-connect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 139 days old (needed 5 days)
• libgpuarray (- to 0.7.6-14)
  • Migration status for libgpuarray (- to 0.7.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgpuarray would introduce bugs in testing: #1031414, #1055690, #1056811
    • autopkgtest for libgpuarray/0.7.6-14: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgpuarray.html
    • Reproducible on i386 - info ♻
    • 139 days old (needed 5 days)
• node-socks-proxy-agent (- to 7.0.0+dfsg+~cs2.0.11-1)
  • Migration status for node-socks-proxy-agent (- to 7.0.0+dfsg+~cs2.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • node-socks-proxy-agent has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 140 days old (needed 5 days)
• python-emmet-core (- to 0.57.1-2)
  • Migration status for python-emmet-core (- to 0.57.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-emmet-core would introduce bugs in testing: #1058225
    • Build-Depends(-Arch): python-emmet-core pymatgen
    • Depends: python-emmet-core pymatgen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-emmet-core.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for python-emmet-core/0.57.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 140 days old (needed 2 days)
• python-mp-api (- to 0.34.3-1)
  • Migration status for python-mp-api (- to 0.34.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-mp-api python-emmet-core (not considered)
    • Depends: python-mp-api python-emmet-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): python-mp-api pymatgen
    • Depends: python-mp-api pymatgen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mp-api.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for python-mp-api/0.34.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 140 days old (needed 2 days)
• sendxmpp (- to 1.24-4)
  • Migration status for sendxmpp (- to 1.24-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sendxmpp libnet-xmpp-perl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sendxmpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 days old (needed 5 days)
• hinawa-utils (- to 0.3.0-3)
  • Migration status for hinawa-utils (- to 0.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hinawa-utils would introduce bugs in testing: #1056354
    • Impossible Depends: hinawa-utils -> gir1.2-hinawa-3.0/2.6.1-1/amd64
    • Impossible Depends: hinawa-utils -> gir1.2-hinawa-3.0/2.6.1-1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hinawa-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• node-lockfile (- to 1.0.4+~1.0.2-3)
  • Migration status for node-lockfile (- to 1.0.4+~1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-lockfile would introduce bugs in testing: #1005940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-lockfile.html
    • autopkgtest for node-lockfile/1.0.4+~1.0.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 141 days old (needed 2 days)
• python-maturin (- to 1.1.0-1)
  • Migration status for python-maturin (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-maturin would introduce bugs in testing: #1052912
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-maturin.html
    • autopkgtest for python-maturin/1.1.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • 141 days old (needed 5 days)
• geary (- to 44.1-1)
  • Migration status for geary (- to 44.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for geary/44.1-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geary.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 142 days old (needed 5 days)
• pyfftw (- to 0.13.1-1)
  • Migration status for pyfftw (- to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfftw would introduce bugs in testing: #1055703, #1056836
    • autopkgtest for pyfftw/0.13.1-1: amd64: Pass, arm64: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfftw.html
    • Reproducible on i386 - info ♻
    • 142 days old (needed 5 days)
• bioxtasraw (- to 2.2.1-1)
  • Migration status for bioxtasraw (- to 2.2.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): bioxtasraw pyfai (not considered)
    • Depends: bioxtasraw pyfai (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bioxtasraw.html
    • autopkgtest for bioxtasraw/2.2.1-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• go-cve-dictionary (- to 0.3.1-5)
  • Migration status for go-cve-dictionary (- to 0.3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Depends: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-cve-dictionary.html
    • autopkgtest for go-cve-dictionary/0.3.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• golang-github-jesseduffield-termbox-go (- to 0.0~git20200823.a2289ed-1)
  • Migration status for golang-github-jesseduffield-termbox-go (- to 0.0~git20200823.a2289ed-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-termbox-go would introduce bugs in testing: #1032114
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-termbox-go.html
    • autopkgtest for golang-github-jesseduffield-termbox-go/0.0~git20200823.a2289ed-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gost golang-github-go-redis-redis (not considered)
    • Built-Using: gost golang-github-go-redis-redis (not considered)
    • Depends: gost golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gost.html
    • autopkgtest for gost/0.1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): goval-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: goval-dictionary golang-github-go-redis-redis (not considered)
    • Depends: goval-dictionary golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goval-dictionary.html
    • autopkgtest for goval-dictionary/0.2.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• ocaml-odoc-parser (- to 2.0.0-3)
  • Migration status for ocaml-odoc-parser (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ocaml-odoc-parser has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• pcre-ocaml (- to 7.5.0-3)
  • Migration status for pcre-ocaml (- to 7.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcre-ocaml would introduce bugs in testing: #1000004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcre-ocaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• tomopy (- to 1.14.1+ds1-1)
  • Migration status for tomopy (- to 1.14.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomopy would introduce bugs in testing: #1032045, #1036684
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for tomopy/1.14.1+ds1-1: amd64: Pass, armel: Pass, armhf: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• cataclysm-dda (- to 0.G-4)
  • Migration status for cataclysm-dda (- to 0.G-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cataclysm-dda cool-retro-term (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cataclysm-dda.html
    • autopkgtest for cataclysm-dda/0.G-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 144 days old (needed 2 days)
• go-exploitdb (- to 0.0~git20181130.7c961e7-3)
  • Migration status for go-exploitdb (- to 0.0~git20181130.7c961e7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-github-go-redis-redis (not considered)
    • Depends: go-exploitdb golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-exploitdb.html
    • autopkgtest for go-exploitdb/0.0~git20181130.7c961e7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 144 days old (needed 2 days)
• python-discord (- to 2.3.2+dfsg-2)
  • Migration status for python-discord (- to 2.3.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-discord would introduce bugs in testing: #1057608
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-discord.html
    • autopkgtest for python-discord/2.3.2+dfsg-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 144 days old (needed 5 days)
• redmine-plugin-local-avatars (- to 1.0.6-1)
  • Migration status for redmine-plugin-local-avatars (- to 1.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-local-avatars redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-local-avatars.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 144 days old (needed 5 days)
• redmine-plugin-pretend (- to 1.0-2)
  • Migration status for redmine-plugin-pretend (- to 1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-pretend redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-pretend.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 144 days old (needed 5 days)
• binutils-mipsen (10+c4 to 10+c5)
  • Migration status for binutils-mipsen (10+c4 to 10+c5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Updating binutils-mipsen will fix bugs in testing: #1052345
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-mipsen.html
    • 145 days old (needed 5 days)
• cross-toolchain-base-mipsen (24 to 26)
  • Migration status for cross-toolchain-base-mipsen (24 to 26): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cross-toolchain-base-mipsen unsatisfiable Build-Depends(-Arch) on amd64: linux-source-6.4 (>= 6.4.4)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating cross-toolchain-base-mipsen will fix bugs in testing: #1042033, #1052344
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cross-toolchain-base-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 145 days old (needed 5 days)
• gcc-13-cross-mipsen (- to 1+c3)
  • Migration status for gcc-13-cross-mipsen (- to 1+c3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-13-cross-mipsen would introduce bugs in testing: #1040626
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mips-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mipsel-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mips64el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mips64-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mipsisa32r6-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mipsisa32r6el-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mipsisa64r6-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: binutils-mipsisa64r6el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on amd64: gccrs-13
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mips-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mipsel-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mips64el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mips64-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mipsisa32r6-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mipsisa32r6el-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mipsisa64r6-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: binutils-mipsisa64r6el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on arm64: gccrs-13
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mips-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mipsel-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mips64el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mips64-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mipsisa32r6-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mipsisa32r6el-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mipsisa64r6-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: binutils-mipsisa64r6el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on i386: gccrs-13
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mips-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mipsel-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mips64-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mipsisa32r6-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mipsisa32r6el-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mipsisa64r6-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: binutils-mipsisa64r6el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on mips64el: gccrs-13
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mips-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mipsel-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mips64el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mips64-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mipsisa32r6-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mipsisa32r6el-linux-gnu (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mipsisa64r6-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel mips64r6el arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: binutils-mipsisa64r6el-linux-gnuabi64 (>= 2.41~) [amd64 i386 x32 mips64el mipsel arm64 ppc64el]
    • gcc-13-cross-mipsen unsatisfiable Build-Depends(-Arch) on ppc64el: gccrs-13
    • Impossible Build-Depends(-Arch): gcc-13-cross-mipsen -> gcc-13-source/13.2.0-5/mips64el
    • Impossible Build-Depends(-Arch): gcc-13-cross-mipsen -> gnat-13/13.2.0-5/mips64el
    • missing build on amd64
    • missing build on arm64
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-13-cross-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 145 days old (needed 5 days)
• libengine-gost-openssl (- to 3.0.2-1)
  • Migration status for libengine-gost-openssl (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libengine-gost-openssl would introduce bugs in testing: #1054922
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• magicgui (- to 0.7.2-3)
  • Migration status for magicgui (- to 0.7.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for magicgui/0.7.2-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): magicgui docstring-parser
    • Depends: magicgui docstring-parser
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magicgui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• qbrz (- to 0.23.2+bzr1659-1)
  • Migration status for qbrz (- to 0.23.2+bzr1659-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qbrz would introduce bugs in testing: #1053787
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qbrz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 146 days old (needed 5 days)
• rust-isahc (- to 1.7.2+ds-24)
  • Migration status for rust-isahc (- to 1.7.2+ds-24): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-isahc/1.7.2+ds-24: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-isahc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 146 days old (needed 5 days)
• searx (- to 1.1.0+dfsg1-2)
  • Migration status for searx (- to 1.1.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating searx would introduce bugs in testing: #1051510
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx.html
    • autopkgtest for searx/1.1.0+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 146 days old (needed 2 days)
• pox (- to 0.3.3-1)
  • Migration status for pox (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pox.html
    • autopkgtest for pox/0.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 147 days old (needed 2 days)
• fastapi (- to 0.101.0-1)
  • Migration status for fastapi (- to 0.101.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fastapi would introduce bugs in testing: #1054764
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastapi.html
    • autopkgtest for fastapi/0.101.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 149 days old (needed 2 days)
• gcc-arm-none-eabi (15:12.2.rel1-1 to 15:12.3.rel1-1)
  • Migration status for gcc-arm-none-eabi (15:12.2.rel1-1 to 15:12.3.rel1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-arm-none-eabi would introduce bugs in testing: #1050327
    • migrating gcc-arm-none-eabi/15:12.3.rel1-1/amd64 to testing makes libstdc++-arm-none-eabi-dev/15:12.2.rel1-1+23/amd64 uninstallable
    • migrating gcc-arm-none-eabi/15:12.3.rel1-1/amd64 to testing makes libstdc++-arm-none-eabi-newlib/15:12.2.rel1-1+23/amd64 uninstallable
    • migrating gcc-arm-none-eabi/15:12.3.rel1-1/amd64 to testing makes libstdc++-arm-none-eabi-picolibc/15:12.2.rel1-1+23/amd64 uninstallable
    • migrating gcc-arm-none-eabi/15:12.3.rel1-1/arm64 to testing makes libstdc++-arm-none-eabi-dev/15:12.2.rel1-1+23/arm64 uninstallable
    • migrating gcc-arm-none-eabi/15:12.3.rel1-1/arm64 to testing makes libstdc++-arm-none-eabi-newlib/15:12.2.rel1-1+23/arm64 uninstallable
    • migrating gcc-arm-none-eabi/15:12.3.rel1-1/arm64 to testing makes libstdc++-arm-none-eabi-picolibc/15:12.2.rel1-1+23/arm64 uninstallable
    • autopkgtest for binutils-arm-none-eabi/21: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for binutils-riscv64-unknown-elf/6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for gcc-arm-none-eabi/15:12.3.rel1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for libstdc++-arm-none-eabi/23: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for newlib/3.3.0-1.3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating gcc-arm-none-eabi will fix bugs in testing: #1052340
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-arm-none-eabi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 149 days old (needed 5 days)
• tomcatjss (- to 8.4.0-2)
  • Migration status for tomcatjss (- to 8.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomcatjss would introduce bugs in testing: #1031816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcatjss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 149 days old (needed 5 days)
• fanwor (- to 1.16-1)
  • Migration status for fanwor (- to 1.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fanwor would introduce bugs in testing: #1055538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fanwor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 150 days old (needed 5 days)
• libapache-mod-auth-kerb (- to 5.4-3)
  • Migration status for libapache-mod-auth-kerb (- to 5.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-mod-auth-kerb would introduce bugs in testing: #976156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-auth-kerb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 150 days old (needed 5 days)
• eln (- to 1.5.2-1)
  • Migration status for eln (- to 1.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eln unsatisfiable Build-Depends(-Arch) on armel: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on armel: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on armel: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on armel: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qt6-webengine-dev
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qml6-module-qtwebengine
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eln.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 151 days old (needed 5 days)
• pycryptodome (3.11.0+dfsg1-4 to 3.18.0+dfsg1-1)
  • Migration status for pycryptodome (3.11.0+dfsg1-4 to 3.18.0+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pycryptodome would introduce bugs in testing: #1053328, #1056436
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for pycryptodome/3.18.0+dfsg1-1: amd64: Pass, i386: Pass
  • Additional info:
    • Updating pycryptodome will fix bugs in testing: #1052336
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycryptodome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 151 days old (needed 5 days)
• aircrack-ng (- to 1:1.7+git20230807.4bf83f1a-1)
  • Migration status for aircrack-ng (- to 1:1.7+git20230807.4bf83f1a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aircrack-ng would introduce bugs in testing: #1051201
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aircrack-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• freebsd-buildutils (- to 10.3~svn296373-7.1)
  • Migration status for freebsd-buildutils (- to 10.3~svn296373-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freebsd-buildutils unsatisfiable Build-Depends(-Arch) on mips64el: gcc-9
    • missing build on mips64el
    • Build-Depends(-Arch): freebsd-buildutils freebsd-glue
    • Build-Depends(-Arch): freebsd-buildutils freebsd-libs
    • Build-Depends(-Arch): freebsd-buildutils gcc-9
    • Depends: freebsd-buildutils freebsd-glue
    • Depends: freebsd-buildutils freebsd-libs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-buildutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• itop (- to 0.1-4.1)
  • Migration status for itop (- to 0.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating itop would introduce bugs in testing: #904206
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• klepto (- to 0.2.4-1)
  • Migration status for klepto (- to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): klepto pox
    • Depends: klepto pox
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klepto.html
    • autopkgtest for klepto/0.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 152 days old (needed 2 days)
• mystic (- to 0.4.1-1)
  • Migration status for mystic (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mystic would introduce bugs in testing: #1056429
    • autopkgtest for mystic/0.4.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): mystic klepto
    • Depends: mystic klepto
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mystic.html
    • 152 days old (needed 5 days)
• nabu (- to 2023.1.1-3)
  • Migration status for nabu (- to 2023.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nabu/2023.1.1-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻
    • Build-Depends(-Arch): nabu tomoscan
    • Depends: nabu tomoscan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nabu.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 152 days old (needed 5 days)
• pathos (- to 0.3.1-1)
  • Migration status for pathos (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): pathos pox
    • Build-Depends(-Arch): pathos ppft
    • Depends: pathos pox
    • Depends: pathos ppft
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pathos.html
    • autopkgtest for pathos/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 152 days old (needed 2 days)
• ppft (- to 1.7.6.7+dfsg-1)
  • Migration status for ppft (- to 1.7.6.7+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ppft.html
    • autopkgtest for ppft/1.7.6.7+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 152 days old (needed 2 days)
• pyina (- to 0.2.8-1)
  • Migration status for pyina (- to 0.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): pyina pathos
    • Build-Depends(-Arch): pyina pox
    • Depends: pyina pathos
    • Depends: pyina pox
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyina.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• freebsd-glue (- to 0.2.22+nmu1)
  • Migration status for freebsd-glue (- to 0.2.22+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freebsd-glue unsatisfiable Build-Depends(-Arch) on mips64el: gcc-9
    • missing build on mips64el
    • Build-Depends(-Arch): freebsd-glue freebsd-buildutils
    • Build-Depends(-Arch): freebsd-glue gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-glue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 153 days old (needed 5 days)
• kodi (- to 2:20.2+dfsg-4)
  • Migration status for kodi (- to 2:20.2+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kodi would introduce bugs in testing: #1000113
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi.html
    • autopkgtest for kodi/2:20.2+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 154 days old (needed 2 days)
• kodi-imagedecoder-heif (- to 20.1.0+ds1-3)
  • Migration status for kodi-imagedecoder-heif (- to 20.1.0+ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-imagedecoder-heif kodi (not considered)
    • Depends: kodi-imagedecoder-heif kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-imagedecoder-heif.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• kodi-inputstream-adaptive (- to 20.3.11+ds-1)
  • Migration status for kodi-inputstream-adaptive (- to 20.3.11+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): kodi-inputstream-adaptive kodi
    • Depends: kodi-inputstream-adaptive kodi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-inputstream-adaptive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• kodi-inputstream-ffmpegdirect (- to 20.5.0+ds1-2)
  • Migration status for kodi-inputstream-ffmpegdirect (- to 20.5.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-inputstream-ffmpegdirect kodi (not considered)
    • Depends: kodi-inputstream-ffmpegdirect kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-inputstream-ffmpegdirect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• chkservice (- to 0.3-1.1)
  • Migration status for chkservice (- to 0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chkservice would introduce bugs in testing: #988094
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chkservice.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 155 days old (needed 5 days)
• cpupower-gui (- to 0.7.2-2.1)
  • Migration status for cpupower-gui (- to 0.7.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpupower-gui would introduce bugs in testing: #1025555
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpupower-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 155 days old (needed 5 days)
• criu (- to 3.17.1-3)
  • Migration status for criu (- to 3.17.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating criu would introduce bugs in testing: #1054814
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/criu.html
    • 155 days old (needed 5 days)
• oss4 (- to 4.2-build2020-2)
  • Migration status for oss4 (- to 4.2-build2020-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oss4 would introduce bugs in testing: #796636
    • Not built on buildd: arch amd64 binaries uploaded by sthibault
    • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oss4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 155 days old (needed 5 days)
• avfs (- to 1.1.5-1)
  • Migration status for avfs (- to 1.1.5-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 156 days old (needed 5 days)
• tomoscan (- to 1.2.2-2)
  • Migration status for tomoscan (- to 1.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tomoscan/1.2.2-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoscan.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• oce (- to 0.18.3-4)
  • Migration status for oce (- to 0.18.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oce would introduce bugs in testing: #1036879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oce.html
    • autopkgtest for oce/0.18.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 158 days old (needed 2 days)
• newsboat (- to 2.32-3)
  • Migration status for newsboat (- to 2.32-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newsboat would introduce bugs in testing: #1054680
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newsboat.html
    • autopkgtest for newsboat/2.32-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 161 days old (needed 2 days)
• lomiri (- to 0.1.3-1)
  • Migration status for lomiri (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lomiri would introduce bugs in testing: #1059017
    • Build-Depends(-Arch): lomiri libusermetrics
    • Depends: lomiri ayatana-indicator-display
    • Depends: lomiri libusermetrics
    • Depends: lomiri lomiri-telephony-service
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri.html
    • Reproducible on amd64 - info ♻
    • 163 days old (needed 5 days)
• r-bioc-demixt (- to 1.16.0+dfsg-1)
  • Migration status for r-bioc-demixt (- to 1.16.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-bioc-demixt/amd64 has unsatisfiable dependency
    • r-bioc-demixt/arm64 has unsatisfiable dependency
    • r-bioc-demixt/armel has unsatisfiable dependency
    • r-bioc-demixt/armhf has unsatisfiable dependency
    • r-bioc-demixt/i386 has unsatisfiable dependency
    • r-bioc-demixt/mips64el has unsatisfiable dependency
    • r-bioc-demixt/ppc64el has unsatisfiable dependency
    • r-bioc-demixt/s390x has unsatisfiable dependency
    • Updating r-bioc-demixt would introduce bugs in testing: #1058278
    • Build-Depends(-Arch): r-bioc-demixt r-bioc-dss
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-demixt.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 163 days old (needed 5 days)
• r-bioc-dss (- to 2.48.0+dfsg-1)
  • Migration status for r-bioc-dss (- to 2.48.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-bioc-dss/amd64 has unsatisfiable dependency
    • r-bioc-dss/arm64 has unsatisfiable dependency
    • r-bioc-dss/armel has unsatisfiable dependency
    • r-bioc-dss/armhf has unsatisfiable dependency
    • r-bioc-dss/i386 has unsatisfiable dependency
    • r-bioc-dss/mips64el has unsatisfiable dependency
    • r-bioc-dss/ppc64el has unsatisfiable dependency
    • r-bioc-dss/s390x has unsatisfiable dependency
    • Updating r-bioc-dss would introduce bugs in testing: #1058613
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dss.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 163 days old (needed 5 days)
• libusermetrics (- to 1.3.0-2)
  • Migration status for libusermetrics (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libusermetrics would introduce bugs in testing: #1054997
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libusermetrics.html
    • 164 days old (needed 5 days)
• bitsnpicas (- to 2.0+ds-2)
  • Migration status for bitsnpicas (- to 2.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bitsnpicas would introduce bugs in testing: #1041435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitsnpicas.html
    • 167 days old (needed 5 days)
• haskell-swish (- to 0.10.4.0-1)
  • Migration status for haskell-swish (- to 0.10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-swish-doc/amd64 has unsatisfiable dependency
    • libghc-swish-doc/arm64 has unsatisfiable dependency
    • libghc-swish-dev/mips64el has unsatisfiable dependency
    • libghc-swish-prof/mips64el has unsatisfiable dependency
    • Updating haskell-swish would introduce bugs in testing: #1058746
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-swish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 167 days old (needed 5 days)
• mythtv-status (- to 1.1.0-1)
  • Migration status for mythtv-status (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mythtv-status would introduce bugs in testing: #1052282
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mythtv-status.html
    • autopkgtest for mythtv-status/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 169 days old (needed 2 days)
• ocaml-mm (- to 0.8.4-2)
  • Migration status for ocaml-mm (- to 0.8.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocaml-mm ocamlsdl (not considered)
    • Depends: ocaml-mm ocamlsdl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-mm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 170 days old (needed 5 days)
• openjdk-20 (- to 20.0.2+9-1)
  • Migration status for openjdk-20 (- to 20.0.2+9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-20 would introduce bugs in testing: #1031889
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-20.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-20/20.0.2+9-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 170 days old (needed 5 days)
• pyrlp (- to 0.5.1-4)
  • Migration status for pyrlp (- to 0.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyrlp would introduce bugs in testing: #1056442
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrlp.html
    • autopkgtest for pyrlp/0.5.1-4: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 170 days old (needed 5 days)
• ctfutils (- to 10.3~svn297264-2.1)
  • Migration status for ctfutils (- to 10.3~svn297264-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ctfutils freebsd-libs (not considered)
    • Depends: ctfutils freebsd-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ctfutils freebsd-buildutils
    • Build-Depends(-Arch): ctfutils freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctfutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 171 days old (needed 5 days)
• python-package-smoke-test (- to 1.0-1)
  • Migration status for python-package-smoke-test (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-package-smoke-test.html
    • autopkgtest for python-package-smoke-test/1.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 171 days old (needed 5 days)
• rust-loom (- to 0.5.6-1)
  • Migration status for rust-loom (- to 0.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-loom-dev/amd64 has unsatisfiable dependency
    • librust-loom-dev/arm64 has unsatisfiable dependency
    • Updating rust-loom would introduce bugs in testing: #1054724
    • rust-loom unsatisfiable Build-Depends(-Arch) on amd64: librust-tracing-subscriber-0.3+env-filter-dev
    • rust-loom unsatisfiable Build-Depends(-Arch) on arm64: librust-tracing-subscriber-0.3+env-filter-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-loom.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 171 days old (needed 5 days)
• debian-parl (- to 1.9.31+nmu1)
  • Migration status for debian-parl (- to 1.9.31+nmu1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-parl syncevolution (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-parl.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 172 days old (needed 5 days)
• gcc-10 (- to 10.5.0-2)
  • Migration status for gcc-10 (- to 10.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10 would introduce bugs in testing: #1023666
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10.html
    • autopkgtest for gcc-10/10.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 173 days old (needed 2 days)
• supertuxkart (- to 1.4+dfsg-3)
  • Migration status for supertuxkart (- to 1.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating supertuxkart would introduce bugs in testing: #1057463
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/supertuxkart.html
    • 175 days old (needed 5 days)
• sysdig (- to 0.32.0-1)
  • Migration status for sysdig (- to 0.32.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sysdig unsatisfiable Build-Depends(-Arch) on armel: libfalcosecurity0-dev (>= 0.11.3)
    • sysdig unsatisfiable Build-Depends(-Arch) on armhf: libfalcosecurity0-dev (>= 0.11.3)
    • sysdig unsatisfiable Build-Depends(-Arch) on i386: libfalcosecurity0-dev (>= 0.11.3)
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): sysdig falcosecurity-libs
    • Depends: sysdig falcosecurity-libs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysdig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 175 days old (needed 5 days)
• gcc-12-cross-mipsen (3+c3 to 4+c1)
  • Migration status for gcc-12-cross-mipsen (3+c3 to 4+c1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gcc-12-cross-mipsen gcc-13-cross-mipsen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating gcc-12-cross-mipsen will fix bugs in testing: #1049444
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-12-cross-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 176 days old (needed 5 days)
• renderdoc (- to 1.27+dfsg-1)
  • Migration status for renderdoc (- to 1.27+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating renderdoc would introduce bugs in testing: #999924
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 176 days old (needed 5 days)
• rust-packed-simd (- to 0.3.8-1)
  • Migration status for rust-packed-simd (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-packed-simd/0.3.8-1: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-packed-simd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 176 days old (needed 5 days)
• gcc-9 (- to 9.5.0-4)
  • Migration status for gcc-9 (- to 9.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9 would introduce bugs in testing: #994108
    • missing build on mips64el
    • Build-Depends(-Arch): gcc-9 gcc-10
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9.html
    • autopkgtest for gcc-9/9.5.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 177 days old (needed 2 days)
• gcc-9-cross (- to 29)
  • Migration status for gcc-9-cross (- to 29): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross would introduce bugs in testing: #1032217, #994134
    • Build-Depends(-Arch): gcc-9-cross autoconf2.64
    • Build-Depends(-Arch): gcc-9-cross gcc-9
    • Built-Using: gcc-9-cross gcc-9
    • Depends: gcc-9-cross gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 177 days old (needed 5 days)
• gcc-9-cross-ports (- to 27)
  • Migration status for gcc-9-cross-ports (- to 27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross-ports would introduce bugs in testing: #1032216, #994135
    • Build-Depends(-Arch): gcc-9-cross-ports autoconf2.64
    • Build-Depends(-Arch): gcc-9-cross-ports gcc-9
    • Built-Using: gcc-9-cross-ports gcc-9
    • Depends: gcc-9-cross-ports gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross-ports.html
    • 177 days old (needed 5 days)
• ruby-appraiser-rubocop (- to 1.0.1-2)
  • Migration status for ruby-appraiser-rubocop (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-appraiser-rubocop/amd64 has unsatisfiable dependency
    • ruby-appraiser-rubocop/arm64 has unsatisfiable dependency
    • Updating ruby-appraiser-rubocop would introduce bugs in testing: #1054166
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-appraiser-rubocop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 177 days old (needed 5 days)
• python-molotov (- to 2.1-6)
  • Migration status for python-molotov (- to 2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-molotov would introduce bugs in testing: #1056484
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-molotov.html
    • autopkgtest for python-molotov/2.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 178 days old (needed 2 days)
• gcc-10-cross-mipsen (- to 3+c6)
  • Migration status for gcc-10-cross-mipsen (- to 3+c6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • g++-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • Updating gcc-10-cross-mipsen would introduce bugs in testing: #1032218, #1040624
    • Build-Depends(-Arch): gcc-10-cross-mipsen gcc-10
    • Built-Using: gcc-10-cross-mipsen gcc-10
    • Depends: gcc-10-cross-mipsen gcc-10
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 179 days old (needed 5 days)
• golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1)
  • Migration status for golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by foka, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-terraform-registry-address.html
    • autopkgtest for golang-github-hashicorp-terraform-registry-address/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 179 days old (needed 2 days)
• python-ocspbuilder (- to 0.10.2-2)
  • Migration status for python-ocspbuilder (- to 0.10.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ocspbuilder would introduce bugs in testing: #1056489, #1058344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ocspbuilder.html
    • autopkgtest for python-ocspbuilder/0.10.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 179 days old (needed 2 days)
• python-pyomop (- to 3.2.0-2)
  • Migration status for python-pyomop (- to 3.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-pyomop sqlacodegen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyomop.html
    • autopkgtest for python-pyomop/3.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 179 days old (needed 2 days)
• gcc-10-cross-ports (- to 24)
  • Migration status for gcc-10-cross-ports (- to 24): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-10-cross-ports gcc-10 (not considered)
    • Built-Using: gcc-10-cross-ports gcc-10 (not considered)
    • Depends: gcc-10-cross-ports gcc-10 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-ports.html
    • 181 days old (needed 5 days)
• python-wordcloud (- to 1.9.2+dfsg-1)
  • Migration status for python-wordcloud (- to 1.9.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-wordcloud would introduce bugs in testing: #1055721
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-wordcloud.html
    • autopkgtest for python-wordcloud/1.9.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 181 days old (needed 2 days)
• redmine (- to 5.0.4-7)
  • Migration status for redmine (- to 5.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redmine would introduce bugs in testing: #1040927, #1052877, #1055474
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine.html
    • autopkgtest for redmine/5.0.4-7: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): redmine ruby-html-pipeline
    • Build-Depends(-Arch): redmine ruby-sanitize
    • Build-Depends(-Arch): redmine ruby-task-list
    • Depends: redmine ruby-html-pipeline
    • Depends: redmine ruby-sanitize
    • Depends: redmine ruby-task-list
  • Additional info:
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 181 days old (needed 5 days)
• gcc-10-cross (- to 23)
  • Migration status for gcc-10-cross (- to 23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-10-cross gcc-10 (not considered)
    • Built-Using: gcc-10-cross gcc-10 (not considered)
    • Depends: gcc-10-cross gcc-10 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross.html
    • 182 days old (needed 5 days)
• kanboard (- to 1.2.31+ds2-1)
  • Migration status for kanboard (- to 1.2.31+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kanboard would introduce bugs in testing: #1052638
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kanboard.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for kanboard/1.2.31+ds2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 182 days old (needed 2 days)
• magnum-cluster-api (- to 0.6.0-1)
  • Migration status for magnum-cluster-api (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magnum-cluster-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• odr-padenc (- to 3.0.0-2)
  • Migration status for odr-padenc (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odr-padenc would introduce bugs in testing: #1033127
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odr-padenc.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• ruby-kdl (- to 1.0.3-1)
  • Migration status for ruby-kdl (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-kdl.html
    • autopkgtest for ruby-kdl/1.0.3-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 184 days old (needed 5 days)
• openjdk-19 (- to 19.0.2+7-4)
  • Migration status for openjdk-19 (- to 19.0.2+7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-19 would introduce bugs in testing: #1016376, #1042582
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-19.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: armel: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-19/19.0.2+7-4: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • 185 days old (needed 5 days)
• binutils-msp430 (- to 2.40.50~ti1)
  • Migration status for binutils-msp430 (- to 2.40.50~ti1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-msp430 would introduce bugs in testing: #1042343
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-msp430.html
    • 188 days old (needed 5 days)
• bup (- to 0.33.2-1)
  • Migration status for bup (- to 0.33.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bup would introduce bugs in testing: #1042250
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 188 days old (needed 5 days)
• printrun (- to 2.0.1-1)
  • Migration status for printrun (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating printrun would introduce bugs in testing: #1050157
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printrun.html
    • autopkgtest for printrun/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 188 days old (needed 2 days)
• golang-github-traefik-yaegi (- to 0.15.1-2)
  • Migration status for golang-github-traefik-yaegi (- to 0.15.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-traefik-yaegi would introduce bugs in testing: #1052085
    • autopkgtest for golang-github-traefik-yaegi/0.15.1-2: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-yaegi.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 189 days old (needed 5 days)
• markdown-toc-el (- to 0.1.5-3)
  • Migration status for markdown-toc-el (- to 0.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating markdown-toc-el would introduce bugs in testing: #1036359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-toc-el.html
    • autopkgtest for markdown-toc-el/0.1.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 189 days old (needed 2 days)
• timew (- to 1.5.0+ds.1-1)
  • Migration status for timew (- to 1.5.0+ds.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating timew would introduce bugs in testing: #1053924
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/timew.html
    • autopkgtest for timew/1.5.0+ds.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 189 days old (needed 2 days)
• node-data-uri-to-buffer (- to 4.0.0-4)
  • Migration status for node-data-uri-to-buffer (- to 4.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • node-data-uri-to-buffer has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 192 days old (needed 5 days)
• pymatgen (- to 2023.06.23+dfsg1-2)
  • Migration status for pymatgen (- to 2023.06.23+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pymatgen would introduce bugs in testing: #1056841, #1058040
    • Build-Depends(-Arch): pymatgen python-ase
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymatgen.html
    • autopkgtest for pymatgen/2023.06.23+dfsg1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 192 days old (needed 2 days)
• ruby-rack-session (- to 2.0.0-1)
  • Migration status for ruby-rack-session (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rack-session would introduce bugs in testing: #1027350
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rack-session.html
    • ruby-rack-session unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (>= 3.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 193 days old (needed 5 days)
• ruby-rackup (- to 2.1.0-1)
  • Migration status for ruby-rackup (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rackup would introduce bugs in testing: #1027339
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rackup.html
    • ruby-rackup unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (>= 3.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 193 days old (needed 5 days)
• brial (- to 1.2.12-1)
  • Migration status for brial (- to 1.2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for brial/1.2.12-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Depends: brial sagemath
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/brial.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 195 days old (needed 5 days)
• sogo (- to 5.8.4-1)
  • Migration status for sogo (- to 5.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sogo would introduce bugs in testing: #1042529, #1054486
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sogo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 195 days old (needed 5 days)
• foxtrotgps (- to 1.2.2+bzr332-1)
  • Migration status for foxtrotgps (- to 1.2.2+bzr332-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): foxtrotgps libglade2 (not considered)
    • Depends: foxtrotgps libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxtrotgps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• phylonium (- to 1.7-1)
  • Migration status for phylonium (- to 1.7-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for phylonium/1.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phylonium.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 197 days old (needed 5 days)
• golang-github-form3tech-oss-jwt-go (- to 3.2.3-2)
  • Migration status for golang-github-form3tech-oss-jwt-go (- to 3.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-form3tech-oss-jwt-go would introduce bugs in testing: #1038793, #1042736
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-form3tech-oss-jwt-go.html
    • autopkgtest for golang-github-form3tech-oss-jwt-go/3.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 200 days old (needed 2 days)
• xserver-xorg-video-qxl (- to 0.1.6-1)
  • Migration status for xserver-xorg-video-qxl (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-qxl would introduce bugs in testing: #1042862
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-qxl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 200 days old (needed 5 days)
• python-django-ical (- to 1.9.2-1)
  • Migration status for python-django-ical (- to 1.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-ical would introduce bugs in testing: #1052796
    • autopkgtest for python-django-ical/1.9.2-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ical.html
    • Reproducible on i386 - info ♻
    • 201 days old (needed 5 days)
• ruby-faraday-multipart (- to 1.0.4-1)
  • Migration status for ruby-faraday-multipart (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-faraday-multipart.html
    • autopkgtest for ruby-faraday-multipart/1.0.4-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 201 days old (needed 5 days)
• golang-github-gonvenience-ytbx (- to 1.4.4-1)
  • Migration status for golang-github-gonvenience-ytbx (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by czchen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gonvenience-ytbx.html
    • autopkgtest for golang-github-gonvenience-ytbx/1.4.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 202 days old (needed 2 days)
• octave-database (- to 2.4.4-8)
  • Migration status for octave-database (- to 2.4.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-database would introduce bugs in testing: #1004158
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-database.html
    • autopkgtest for octave-database/2.4.4-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 202 days old (needed 2 days)
• octave-tisean (- to 0.2.3.hg.2021.11.29-1)
  • Migration status for octave-tisean (- to 0.2.3.hg.2021.11.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-tisean/amd64 has unsatisfiable dependency
    • octave-tisean/mips64el has unsatisfiable dependency
    • Updating octave-tisean would introduce bugs in testing: #874116
    • missing build on armel
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/octave-tisean.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • 202 days old (needed 5 days)
• python-pyvmomi (- to 6.7.1-6)
  • Migration status for python-pyvmomi (- to 6.7.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyvmomi would introduce bugs in testing: #1052793
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyvmomi.html
    • 204 days old (needed 5 days)
• liboqs (- to 0.8.0-1)
  • Migration status for liboqs (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liboqs would introduce bugs in testing: #1000303
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboqs.html
    • 205 days old (needed 5 days)
• python-dicompylercore (- to 0.5.6-1)
  • Migration status for python-dicompylercore (- to 0.5.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-dicompylercore pydicom (not considered)
    • Depends: python-dicompylercore pydicom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dicompylercore.html
    • autopkgtest for python-dicompylercore/0.5.6-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 205 days old (needed 5 days)
• rust-transmission-client (- to 0.1.3-3)
  • Migration status for rust-transmission-client (- to 0.1.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-transmission-client rust-isahc (not considered)
    • Depends: rust-transmission-client rust-isahc (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-transmission-client.html
    • autopkgtest for rust-transmission-client/0.1.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 205 days old (needed 2 days)
• webcamoid (- to 9.1.1-1)
  • Migration status for webcamoid (- to 9.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webcamoid would introduce bugs in testing: #1053808
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webcamoid.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 205 days old (needed 5 days)
• wifite (- to 2.7.0-1)
  • Migration status for wifite (- to 2.7.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wifite aircrack-ng (not considered)
    • Depends: wifite aircrack-ng (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wifite.html
    • autopkgtest for wifite/2.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 205 days old (needed 2 days)
• pcb (- to 1:4.3.0-3)
  • Migration status for pcb (- to 1:4.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pcb gtkglext (not considered)
    • Depends: pcb gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 206 days old (needed 5 days)
• rust-hdrhistogram (- to 7.5.2-1)
  • Migration status for rust-hdrhistogram (- to 7.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-hdrhistogram would introduce bugs in testing: #1014034
    • autopkgtest for rust-hdrhistogram/7.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hdrhistogram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 206 days old (needed 5 days)
• ruby-jekyll-remote-theme (- to 0.4.3-4)
  • Migration status for ruby-jekyll-remote-theme (- to 0.4.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-remote-theme would introduce bugs in testing: #1031548, #1032541
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-github-metadata
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-remote-theme.html
    • autopkgtest for ruby-jekyll-remote-theme/0.4.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 207 days old (needed 2 days)
• rust-minijinja (- to 0.34.0-1)
  • Migration status for rust-minijinja (- to 0.34.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-minijinja-dev/amd64 has unsatisfiable dependency
    • librust-minijinja-dev/arm64 has unsatisfiable dependency
    • librust-minijinja-dev/armel has unsatisfiable dependency
    • librust-minijinja-dev/armhf has unsatisfiable dependency
    • librust-minijinja-dev/i386 has unsatisfiable dependency
    • librust-minijinja-dev/mips64el has unsatisfiable dependency
    • librust-minijinja-dev/ppc64el has unsatisfiable dependency
    • librust-minijinja-dev/s390x has unsatisfiable dependency
    • Updating rust-minijinja would introduce bugs in testing: #1051615
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-minijinja.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 207 days old (needed 5 days)
• prometheus-frr-exporter (- to 1.2.0-1)
  • Migration status for prometheus-frr-exporter (- to 1.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prometheus-frr-exporter frr (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-frr-exporter.html
    • autopkgtest for prometheus-frr-exporter/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 208 days old (needed 2 days)
• ruby-ruby-magic-static (- to 0.6.0-2)
  • Migration status for ruby-ruby-magic-static (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-ruby-magic-static would introduce bugs in testing: #1052749
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby-magic-static.html
    • autopkgtest for ruby-ruby-magic-static/0.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 208 days old (needed 2 days)
• vulkan-validationlayers (- to 1.3.250.0-1)
  • Migration status for vulkan-validationlayers (- to 1.3.250.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vulkan-validationlayers would introduce bugs in testing: #1054709
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vulkan-validationlayers.html
    • 208 days old (needed 5 days)
• python-cdo (- to 1.6.0-2)
  • Migration status for python-cdo (- to 1.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-cdo python-xarray (not considered)
    • Depends: python-cdo python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cdo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 209 days old (needed 5 days)
• triton (- to 2.0.0.post1-3)
  • Migration status for triton (- to 2.0.0.post1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating triton would introduce bugs in testing: #1052930
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/triton.html
    • autopkgtest for triton/2.0.0.post1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 209 days old (needed 2 days)
• php-lcobucci-clock (- to 3.1.0-2)
  • Migration status for php-lcobucci-clock (- to 3.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-lcobucci-clock/3.1.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • php-lcobucci-clock unsatisfiable Build-Depends(-Arch) on amd64: phpunit (>= 10)
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-lcobucci-clock.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 215 days old (needed 5 days)
• php-algo26-idna-convert (- to 3.1.0-1)
  • Migration status for php-algo26-idna-convert (- to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-algo26-idna-convert/3.1.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-algo26-idna-convert php-jakeasmith-http-build-url
    • Depends: php-algo26-idna-convert php-jakeasmith-http-build-url
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-algo26-idna-convert.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 225 days old (needed 5 days)
• php-jakeasmith-http-build-url (- to 1.0.1-1)
  • Migration status for php-jakeasmith-http-build-url (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-jakeasmith-http-build-url.html
    • autopkgtest for php-jakeasmith-http-build-url/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 226 days old (needed 2 days)
• php-league-uri (- to 6.8.0-1)
  • Migration status for php-league-uri (- to 6.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): php-league-uri php-league-uri-interfaces
    • Depends: php-league-uri php-league-uri-interfaces
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-league-uri.html
    • autopkgtest for php-league-uri/6.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• php-league-uri-interfaces (- to 2.3.0-1)
  • Migration status for php-league-uri-interfaces (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-league-uri-interfaces.html
    • autopkgtest for php-league-uri-interfaces/2.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• pyramid-jinja2 (- to 2.7+dfsg-1.3)
  • Migration status for pyramid-jinja2 (- to 2.7+dfsg-1.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyramid-jinja2 python-pyramid (not considered)
    • Depends: pyramid-jinja2 python-pyramid (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyramid-jinja2.html
    • autopkgtest for pyramid-jinja2/2.7+dfsg-1.3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 229 days old (needed 5 days)
• lomiri-session (- to 0.2-4)
  • Migration status for lomiri-session (- to 0.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-session lomiri (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 230 days old (needed 5 days)
• x2gothinclient (- to 1.5.0.1-10)
  • Migration status for x2gothinclient (- to 1.5.0.1-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2gothinclient x2goclient (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2gothinclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 233 days old (needed 5 days)
• ogmrip (- to 1.0.1-4)
  • Migration status for ogmrip (- to 1.0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ogmrip gpac (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogmrip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 237 days old (needed 5 days)
• puppetserver (- to 7.9.5-2)
  • Migration status for puppetserver (- to 7.9.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • puppetserver/amd64 has unsatisfiable dependency
    • puppetserver/arm64 has unsatisfiable dependency
    • Updating puppetserver would introduce bugs in testing: #1042314
    • Build-Depends(-Arch): puppetserver jruby-utils-clojure
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/puppetserver.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on i386 - info ♻
    • 240 days old (needed 5 days)
• ruby-ruby-openai (- to 3.7.0-2)
  • Migration status for ruby-ruby-openai (- to 3.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby-openai.html
    • autopkgtest for ruby-ruby-openai/3.7.0-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 240 days old (needed 5 days)
• libretro-bsnes-mercury (- to 094+git20220807-8)
  • Migration status for libretro-bsnes-mercury (- to 094+git20220807-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: libretro-bsnes-mercury kodi-game-libretro (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-bsnes-mercury.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 241 days old (needed 5 days)
• sniproxy (- to 0.6.0-2.1)
  • Migration status for sniproxy (- to 0.6.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sniproxy would introduce bugs in testing: #999957
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sniproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 244 days old (needed 5 days)
• libanyevent-riperedis-perl (- to 0.48-1)
  • Migration status for libanyevent-riperedis-perl (- to 0.48-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by az, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libanyevent-riperedis-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• matomo-component-ini (- to 3.0.1-1)
  • Migration status for matomo-component-ini (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-component-ini.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• matomo-component-network (- to 2.0.1-1)
  • Migration status for matomo-component-network (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-component-network.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• matomo-device-detector (- to 6.1.1-1)
  • Migration status for matomo-device-detector (- to 6.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
    • Depends: matomo-device-detector php-spyc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-device-detector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• matomo-php-tracker (- to 3.1.3-1)
  • Migration status for matomo-php-tracker (- to 3.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-php-tracker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• matomo-referrer-spam-list (- to 4.0.0-1)
  • Migration status for matomo-referrer-spam-list (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-referrer-spam-list.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• matomo-searchengine-and-social-list (- to 3.13.0-1)
  • Migration status for matomo-searchengine-and-social-list (- to 3.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-searchengine-and-social-list.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• regina-normal (- to 7.3-2)
  • Migration status for regina-normal (- to 7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating regina-normal would introduce bugs in testing: #1037840
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/regina-normal.html
    • autopkgtest for regina-normal/7.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 247 days old (needed 2 days)
• less.php (- to 4.1.0-1)
  • Migration status for less.php (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/less.php.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 253 days old (needed 5 days)
• php-maxmind-web-service-common (- to 0.9.0-1)
  • Migration status for php-maxmind-web-service-common (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-maxmind-web-service-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 259 days old (needed 5 days)
• php-jshrink (- to 1.6.5-1)
  • Migration status for php-jshrink (- to 1.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-jshrink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 266 days old (needed 5 days)
• shadowsocks-libev (- to 3.3.5+ds-10)
  • Migration status for shadowsocks-libev (- to 3.3.5+ds-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shadowsocks-libev would introduce bugs in testing: #999965
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shadowsocks-libev.html
    • autopkgtest for shadowsocks-libev/3.3.5+ds-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 267 days old (needed 2 days)
• php-sparkline (- to 2.2.0-1)
  • Migration status for php-sparkline (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sparkline would introduce bugs in testing: #1034403
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sparkline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 270 days old (needed 5 days)
• php-spyc (- to 0.6.3-1)
  • Migration status for php-spyc (- to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-spyc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 270 days old (needed 5 days)
• puppet-module-voxpupuli-kmod (- to 3.2.0-1)
  • Migration status for puppet-module-voxpupuli-kmod (- to 3.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-voxpupuli-kmod.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 272 days old (needed 5 days)
• libjpeg9 (- to 1:9e-1)
  • Migration status for libjpeg9 (- to 1:9e-1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 286 days old (needed 5 days)
• opentk (- to 1.1.4c+dfsg-2.2)
  • Migration status for opentk (- to 1.1.4c+dfsg-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: opentk cecil (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentk.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 289 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 14.10.1-1)
  • Migration status for gitlab-ci-multi-runner (- to 14.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1033480
    • gitlab-runner/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/s390x has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • 290 days old (needed 5 days)
• transmission (- to 4.0.2-1)
  • Migration status for transmission (- to 4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating transmission would introduce bugs in testing: #1041519, #1042027
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transmission.html
    • 295 days old (needed 5 days)
• cryptacular (- to 1.2.5-1)
  • Migration status for cryptacular (- to 1.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptacular.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 296 days old (needed 5 days)
• ldaptive (- to 2.1.1+ds-1)
  • Migration status for ldaptive (- to 2.1.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldaptive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 296 days old (needed 5 days)
• gcc-xtensa-lx106 (- to 13)
  • Migration status for gcc-xtensa-lx106 (- to 13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gcc-xtensa-lx106 has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 301 days old (needed 5 days)
• searx-admin (- to 0.0~git20170823.95fe63b+ds-3)
  • Migration status for searx-admin (- to 0.0~git20170823.95fe63b+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: searx-admin searx (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx-admin.html
    • autopkgtest for searx-admin/0.0~git20170823.95fe63b+ds-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 302 days old (needed 5 days)
• igdiscover (- to 0.11-4)
  • Migration status for igdiscover (- to 0.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating igdiscover would introduce bugs in testing: #1032975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/igdiscover.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for igdiscover/0.11-4: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 303 days old (needed 5 days)
• ganeti (- to 3.0.2-3)
  • Migration status for ganeti (- to 3.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganeti would introduce bugs in testing: #1042264
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
    • autopkgtest for ganeti/3.0.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Ignored failure, i386: Pass, ppc64el: Pass, s390x: Ignored failure
    • 306 days old (needed 5 days)
• emacs-helm-ag (- to 0.59-2)
  • Migration status for emacs-helm-ag (- to 0.59-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-helm-ag would introduce bugs in testing: #1057557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-helm-ag.html
    • autopkgtest for emacs-helm-ag/0.59-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 311 days old (needed 2 days)
• debian-timeline (- to 46)
  • Migration status for debian-timeline (- to 46): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-timeline would introduce bugs in testing: #1032166
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-timeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 312 days old (needed 5 days)
• hobbit-plugins (- to 20230301)
  • Migration status for hobbit-plugins (- to 20230301): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: hobbit-plugins xymon (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hobbit-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 312 days old (needed 5 days)
• lomiri-camera-app (- to 4.0.2+dfsg-1)
  • Migration status for lomiri-camera-app (- to 4.0.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-camera-app libusermetrics (not considered)
    • Depends: lomiri-camera-app libusermetrics (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-camera-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 312 days old (needed 5 days)
• qpid-proton-j-extensions (- to 1.2.4-1)
  • Migration status for qpid-proton-j-extensions (- to 1.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: qpid-proton-j-extensions qpid-proton-j
    • Depends: qpid-proton-j-extensions qpid-proton-j
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton-j-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 312 days old (needed 5 days)
• lomiri-clock-app (- to 4.0.2-1)
  • Migration status for lomiri-clock-app (- to 4.0.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-clock-app libusermetrics (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-clock-app.html
    • autopkgtest for lomiri-clock-app/4.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 313 days old (needed 2 days)
• lomiri-music-app (- to 3.0.2-1)
  • Migration status for lomiri-music-app (- to 3.0.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-music-app libusermetrics (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-music-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 313 days old (needed 5 days)
• python-klein (- to 21.8.0-2)
  • Migration status for python-klein (- to 21.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-klein would introduce bugs in testing: #1052869
    • autopkgtest for python-klein/21.8.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-klein.html
    • Reproducible on i386 - info ♻
    • 313 days old (needed 5 days)
• vart (- to 2.5-4)
  • Migration status for vart (- to 2.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vart would introduce bugs in testing: #1037882
    • Build-Depends(-Arch): vart xir
    • Build-Depends(-Arch): vart xrt
    • Depends: vart xir
    • Depends: vart xrt
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vart.html
    • 313 days old (needed 5 days)
• xrt (- to 202210.2.13.466+dfsg-8)
  • Migration status for xrt (- to 202210.2.13.466+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xrt would introduce bugs in testing: #1037903
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrt.html
    • 313 days old (needed 5 days)
• resfinder (- to 4.3.0-1)
  • Migration status for resfinder (- to 4.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): resfinder pdm (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resfinder.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for resfinder/4.3.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 314 days old (needed 2 days)
• renpy (- to 8.0.3+dfsg-1)
  • Migration status for renpy (- to 8.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating renpy would introduce bugs in testing: #1038426, #1055736, #1056883
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/renpy.html
    • 315 days old (needed 5 days)
• qpid-proton-j (- to 0.34.0-1)
  • Migration status for qpid-proton-j (- to 0.34.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton-j.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 316 days old (needed 5 days)
• gdb-doc (- to 13.1-1)
  • Migration status for gdb-doc (- to 13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdb-doc would introduce bugs in testing: #1057563
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 317 days old (needed 5 days)
• vertx-docgen (- to 0.9.4-2)
  • Migration status for vertx-docgen (- to 0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vertx-docgen openjdk-11 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vertx-docgen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 317 days old (needed 5 days)
• zoneminder (- to 1.36.33+dfsg1-1)
  • Migration status for zoneminder (- to 1.36.33+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zoneminder would introduce bugs in testing: #999919
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zoneminder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 317 days old (needed 5 days)
• fava (- to 1.23.1+dfsg-1)
  • Migration status for fava (- to 1.23.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fava would introduce bugs in testing: #1031724
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fava.html
    • Reproducible on i386 - info ♻
    • 319 days old (needed 5 days)
• golang-github-crewjam-saml (- to 0.4.12-2)
  • Migration status for golang-github-crewjam-saml (- to 0.4.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-crewjam-saml would introduce bugs in testing: #1033753, #1033864, #1054223
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-crewjam-saml.html
    • autopkgtest for golang-github-crewjam-saml/0.4.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 319 days old (needed 2 days)
• python-lua (- to 0.6-1)
  • Migration status for python-lua (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lua/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lua.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 320 days old (needed 5 days)
• quickjs (- to 2021.03.27-1)
  • Migration status for quickjs (- to 2021.03.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickjs would introduce bugs in testing: #1031074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 320 days old (needed 5 days)
• ukui-settings-daemon (- to 3.1.1.1-3)
  • Migration status for ukui-settings-daemon (- to 3.1.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ukui-settings-daemon would introduce bugs in testing: #1051424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-settings-daemon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 320 days old (needed 5 days)
• oregano (- to 0.84.41+dfsg.1-1.1)
  • Migration status for oregano (- to 0.84.41+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oregano would introduce bugs in testing: #1051281
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oregano.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 322 days old (needed 5 days)
• simplescreenrecorder (- to 0.4.4-3)
  • Migration status for simplescreenrecorder (- to 0.4.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplescreenrecorder would introduce bugs in testing: #1040375
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplescreenrecorder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 323 days old (needed 5 days)
• afnix (- to 3.8.0-1)
  • Migration status for afnix (- to 3.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating afnix would introduce bugs in testing: #1031749, #1037570
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/afnix.html
    • 325 days old (needed 5 days)
• facet-analyser (- to 0.0~git20221121142040.6be10b8+ds1-3)
  • Migration status for facet-analyser (- to 0.0~git20221121142040.6be10b8+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • facet-analyser/amd64 has unsatisfiable dependency
    • Updating facet-analyser would introduce bugs in testing: #1040334
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/facet-analyser.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 326 days old (needed 5 days)
• lomiri-telephony-service (- to 0.5.1-1)
  • Migration status for lomiri-telephony-service (- to 0.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-telephony-service libusermetrics (not considered)
    • Depends: lomiri-telephony-service libusermetrics (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-telephony-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 327 days old (needed 5 days)
• python-pycdlib (- to 1.12.0+ds1-4)
  • Migration status for python-pycdlib (- to 1.12.0+ds1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pycdlib would introduce bugs in testing: #1002789
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pycdlib.html
    • 327 days old (needed 5 days)
• ognibuild (- to 0.0.18+git20230208.1.9b890a2-1)
  • Migration status for ognibuild (- to 0.0.18+git20230208.1.9b890a2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ognibuild/0.0.18+git20230208.1.9b890a2-1: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ognibuild.html
    • 329 days old (needed 5 days)
• jruby-utils-clojure (- to 4.0.3-4)
  • Migration status for jruby-utils-clojure (- to 4.0.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jruby-utils-clojure would introduce bugs in testing: #1042031
    • Build-Depends(-Arch): jruby-utils-clojure jruby
    • Depends: jruby-utils-clojure jruby
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-utils-clojure.html
    • autopkgtest for jruby-utils-clojure/4.0.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 330 days old (needed 2 days)
• rust-ripasso-cursive (- to 0.6.1-2)
  • Migration status for rust-ripasso-cursive (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ripasso-cursive would introduce bugs in testing: #1056253
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/amd64
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/arm64
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/armel
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/armhf
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/i386
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/mips64el
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/ppc64el
    • Impossible Depends: rust-ripasso-cursive -> libgit2-1.5/1.5.1+ds-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ripasso-cursive.html
    • 330 days old (needed 5 days)
• codelite (- to 17.0.0+dfsg-1)
  • Migration status for codelite (- to 17.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating codelite would introduce bugs in testing: #1057392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codelite.html
    • 331 days old (needed 5 days)
• dogtag-pki (- to 11.2.1-2)
  • Migration status for dogtag-pki (- to 11.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pki-server/amd64 has unsatisfiable dependency
    • pki-server/arm64 has unsatisfiable dependency
    • pki-server/armel has unsatisfiable dependency
    • pki-server/armhf has unsatisfiable dependency
    • pki-server/i386 has unsatisfiable dependency
    • pki-server/mips64el has unsatisfiable dependency
    • pki-server/ppc64el has unsatisfiable dependency
    • pki-server/s390x has unsatisfiable dependency
    • Updating dogtag-pki would introduce bugs in testing: #1054480
    • Build-Depends(-Arch): dogtag-pki tomcatjss
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogtag-pki.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 331 days old (needed 5 days)
• php-horde-wicked (- to 2.0.8-9)
  • Migration status for php-horde-wicked (- to 2.0.8-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-wicked php-horde-rpc (not considered)
    • Invalidated by dependency
    • Depends: php-horde-wicked php-horde
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
    • autopkgtest for php-horde-wicked/2.0.8-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 331 days old (needed 2 days)
• dials (- to 3.12.1+dfsg3-5)
  • Migration status for dials (- to 3.12.1+dfsg3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dials would introduce bugs in testing: #1056241, #1059175
    • Build-Depends(-Arch): dials pyfai
    • Depends: dials pyfai
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dials.html
    • autopkgtest for dials/3.12.1+dfsg3-5: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 332 days old (needed 2 days)
• ruby-jekyll-github-metadata (- to 2.15.0-1)
  • Migration status for ruby-jekyll-github-metadata (- to 2.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-github-metadata would introduce bugs in testing: #1037529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-github-metadata.html
    • autopkgtest for ruby-jekyll-github-metadata/2.15.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 332 days old (needed 2 days)
• bambootracker (- to 0.6.1-1)
  • Migration status for bambootracker (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bambootracker would introduce bugs in testing: #1051573
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bambootracker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 333 days old (needed 5 days)
• haskell-raaz (- to 0.2.1-2.1)
  • Migration status for haskell-raaz (- to 0.2.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-raaz-dev/amd64 has unsatisfiable dependency
    • libghc-raaz-doc/amd64 has unsatisfiable dependency
    • libghc-raaz-prof/amd64 has unsatisfiable dependency
    • libghc-raaz-dev/arm64 has unsatisfiable dependency
    • libghc-raaz-doc/arm64 has unsatisfiable dependency
    • libghc-raaz-prof/arm64 has unsatisfiable dependency
    • libghc-raaz-dev/armel has unsatisfiable dependency
    • libghc-raaz-prof/armel has unsatisfiable dependency
    • libghc-raaz-dev/armhf has unsatisfiable dependency
    • libghc-raaz-prof/armhf has unsatisfiable dependency
    • libghc-raaz-dev/i386 has unsatisfiable dependency
    • libghc-raaz-prof/i386 has unsatisfiable dependency
    • libghc-raaz-dev/mips64el has unsatisfiable dependency
    • libghc-raaz-prof/mips64el has unsatisfiable dependency
    • libghc-raaz-dev/ppc64el has unsatisfiable dependency
    • libghc-raaz-prof/ppc64el has unsatisfiable dependency
    • libghc-raaz-dev/s390x has unsatisfiable dependency
    • libghc-raaz-prof/s390x has unsatisfiable dependency
    • Updating haskell-raaz would introduce bugs in testing: #1053980, #1054978
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-raaz.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 333 days old (needed 5 days)
• sagemath (- to 9.5-6)
  • Migration status for sagemath (- to 9.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagemath would introduce bugs in testing: #1042683, #1042935, #1050182, #1056885
    • Build-Depends(-Arch): sagemath brial
    • Build-Depends(-Arch): sagemath cypari2
    • Build-Depends(-Arch): sagemath fpylll
    • Depends: sagemath brial
    • Depends: sagemath cypari2
    • Depends: sagemath fpylll
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sagemath.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for sagemath/9.5-6: amd64: Pass, arm64: Pass, i386: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 333 days old (needed 2 days)
• segyio (- to 1.8.3-1.2)
  • Migration status for segyio (- to 1.8.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating segyio would introduce bugs in testing: #1055728
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/segyio.html
    • autopkgtest for segyio/1.8.3-1.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 333 days old (needed 2 days)
• hyperspy (- to 1.7.3-1)
  • Migration status for hyperspy (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperspy would introduce bugs in testing: #1040332, #1041803
    • hyperspy unsatisfiable Build-Depends(-Arch) on amd64: python3-ptable
    • hyperspy unsatisfiable Build-Depends(-Arch) on ppc64el: python3-ptable
    • Build-Depends(-Arch): hyperspy python-sparse
    • Depends: hyperspy python-sparse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperspy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 334 days old (needed 5 days)
• openems (- to 0.0.35+git20190103.6a75e98+dfsg.1-3.2)
  • Migration status for openems (- to 0.0.35+git20190103.6a75e98+dfsg.1-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openems would introduce bugs in testing: #1054794, #1056826
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openems.html
    • autopkgtest for openems/0.0.35+git20190103.6a75e98+dfsg.1-3.2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 334 days old (needed 5 days)
• ruby-gitlab-markup (- to 1.9.0-1)
  • Migration status for ruby-gitlab-markup (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-markup would introduce bugs in testing: #1053838
    • Build-Depends(-Arch): ruby-gitlab-markup ruby-html-pipeline
    • Build-Depends(-Arch): ruby-gitlab-markup ruby-sanitize
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-markup.html
    • autopkgtest for ruby-gitlab-markup/1.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 334 days old (needed 2 days)
• ruby-gruff (- to 0.6.0-2)
  • Migration status for ruby-gruff (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gruff would introduce bugs in testing: #1054733
    • autopkgtest for ruby-gruff/0.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ , s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gruff.html
    • Reproducible on i386 - info ♻
    • 334 days old (needed 5 days)
• python-aioxmpp (- to 0.13.3-1)
  • Migration status for python-aioxmpp (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioxmpp would introduce bugs in testing: #1042239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioxmpp.html
    • Reproducible on i386 - info ♻
    • 335 days old (needed 5 days)
• ayatana-indicator-display (- to 22.9.4-1)
  • Migration status for ayatana-indicator-display (- to 22.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ayatana-indicator-display would introduce bugs in testing: #1052946
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-display.html
    • Reproducible on i386 - info ♻
    • 336 days old (needed 5 days)
• gfpoken (- to 1-4)
  • Migration status for gfpoken (- to 1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gfpoken blender (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfpoken.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 336 days old (needed 5 days)
• ubertooth (- to 2018.12.R1-5.1)
  • Migration status for ubertooth (- to 2018.12.R1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ubertooth would introduce bugs in testing: #1054741
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ubertooth.html
    • autopkgtest for ubertooth/2018.12.R1-5.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 336 days old (needed 2 days)
• freesas (- to 0.9.0-6)
  • Migration status for freesas (- to 0.9.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): freesas pyfai (not considered)
    • Depends: freesas pyfai (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freesas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 337 days old (needed 5 days)
• mlpy (- to 3.5.0+ds-2)
  • Migration status for mlpy (- to 3.5.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlpy would introduce bugs in testing: #1054748, #1055693, #1056819
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlpy.html
    • autopkgtest for mlpy/3.5.0+ds-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 337 days old (needed 5 days)
• openfpgaloader (- to 0.10.0+git20230202-edea24f-1)
  • Migration status for openfpgaloader (- to 0.10.0+git20230202-edea24f-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openfpgaloader would introduce bugs in testing: #1037802
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openfpgaloader.html
    • Reproducible on i386 - info ♻
    • 337 days old (needed 5 days)
• php-horde-imp (- to 6.2.27-3)
  • Migration status for php-horde-imp (- to 6.2.27-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-imp would introduce bugs in testing: #1038441
    • Depends: php-horde-imp php-horde
    • Depends: php-horde-imp php-horde-editor
    • Depends: php-horde-imp php-horde-mail-autoconfig
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
    • autopkgtest for php-horde-imp/6.2.27-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 337 days old (needed 2 days)
• swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-3)
  • Migration status for swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swift-im would introduce bugs in testing: #1032724, #1056100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-im.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 337 days old (needed 5 days)
• nmodl (- to 0.5-1)
  • Migration status for nmodl (- to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nmodl would introduce bugs in testing: #1054683
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nmodl.html
    • autopkgtest for nmodl/0.5-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 338 days old (needed 5 days)
• polyml (- to 5.7.1-5)
  • Migration status for polyml (- to 5.7.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating polyml would introduce bugs in testing: #1033835
    • autopkgtest for polyml/5.7.1-5: amd64: Regression or new test ♻ , arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 338 days old (needed 5 days)
• propellor (- to 5.13-3)
  • Migration status for propellor (- to 5.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-propellor-dev/amd64 has unsatisfiable dependency
    • libghc-propellor-doc/amd64 has unsatisfiable dependency
    • libghc-propellor-prof/amd64 has unsatisfiable dependency
    • libghc-propellor-dev/arm64 has unsatisfiable dependency
    • libghc-propellor-doc/arm64 has unsatisfiable dependency
    • libghc-propellor-prof/arm64 has unsatisfiable dependency
    • libghc-propellor-dev/armel has unsatisfiable dependency
    • libghc-propellor-prof/armel has unsatisfiable dependency
    • libghc-propellor-dev/armhf has unsatisfiable dependency
    • libghc-propellor-prof/armhf has unsatisfiable dependency
    • libghc-propellor-dev/i386 has unsatisfiable dependency
    • libghc-propellor-prof/i386 has unsatisfiable dependency
    • libghc-propellor-dev/mips64el has unsatisfiable dependency
    • libghc-propellor-prof/mips64el has unsatisfiable dependency
    • libghc-propellor-dev/ppc64el has unsatisfiable dependency
    • libghc-propellor-prof/ppc64el has unsatisfiable dependency
    • libghc-propellor-dev/s390x has unsatisfiable dependency
    • libghc-propellor-prof/s390x has unsatisfiable dependency
    • Updating propellor would introduce bugs in testing: #1053981, #1054640, #1054828
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/propellor.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 338 days old (needed 5 days)
• python-languagecodes (- to 1.1.1-2)
  • Migration status for python-languagecodes (- to 1.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-languagecodes would introduce bugs in testing: #1056477, #1058368
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-languagecodes.html
    • autopkgtest for python-languagecodes/1.1.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 338 days old (needed 2 days)
• sqlfluff (- to 1.4.5-2)
  • Migration status for sqlfluff (- to 1.4.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqlfluff would introduce bugs in testing: #1056532
    • autopkgtest for sqlfluff/1.4.5-2: amd64: Regression or new test ♻ , arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlfluff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 338 days old (needed 5 days)
• gnome-photos (- to 43.0-2)
  • Migration status for gnome-photos (- to 43.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-photos would introduce bugs in testing: #1040202, #1040746
    • autopkgtest for gnome-photos/43.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-photos.html
    • Reproducible on i386 - info ♻
    • 340 days old (needed 5 days)
• pyhst2 (- to 2020c-7)
  • Migration status for pyhst2 (- to 2020c-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyhst2 would introduce bugs in testing: #1036680, #1056840
    • Impossible Depends: pyhst2 -> libcublas11/11.11.3.6~11.8.0-5/amd64
    • Impossible Depends: pyhst2 -> libcudart11.0/11.8.89~11.8.0-5/amd64
    • Impossible Depends: pyhst2 -> libcufft10/11.1.1+~10.9.0.58~11.8.0-5/amd64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 340 days old (needed 5 days)
• ruby-moneta (- to 1.5.2-1)
  • Migration status for ruby-moneta (- to 1.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-moneta would introduce bugs in testing: #1033316
    • autopkgtest for ruby-moneta/1.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-moneta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 341 days old (needed 5 days)
• varnish-vmod-digest (- to 6.4+20220108-1)
  • Migration status for varnish-vmod-digest (- to 6.4+20220108-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): varnish-vmod-digest varnish (not considered)
    • Depends: varnish-vmod-digest varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varnish-vmod-digest.html
    • autopkgtest for varnish-vmod-digest/6.4+20220108-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 341 days old (needed 2 days)
• hyperkitty (- to 1.3.7-1)
  • Migration status for hyperkitty (- to 1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-django-hyperkitty/amd64 has unsatisfiable dependency
    • python3-django-hyperkitty/arm64 has unsatisfiable dependency
    • Updating hyperkitty would introduce bugs in testing: #1052805
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/h/hyperkitty.html
    • hyperkitty unsatisfiable Build-Depends(-Arch) on amd64: python3-django (<< 3:4.2)
    • Build-Depends(-Arch): hyperkitty django-mailman3
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 342 days old (needed 5 days)
• mailman-hyperkitty (- to 1.2.1-1)
  • Migration status for mailman-hyperkitty (- to 1.2.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailman-hyperkitty mailman3 (not considered)
    • Depends: mailman-hyperkitty mailman3 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman-hyperkitty.html
    • autopkgtest for mailman-hyperkitty/1.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 342 days old (needed 2 days)
• postorius (- to 1.3.8-3)
  • Migration status for postorius (- to 1.3.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: postorius django-mailman3 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postorius.html
    • autopkgtest for postorius/1.3.8-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 342 days old (needed 2 days)
• psi4 (- to 1:1.3.2+dfsg-5)
  • Migration status for psi4 (- to 1:1.3.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for psi4/1:1.3.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): psi4 chemps2
    • Depends: psi4 chemps2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psi4.html
    • 342 days old (needed 5 days)
• binutils-m68hc1x (- to 1:3.5.0)
  • Migration status for binutils-m68hc1x (- to 1:3.5.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-m68hc1x would introduce bugs in testing: #1042317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-m68hc1x.html
    • 343 days old (needed 5 days)
• mikutter (- to 5.0.4+dfsg1-2)
  • Migration status for mikutter (- to 5.0.4+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mikutter ruby-moneta (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mikutter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 343 days old (needed 5 days)
• mvdsv (- to 0.35-6)
  • Migration status for mvdsv (- to 0.35-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mvdsv would introduce bugs in testing: #1050187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mvdsv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 343 days old (needed 5 days)
• php-horde (- to 5.2.23+debian0-6)
  • Migration status for php-horde (- to 5.2.23+debian0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde php-horde-rpc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 344 days old (needed 5 days)
• pyswarms (- to 1.3.0-5)
  • Migration status for pyswarms (- to 1.3.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyswarms would introduce bugs in testing: #1056445, #1058390
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyswarms.html
    • autopkgtest for pyswarms/1.3.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 344 days old (needed 2 days)
• ktx (- to 1.42+dfsg-3)
  • Migration status for ktx (- to 1.42+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ktx mvdsv (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 345 days old (needed 5 days)
• ruby-riddle (- to 2.4.2-3)
  • Migration status for ruby-riddle (- to 2.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-riddle would introduce bugs in testing: #1033369
    • autopkgtest for ruby-riddle/2.4.2-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ruby-riddle/blocked-on-ci-infra: armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-riddle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 345 days old (needed 5 days)
• mame-extra (- to 0.250-1)
  • Migration status for mame-extra (- to 0.250-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mame-extra mame (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 346 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-9)
  • Migration status for php-horde-passwd (- to 5.0.7-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-passwd php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
    • autopkgtest for php-horde-passwd/5.0.7-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 346 days old (needed 2 days)
• q2-dada2 (- to 2022.11.2-2)
  • Migration status for q2-dada2 (- to 2022.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/q/q2-dada2.html
    • autopkgtest for q2-dada2/2022.11.2-2: amd64: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 347 days old (needed 5 days)
• sepp (- to 4.5.1+really4.5.1+dfsg-5)
  • Migration status for sepp (- to 4.5.1+really4.5.1+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sepp pplacer (not considered)
    • Depends: sepp pplacer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sepp.html
    • autopkgtest for sepp/4.5.1+really4.5.1+dfsg-5: amd64: Pass, arm64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 347 days old (needed 2 days)
• android-sdk-meta (- to 28.0.2+9)
  • Migration status for android-sdk-meta (- to 28.0.2+9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-sdk-meta android-platform-build (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-sdk-meta.html
    • autopkgtest for android-sdk-meta/28.0.2+9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 348 days old (needed 2 days)
• eviacam (- to 2.1.4-2.1)
  • Migration status for eviacam (- to 2.1.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eviacam would introduce bugs in testing: #1033052
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eviacam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 348 days old (needed 5 days)
• lava (- to 2023.01-2)
  • Migration status for lava (- to 2023.01-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lava would introduce bugs in testing: #1041342
    • autopkgtest for lava/2023.01-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Depends: lava djangorestframework-filters
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 348 days old (needed 5 days)
• python-pgpy (- to 0.6.0-1)
  • Migration status for python-pgpy (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pgpy would introduce bugs in testing: #1042703
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pgpy.html
    • autopkgtest for python-pgpy/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 348 days old (needed 2 days)
• kodi-peripheral-joystick (- to 20.1.3+ds-1)
  • Migration status for kodi-peripheral-joystick (- to 20.1.3+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-peripheral-joystick kodi (not considered)
    • Depends: kodi-peripheral-joystick kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-peripheral-joystick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• kodi-peripheral-xarcade (- to 20.1.3-1)
  • Migration status for kodi-peripheral-xarcade (- to 20.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-peripheral-xarcade kodi (not considered)
    • Depends: kodi-peripheral-xarcade kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-peripheral-xarcade.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• kodi-pvr-teleboy (- to 20.3.3+ds-1)
  • Migration status for kodi-pvr-teleboy (- to 20.3.3+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-teleboy kodi (not considered)
    • Depends: kodi-pvr-teleboy kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-teleboy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• kodi-pvr-vuplus (- to 20.4.1+ds-1)
  • Migration status for kodi-pvr-vuplus (- to 20.4.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-vuplus kodi (not considered)
    • Depends: kodi-pvr-vuplus kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-vuplus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• kodi-pvr-zattoo (- to 20.3.3+ds-1)
  • Migration status for kodi-pvr-zattoo (- to 20.3.3+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-zattoo kodi (not considered)
    • Depends: kodi-pvr-zattoo kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-zattoo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• libembperl-perl (- to 2.5.0-17)
  • Migration status for libembperl-perl (- to 2.5.0-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libembperl-perl would introduce bugs in testing: #1042845
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libembperl-perl.html
    • autopkgtest for libembperl-perl/2.5.0-17: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• sfepy (- to 2021.4-4)
  • Migration status for sfepy (- to 2021.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfepy would introduce bugs in testing: #1056887
    • Build-Depends(-Arch): sfepy python-sparse
    • Depends: sfepy python-sparse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfepy.html
    • autopkgtest for sfepy/2021.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 349 days old (needed 2 days)
• glirc (- to 2.39.0.1-1)
  • Migration status for glirc (- to 2.39.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glirc would introduce bugs in testing: #1054966
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-vty-dev (<< 5.36)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glirc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• ruby-github-markup (- to 1.7.0+dfsg-6)
  • Migration status for ruby-github-markup (- to 1.7.0+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-github-markup would introduce bugs in testing: #1053839
    • Build-Depends(-Arch): ruby-github-markup ruby-html-pipeline
    • Build-Depends(-Arch): ruby-github-markup ruby-sanitize
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-github-markup.html
    • autopkgtest for ruby-github-markup/1.7.0+dfsg-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 350 days old (needed 2 days)
• darcs (- to 2.16.5-1)
  • Migration status for darcs (- to 2.16.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs would introduce bugs in testing: #1054953
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darcs.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 351 days old (needed 5 days)
• gtk-sharp3 (- to 2.99.3-4.1)
  • Migration status for gtk-sharp3 (- to 2.99.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtk-sharp3 would introduce bugs in testing: #1017897
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-sharp3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 351 days old (needed 5 days)
• scrcpy (- to 1.25-1)
  • Migration status for scrcpy (- to 1.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scrcpy would introduce bugs in testing: #1050097
    • autopkgtest for scrcpy/1.25-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends-Indep: scrcpy android-framework-23
    • Build-Depends-Indep: scrcpy android-sdk-meta
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrcpy.html
    • 351 days old (needed 5 days)
• clazy (- to 1.11-4)
  • Migration status for clazy (- to 1.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clazy would introduce bugs in testing: #1051858
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clazy.html
    • autopkgtest for clazy/1.11-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 353 days old (needed 2 days)
• relion-cuda (- to 3.1.3-2)
  • Migration status for relion-cuda (- to 3.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating relion-cuda would introduce bugs in testing: #1036681, #1040128
    • Impossible Depends: relion-cuda -> libcufft10/11.1.1+~10.9.0.58~11.8.0-5/amd64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for relion-cuda/3.1.3-2: amd64: No tests, superficial or marked flaky ♻
    • 353 days old (needed 5 days)
• jruby (- to 9.3.9.0+ds-8)
  • Migration status for jruby (- to 9.3.9.0+ds-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jruby would introduce bugs in testing: #1042129
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby.html
    • autopkgtest for jruby/9.3.9.0+ds-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 355 days old (needed 2 days)
• python-ase (- to 3.22.1-3)
  • Migration status for python-ase (- to 3.22.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ase would introduce bugs in testing: #1056184, #1056457
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ase.html
    • autopkgtest for python-ase/3.22.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 355 days old (needed 2 days)
• vim-ultisnips (- to 3.2-2)
  • Migration status for vim-ultisnips (- to 3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-ultisnips would introduce bugs in testing: #1033510
    • autopkgtest for vim-ultisnips/3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ , s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-ultisnips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 355 days old (needed 5 days)
• fpylll (- to 0.5.9-1)
  • Migration status for fpylll (- to 0.5.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fpylll would introduce bugs in testing: #1055732, #1056800
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fpylll.html
    • autopkgtest for fpylll/0.5.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 356 days old (needed 2 days)
• cumin (- to 4.2.0-1)
  • Migration status for cumin (- to 4.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cumin would introduce bugs in testing: #1042262
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cumin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 358 days old (needed 5 days)
• varnish (- to 7.1.1-1.1)
  • Migration status for varnish (- to 7.1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating varnish would introduce bugs in testing: #1054484, #1056156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varnish.html
    • autopkgtest for varnish/7.1.1-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 359 days old (needed 2 days)
• php-smbclient (- to 1.0.6-8)
  • Migration status for php-smbclient (- to 1.0.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-smbclient would introduce bugs in testing: #1035516
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-smbclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 360 days old (needed 5 days)
• prody (- to 2.3.1+dfsg-3)
  • Migration status for prody (- to 2.3.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prody would introduce bugs in testing: #1053865, #1058454
    • autopkgtest for prody/2.3.1+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prody.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 360 days old (needed 5 days)
• apbs (- to 3.4.1-5)
  • Migration status for apbs (- to 3.4.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apbs would introduce bugs in testing: #1033528
    • autopkgtest for apbs/3.4.1-5: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • autopkgtest for apbs/blocked-on-ci-infra: armel: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apbs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 361 days old (needed 5 days)
• xraylib (- to 4.0.0+dfsg1-3)
  • Migration status for xraylib (- to 4.0.0+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xraylib would introduce bugs in testing: #1042221
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xraylib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 361 days old (needed 5 days)
• gbrainy (- to 1:2.4.6-1)
  • Migration status for gbrainy (- to 1:2.4.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gbrainy gtk-sharp3 (not considered)
    • Depends: gbrainy gtk-sharp3 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbrainy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• kodi-pvr-iptvsimple (- to 20.6.1+ds-1)
  • Migration status for kodi-pvr-iptvsimple (- to 20.6.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-iptvsimple kodi (not considered)
    • Depends: kodi-pvr-iptvsimple kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-iptvsimple.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• giara (- to 1.0.1-2)
  • Migration status for giara (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating giara would introduce bugs in testing: #1051091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giara.html
    • autopkgtest for giara/1.0.1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 363 days old (needed 5 days)
• libobjcryst (- to 2022.1.4+ds1-2)
  • Migration status for libobjcryst (- to 2022.1.4+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libobjcryst newmat (not considered)
    • Depends: libobjcryst newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobjcryst.html
    • autopkgtest for libobjcryst/2022.1.4+ds1-2: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 363 days old (needed 2 days)
• pyobjcryst (- to 2.2.5-1)
  • Migration status for pyobjcryst (- to 2.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyobjcryst libobjcryst (not considered)
    • Depends: pyobjcryst libobjcryst (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyobjcryst.html
    • autopkgtest for pyobjcryst/2.2.5-1: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 363 days old (needed 2 days)
• python-questplus (- to 2019.4-6)
  • Migration status for python-questplus (- to 2019.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-questplus python-xarray (not considered)
    • Depends: python-questplus python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-questplus.html
    • autopkgtest for python-questplus/2019.4-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 363 days old (needed 2 days)
• python-clickhouse-driver (- to 0.2.5-1)
  • Migration status for python-clickhouse-driver (- to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-clickhouse-driver would introduce bugs in testing: #1041206
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-clickhouse-driver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 364 days old (needed 5 days)
• php-mailparse (- to 3.1.4+2.1.7~dev20160128-1)
  • Migration status for php-mailparse (- to 3.1.4+2.1.7~dev20160128-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mailparse would introduce bugs in testing: #999998
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mailparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 365 days old (needed 5 days)
• php-mongodb (- to 1.15.0+1.11.1+1.9.2+1.7.5-1)
  • Migration status for php-mongodb (- to 1.15.0+1.11.1+1.9.2+1.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mongodb would introduce bugs in testing: #999997
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 365 days old (needed 5 days)
• closql-el (- to 1.2.1-3)
  • Migration status for closql-el (- to 1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating closql-el would introduce bugs in testing: #1052943
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/closql-el.html
    • autopkgtest for closql-el/1.2.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 366 days old (needed 2 days)
• nvidia-settings-legacy-390xx (- to 390.157-1)
  • Migration status for nvidia-settings-legacy-390xx (- to 390.157-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-legacy-390xx nvidia-graphics-drivers-legacy-390xx (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 366 days old (needed 5 days)
• nvidia-settings-tesla-418 (- to 418.113-9)
  • Migration status for nvidia-settings-tesla-418 (- to 418.113-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-418 nvidia-graphics-drivers-tesla-418 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 366 days old (needed 5 days)
• nvidia-settings-tesla-450 (- to 450.119.03-4)
  • Migration status for nvidia-settings-tesla-450 (- to 450.119.03-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-450 nvidia-graphics-drivers-tesla-450 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 366 days old (needed 5 days)
• nvidia-settings-tesla-460 (- to 460.91.03-4)
  • Migration status for nvidia-settings-tesla-460 (- to 460.91.03-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-460 nvidia-graphics-drivers-tesla-460 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 366 days old (needed 5 days)
• php-horde-sesha (- to 1.0.0~rc3-9)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-sesha php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
    • autopkgtest for php-horde-sesha/1.0.0~rc3-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 366 days old (needed 2 days)
• tycho (- to 1.6.0-3)
  • Migration status for tycho (- to 1.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libtycho-java/amd64 has unsatisfiable dependency
    • libtycho-java/arm64 has unsatisfiable dependency
    • Updating tycho would introduce bugs in testing: #1031686, #1033428, #1050407
    • tycho unsatisfiable Build-Depends(-Arch) on amd64: libeclipse-osgi-util-java
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tycho.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 366 days old (needed 5 days)
• nuitka (- to 1.3.5+ds-1)
  • Migration status for nuitka (- to 1.3.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nuitka would introduce bugs in testing: #1030440, #1035782
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nuitka.html
    • Reproducible on i386 - info ♻
    • 367 days old (needed 5 days)
• nvidia-settings-legacy-340xx (- to 340.108-7)
  • Migration status for nvidia-settings-legacy-340xx (- to 340.108-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-legacy-340xx nvidia-graphics-drivers-legacy-340xx (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 367 days old (needed 5 days)
• php-horde-turba (- to 4.2.29-2)
  • Migration status for php-horde-turba (- to 4.2.29-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-turba php-horde-dav (not considered)
    • Invalidated by dependency
    • Depends: php-horde-turba php-horde
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
    • autopkgtest for php-horde-turba/4.2.29-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 367 days old (needed 2 days)
• ruby-html-pipeline (- to 2.14.3-1)
  • Migration status for ruby-html-pipeline (- to 2.14.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-html-pipeline would introduce bugs in testing: #1053837
    • Build-Depends(-Arch): ruby-html-pipeline ruby-sanitize
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-html-pipeline.html
    • autopkgtest for ruby-html-pipeline/2.14.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 367 days old (needed 2 days)
• ruby-task-list (- to 2.3.2-2)
  • Migration status for ruby-task-list (- to 2.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-task-list ruby-html-pipeline (not considered)
    • Depends: ruby-task-list ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-task-list.html
    • autopkgtest for ruby-task-list/2.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 367 days old (needed 2 days)
• php-horde-ingo (- to 3.2.16-9)
  • Migration status for php-horde-ingo (- to 3.2.16-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-ingo php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
    • autopkgtest for php-horde-ingo/3.2.16-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 368 days old (needed 2 days)
• tetradraw (- to 2.0.3-10)
  • Migration status for tetradraw (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tetradraw would introduce bugs in testing: #1057594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tetradraw.html
    • 368 days old (needed 5 days)
• logbook (- to 1.5.3-5.2)
  • Migration status for logbook (- to 1.5.3-5.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating logbook would introduce bugs in testing: #1042681, #1055691, #1056420, #1056814
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/logbook.html
    • autopkgtest for logbook/1.5.3-5.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 369 days old (needed 2 days)
• php-horde-kronolith (- to 4.2.29-3)
  • Migration status for php-horde-kronolith (- to 4.2.29-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kronolith would introduce bugs in testing: #1054531
    • Depends: php-horde-kronolith php-horde
    • Depends: php-horde-kronolith php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
    • autopkgtest for php-horde-kronolith/4.2.29-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 369 days old (needed 2 days)
• qutip (- to 4.7.1-2)
  • Migration status for qutip (- to 4.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qutip would introduce bugs in testing: #1042704, #1056517, #1056880
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qutip.html
    • autopkgtest for qutip/4.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 369 days old (needed 2 days)
• emacspeak-ss (- to 1.12.1-9)
  • Migration status for emacspeak-ss (- to 1.12.1-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: emacspeak-ss emacspeak (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/emacspeak-ss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 370 days old (needed 5 days)
• safeclib (- to 3.7.1-2)
  • Migration status for safeclib (- to 3.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating safeclib would introduce bugs in testing: #1042344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safeclib.html
    • Reproducible on i386 - info ♻
    • 370 days old (needed 5 days)
• golang-github-google-cel-go (- to 0.12.5+ds-1)
  • Migration status for golang-github-google-cel-go (- to 0.12.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-google-cel-go/0.12.5+ds-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-cel-go.html
    • 372 days old (needed 5 days)
• openstack-meta-packages (- to 0.34)
  • Migration status for openstack-meta-packages (- to 0.34): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openstack-clients/amd64 has unsatisfiable dependency
    • openstack-clients/arm64 has unsatisfiable dependency
    • Depends: openstack-meta-packages nova
    • Depends: openstack-meta-packages placement
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openstack-meta-packages.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 373 days old (needed 5 days)
• php-sabre-vobject (- to 2.1.7-6.1)
  • Migration status for php-sabre-vobject (- to 2.1.7-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-vobject would introduce bugs in testing: #1052792
    • autopkgtest for php-sabre-vobject/2.1.7-6.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-vobject.html
    • Reproducible on i386 - info ♻
    • 373 days old (needed 5 days)
• tiemu (- to 3.04~git20220826.cda2db4+dfsg-2)
  • Migration status for tiemu (- to 3.04~git20220826.cda2db4+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tiemu libglade2 (not considered)
    • Depends: tiemu libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiemu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 373 days old (needed 5 days)
• eclipse-collections (- to 11.0.0.M3-3)
  • Migration status for eclipse-collections (- to 11.0.0.M3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eclipse-collections would introduce bugs in testing: #1031467
    • Build-Depends(-Arch): eclipse-collections tycho
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-collections.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 374 days old (needed 5 days)
• scalene (- to 1.5.16-1)
  • Migration status for scalene (- to 1.5.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scalene would introduce bugs in testing: #1037852, #1055725, #1056886
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scalene.html
    • autopkgtest for scalene/1.5.16-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 376 days old (needed 2 days)
• cypari2 (- to 2.1.2-4)
  • Migration status for cypari2 (- to 2.1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cypari2 would introduce bugs in testing: #1055731, #1056797
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cypari2.html
    • Reproducible on i386 - info ♻
    • 377 days old (needed 5 days)
• i3pystatus (- to 3.35+git20191126.5a8eaf4-2.1)
  • Migration status for i3pystatus (- to 3.35+git20191126.5a8eaf4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i3pystatus would introduce bugs in testing: #1056410
    • autopkgtest for i3pystatus/3.35+git20191126.5a8eaf4-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i3pystatus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 377 days old (needed 5 days)
• php-horde-ansel (- to 3.0.10+debian1-3)
  • Migration status for php-horde-ansel (- to 3.0.10+debian1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-ansel php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ansel.html
    • autopkgtest for php-horde-ansel/3.0.10+debian1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 377 days old (needed 2 days)
• python-omegaconf (- to 2.2.2-2.1)
  • Migration status for python-omegaconf (- to 2.2.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-omegaconf would introduce bugs in testing: #1042251
    • autopkgtest for python-omegaconf/2.2.2-2.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-omegaconf.html
    • 377 days old (needed 5 days)
• python-pyramid (- to 2.0+dfsg-2)
  • Migration status for python-pyramid (- to 2.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-pyramid python-plaster (not considered)
    • Depends: python-pyramid python-plaster (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): python-pyramid python-plaster-pastedeploy
    • Depends: python-pyramid python-plaster-pastedeploy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid.html
    • autopkgtest for python-pyramid/2.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 377 days old (needed 2 days)
• golang-github-bradenhilton-mozillainstallhash (- to 1.0.0-1)
  • Migration status for golang-github-bradenhilton-mozillainstallhash (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-github-bradenhilton-mozillainstallhash golang-github-bradenhilton-cityhash
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bradenhilton-mozillainstallhash.html
    • autopkgtest for golang-github-bradenhilton-mozillainstallhash/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 378 days old (needed 2 days)
• mailscripts (- to 28-1)
  • Migration status for mailscripts (- to 28-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailscripts python-pgpy (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailscripts.html
    • Reproducible on i386 - info ♻
    • 378 days old (needed 5 days)
• gfm (- to 1.09~git20220826.71eaa92-1)
  • Migration status for gfm (- to 1.09~git20220826.71eaa92-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gfm libglade2 (not considered)
    • Depends: gfm libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 379 days old (needed 5 days)
• libgit-annex-perl (- to 0.008-1)
  • Migration status for libgit-annex-perl (- to 0.008-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libgit-annex-perl/0.008-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgit-annex-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 379 days old (needed 5 days)
• speedcrunch (- to 0.12.0-6)
  • Migration status for speedcrunch (- to 0.12.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): speedcrunch quark-sphinx-theme (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speedcrunch.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 379 days old (needed 5 days)
• cpm (- to 0.32-1.5)
  • Migration status for cpm (- to 0.32-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpm would introduce bugs in testing: #851594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpm.html
    • Reproducible on i386 - info ♻
    • 380 days old (needed 5 days)
• multiplex (- to 0.6.0-1)
  • Migration status for multiplex (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating multiplex would introduce bugs in testing: #1027462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multiplex.html
    • autopkgtest for multiplex/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 383 days old (needed 2 days)
• kodi-pvr-nextpvr (- to 20.3.1+ds1-1)
  • Migration status for kodi-pvr-nextpvr (- to 20.3.1+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-nextpvr kodi (not considered)
    • Depends: kodi-pvr-nextpvr kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-nextpvr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 386 days old (needed 5 days)
• kodi-visualization-fishbmc (- to 20.2.0+ds1-1)
  • Migration status for kodi-visualization-fishbmc (- to 20.2.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-visualization-fishbmc kodi (not considered)
    • Depends: kodi-visualization-fishbmc kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-fishbmc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 386 days old (needed 5 days)
• tpot (- to 0.11.7+dfsg-5)
  • Migration status for tpot (- to 0.11.7+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpot would introduce bugs in testing: #1027205
    • autopkgtest for tpot/0.11.7+dfsg-5: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpot.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 387 days old (needed 5 days)
• freedom-maker (- to 0.32)
  • Migration status for freedom-maker (- to 0.32): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freedom-maker would introduce bugs in testing: #1056248, #1058100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freedom-maker.html
    • autopkgtest for freedom-maker/0.32: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 389 days old (needed 2 days)
• pigx-rnaseq (- to 0.1.0-1.1)
  • Migration status for pigx-rnaseq (- to 0.1.0-1.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pigx-rnaseq.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 389 days old (needed 5 days)
• prospector (- to 1.1.7-4)
  • Migration status for prospector (- to 1.1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • prospector/amd64 has unsatisfiable dependency
    • prospector/arm64 has unsatisfiable dependency
    • Updating prospector would introduce bugs in testing: #1055672, #947551
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prospector.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 389 days old (needed 5 days)
• btas (- to 0.0+git20221014.147bf4d4-1)
  • Migration status for btas (- to 0.0+git20221014.147bf4d4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btas would introduce bugs in testing: #1028634
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 392 days old (needed 5 days)
• jhbuild (- to 3.38.0-3.1)
  • Migration status for jhbuild (- to 3.38.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jhbuild would introduce bugs in testing: #1054720
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jhbuild.html
    • Reproducible on i386 - info ♻
    • 393 days old (needed 5 days)
• octave-vrml (- to 1.0.13-8)
  • Migration status for octave-vrml (- to 1.0.13-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-vrml whitedune (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-vrml.html
    • autopkgtest for octave-vrml/1.0.13-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 394 days old (needed 2 days)
• golang-github-jesseduffield-rollrus (- to 0.0~git20190701.dd028cb-4)
  • Migration status for golang-github-jesseduffield-rollrus (- to 0.0~git20190701.dd028cb-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-rollrus would introduce bugs in testing: #1032112
    • Build-Depends-Indep: golang-github-jesseduffield-rollrus golang-github-jesseduffield-roll
    • Depends: golang-github-jesseduffield-rollrus golang-github-jesseduffield-roll
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-rollrus.html
    • autopkgtest for golang-github-jesseduffield-rollrus/0.0~git20190701.dd028cb-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 395 days old (needed 2 days)
• python-certbot-dns-linode (- to 2.1.0-1)
  • Migration status for python-certbot-dns-linode (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-linode would introduce bugs in testing: #1049421
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-linode.html
    • autopkgtest for python-certbot-dns-linode/2.1.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• python-certbot-dns-ovh (- to 2.1.0-1)
  • Migration status for python-certbot-dns-ovh (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-ovh would introduce bugs in testing: #1054635
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-ovh.html
    • autopkgtest for python-certbot-dns-ovh/2.1.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• bookletimposer (- to 0.3.1-3)
  • Migration status for bookletimposer (- to 0.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bookletimposer would introduce bugs in testing: #1054753
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookletimposer.html
    • autopkgtest for bookletimposer/0.3.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 397 days old (needed 2 days)
• golang-github-bradenhilton-cityhash (- to 1.0.0-1)
  • Migration status for golang-github-bradenhilton-cityhash (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bradenhilton-cityhash.html
    • autopkgtest for golang-github-bradenhilton-cityhash/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 398 days old (needed 2 days)
• node-puppeteer (- to 13.4.1+dfsg-2)
  • Migration status for node-puppeteer (- to 13.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-puppeteer would introduce bugs in testing: #1026868, #1054431
    • autopkgtest for node-puppeteer/13.4.1+dfsg-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-puppeteer.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 400 days old (needed 5 days)
• pynfft (- to 1.3.2-7)
  • Migration status for pynfft (- to 1.3.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pynfft would introduce bugs in testing: #1055704, #1056845
    • Build-Depends(-Arch): pynfft nfft
    • Depends: pynfft nfft
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynfft.html
    • autopkgtest for pynfft/1.3.2-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 400 days old (needed 2 days)
• squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3.1)
  • Migration status for squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squeak-plugins-scratch would introduce bugs in testing: #909352
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeak-plugins-scratch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 401 days old (needed 5 days)
• golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-3)
  • Migration status for golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-sethvargo-go-fastly golang-github-ajg-form (not considered)
    • Depends: golang-github-sethvargo-go-fastly golang-github-ajg-form (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sethvargo-go-fastly.html
    • autopkgtest for golang-github-sethvargo-go-fastly/1.2.1+git20190805.5c6c8bd-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 403 days old (needed 2 days)
• jupyter-sphinx (- to 0.3.2-2)
  • Migration status for jupyter-sphinx (- to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jupyter-sphinx would introduce bugs in testing: #950598
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-sphinx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• libapache-db-perl (- to 0.18-2)
  • Migration status for libapache-db-perl (- to 0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-db-perl would introduce bugs in testing: #1040396
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-db-perl.html
    • autopkgtest for libapache-db-perl/0.18-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• pyjunitxml (- to 0.7-2)
  • Migration status for pyjunitxml (- to 0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyjunitxml would introduce bugs in testing: #1057356
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyjunitxml.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 403 days old (needed 5 days)
• pydicom (- to 2.3.1-1)
  • Migration status for pydicom (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pydicom would introduce bugs in testing: #1042612
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydicom.html
    • autopkgtest for pydicom/2.3.1-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 404 days old (needed 5 days)
• djangorestframework-filters (- to 1.0.0.dev2-2)
  • Migration status for djangorestframework-filters (- to 1.0.0.dev2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating djangorestframework-filters would introduce bugs in testing: #1052818
    • Build-Depends(-Arch): djangorestframework-filters python-django-crispy-forms
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djangorestframework-filters.html
    • autopkgtest for djangorestframework-filters/1.0.0.dev2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 405 days old (needed 2 days)
• flask-appbuilder (- to 4.1.4+ds-3)
  • Migration status for flask-appbuilder (- to 4.1.4+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-flask-appbuilder/amd64 has unsatisfiable dependency
    • python3-flask-appbuilder/arm64 has unsatisfiable dependency
    • Updating flask-appbuilder would introduce bugs in testing: #1020739, #1036167
    • flask-appbuilder unsatisfiable Build-Depends(-Arch) on amd64: python3-marshmallow-enum
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/flask-appbuilder.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 405 days old (needed 5 days)
• octocatalog-diff (- to 2.1.0-1)
  • Migration status for octocatalog-diff (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octocatalog-diff would introduce bugs in testing: #1025300
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octocatalog-diff.html
    • autopkgtest for octocatalog-diff/2.1.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 405 days old (needed 5 days)
• funguloids (- to 1.06-15)
  • Migration status for funguloids (- to 1.06-15): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): funguloids ogre-1.9 (not considered)
    • Depends: funguloids ogre-1.9 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/funguloids.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 406 days old (needed 5 days)
• pdm (- to 2.2.1+ds1-1)
  • Migration status for pdm (- to 2.2.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdm would introduce bugs in testing: #1043002
    • Build-Depends(-Arch): pdm pep517
    • Depends: pdm pep517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 406 days old (needed 5 days)
• perl-doc-html (- to 5.26.0-7)
  • Migration status for perl-doc-html (- to 5.26.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating perl-doc-html would introduce bugs in testing: #907974
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl-doc-html.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 406 days old (needed 5 days)
• cpptraj (- to 5.1.0+dfsg-3)
  • Migration status for cpptraj (- to 5.1.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpptraj would introduce bugs in testing: #1035833
    • autopkgtest for cpptraj/5.1.0+dfsg-3: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpptraj.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 408 days old (needed 5 days)
• python-jpype (- to 1.4.1-1)
  • Migration status for python-jpype (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-jpype would introduce bugs in testing: #1055714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jpype.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 409 days old (needed 5 days)
• python-webargs (- to 8.0.1-2)
  • Migration status for python-webargs (- to 8.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-webargs python-pyramid (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-webargs.html
    • autopkgtest for python-webargs/8.0.1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 409 days old (needed 5 days)
• vimix (- to 0.7.2+git20221123+ds-1)
  • Migration status for vimix (- to 0.7.2+git20221123+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vimix would introduce bugs in testing: #1037883
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vimix.html
    • 409 days old (needed 5 days)
• gnome-authenticator (- to 3.32.2+dfsg1-5)
  • Migration status for gnome-authenticator (- to 3.32.2+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-authenticator would introduce bugs in testing: #993849
    • Build-Depends(-Arch): gnome-authenticator libhandy
    • Depends: gnome-authenticator libhandy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-authenticator.html
    • autopkgtest for gnome-authenticator/3.32.2+dfsg1-5: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 411 days old (needed 5 days)
• golang-github-jesseduffield-go-getter (- to 0.0~git20180822.906e156-5)
  • Migration status for golang-github-jesseduffield-go-getter (- to 0.0~git20180822.906e156-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-go-getter would introduce bugs in testing: #1032107
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-go-getter.html
    • autopkgtest for golang-github-jesseduffield-go-getter/0.0~git20180822.906e156-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 411 days old (needed 2 days)
• golang-github-jesseduffield-roll (- to 0.0~git20190629.695be2e-3)
  • Migration status for golang-github-jesseduffield-roll (- to 0.0~git20190629.695be2e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-roll would introduce bugs in testing: #1032113
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-roll.html
    • autopkgtest for golang-github-jesseduffield-roll/0.0~git20190629.695be2e-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 411 days old (needed 2 days)
• golang-github-keybase-go-ps (- to 0.0~git20190827.91aafc9-1)
  • Migration status for golang-github-keybase-go-ps (- to 0.0~git20190827.91aafc9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-keybase-go-ps.html
    • autopkgtest for golang-github-keybase-go-ps/0.0~git20190827.91aafc9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 411 days old (needed 2 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-leanovate-gopter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 411 days old (needed 5 days)
• heudiconv (- to 0.11.6-1)
  • Migration status for heudiconv (- to 0.11.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): heudiconv pydicom (not considered)
    • Depends: heudiconv pydicom (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): heudiconv dcmstack
    • Depends: heudiconv dcmstack
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heudiconv.html
    • autopkgtest for heudiconv/0.11.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 411 days old (needed 2 days)
• ogre-1.9 (- to 1.9.0+dfsg1-14)
  • Migration status for ogre-1.9 (- to 1.9.0+dfsg1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ogre-1.9 would introduce bugs in testing: #1024182
    • Depends: ogre-1.9 blender
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogre-1.9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 411 days old (needed 5 days)
• golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-3)
  • Migration status for golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-asciigraph would introduce bugs in testing: #1032108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-asciigraph.html
    • autopkgtest for golang-github-jesseduffield-asciigraph/0.4.1+git20190605.6d88e39-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-2)
  • Migration status for golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-pty would introduce bugs in testing: #1032111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-pty.html
    • autopkgtest for golang-github-jesseduffield-pty/1.1.3+git20191112.07ed706-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• golang-github-jesseduffield-yaml (- to 2.2.2+git20190702.b900b7e-3)
  • Migration status for golang-github-jesseduffield-yaml (- to 2.2.2+git20190702.b900b7e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-yaml would introduce bugs in testing: #1032190
    • autopkgtest for golang-github-jesseduffield-yaml/2.2.2+git20190702.b900b7e-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-yaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 412 days old (needed 5 days)
• golang-github-muesli-combinator (- to 0.3.0-1)
  • Migration status for golang-github-muesli-combinator (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-muesli-combinator.html
    • autopkgtest for golang-github-muesli-combinator/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• golang-github-twpayne-go-pinentry (- to 0.2.0-1)
  • Migration status for golang-github-twpayne-go-pinentry (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-pinentry.html
    • autopkgtest for golang-github-twpayne-go-pinentry/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• golang-github-twpayne-go-shell (- to 0.3.1-1)
  • Migration status for golang-github-twpayne-go-shell (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-shell.html
    • autopkgtest for golang-github-twpayne-go-shell/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• golang-github-twpayne-go-vfs (- to 4.1.0-1)
  • Migration status for golang-github-twpayne-go-vfs (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-vfs.html
    • autopkgtest for golang-github-twpayne-go-vfs/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• golang-github-twpayne-go-xdg (- to 6.0.0-1)
  • Migration status for golang-github-twpayne-go-xdg (- to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-github-twpayne-go-xdg golang-github-twpayne-go-vfs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-xdg.html
    • autopkgtest for golang-github-twpayne-go-xdg/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 412 days old (needed 2 days)
• opensysusers (- to 0.7.3-2)
  • Migration status for opensysusers (- to 0.7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensysusers would introduce bugs in testing: #1055517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensysusers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• rust-fxprof-processed-profile (- to 0.4.0-2)
  • Migration status for rust-fxprof-processed-profile (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-fxprof-processed-profile would introduce bugs in testing: #1030997
    • autopkgtest for rust-fxprof-processed-profile/0.4.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fxprof-processed-profile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• shush (- to 1.2.3-5.1)
  • Migration status for shush (- to 1.2.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shush would introduce bugs in testing: #999964
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• syncmaildir (- to 1.3.0-2)
  • Migration status for syncmaildir (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating syncmaildir would introduce bugs in testing: #1000322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncmaildir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 414 days old (needed 5 days)
• ueberzug (- to 18.1.9-4)
  • Migration status for ueberzug (- to 18.1.9-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ueberzug would introduce bugs in testing: #1041381
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ueberzug.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 414 days old (needed 5 days)
• dh-make-golang (- to 0.6.0-2)
  • Migration status for dh-make-golang (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dh-make-golang would introduce bugs in testing: #1043070, #1050523
    • autopkgtest for dh-make-golang/0.6.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • dh-make-golang/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/armel has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/armhf has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/i386 has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.8-2
    • dh-make-golang/s390x has unsatisfiable Built-Using on golang-1.19 1.19.8-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-make-golang.html
    • Reproducible on i386 - info ♻
    • 415 days old (needed 5 days)
• qflow (- to 1.3.17+dfsg.1-3)
  • Migration status for qflow (- to 1.3.17+dfsg.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): qflow opensta (not considered)
    • Depends: qflow opensta (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qflow.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for qflow/1.3.17+dfsg.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 415 days old (needed 2 days)
• tipp (- to 1.0+dfsg-3)
  • Migration status for tipp (- to 1.0+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tipp sepp (not considered)
    • Depends: tipp sepp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tipp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 416 days old (needed 5 days)
• django-session-security (- to 2.6.6+dfsg-2)
  • Migration status for django-session-security (- to 2.6.6+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-session-security would introduce bugs in testing: #1042590
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-session-security.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• golang-github-github-smimesign (- to 0.2.0+dfsg-1)
  • Migration status for golang-github-github-smimesign (- to 0.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costela, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-github-smimesign.html
    • autopkgtest for golang-github-github-smimesign/0.2.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 417 days old (needed 2 days)
• kodi-audiodecoder-fluidsynth (- to 20.2.1+ds1-2)
  • Migration status for kodi-audiodecoder-fluidsynth (- to 20.2.1+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audiodecoder-fluidsynth kodi (not considered)
    • Depends: kodi-audiodecoder-fluidsynth kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audiodecoder-fluidsynth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-audiodecoder-openmpt (- to 20.2.0+ds1-2)
  • Migration status for kodi-audiodecoder-openmpt (- to 20.2.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audiodecoder-openmpt kodi (not considered)
    • Depends: kodi-audiodecoder-openmpt kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audiodecoder-openmpt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-audiodecoder-sidplay (- to 20.2.0+ds1-2)
  • Migration status for kodi-audiodecoder-sidplay (- to 20.2.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audiodecoder-sidplay kodi (not considered)
    • Depends: kodi-audiodecoder-sidplay kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audiodecoder-sidplay.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-audioencoder-flac (- to 20.2.0+ds1-2)
  • Migration status for kodi-audioencoder-flac (- to 20.2.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audioencoder-flac kodi (not considered)
    • Depends: kodi-audioencoder-flac kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audioencoder-flac.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-audioencoder-lame (- to 20.3.0+ds1-2)
  • Migration status for kodi-audioencoder-lame (- to 20.3.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audioencoder-lame kodi (not considered)
    • Depends: kodi-audioencoder-lame kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audioencoder-lame.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-audioencoder-vorbis (- to 20.2.0+ds1-2)
  • Migration status for kodi-audioencoder-vorbis (- to 20.2.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audioencoder-vorbis kodi (not considered)
    • Depends: kodi-audioencoder-vorbis kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audioencoder-vorbis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-audioencoder-wav (- to 20.2.0-2)
  • Migration status for kodi-audioencoder-wav (- to 20.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-audioencoder-wav kodi (not considered)
    • Depends: kodi-audioencoder-wav kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-audioencoder-wav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-imagedecoder-raw (- to 20.1.0+ds1-2)
  • Migration status for kodi-imagedecoder-raw (- to 20.1.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-imagedecoder-raw kodi (not considered)
    • Depends: kodi-imagedecoder-raw kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-imagedecoder-raw.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-inputstream-rtmp (- to 20.3.0+ds1-1)
  • Migration status for kodi-inputstream-rtmp (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-inputstream-rtmp kodi (not considered)
    • Depends: kodi-inputstream-rtmp kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-inputstream-rtmp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-argustv (- to 20.5.0+ds1-1)
  • Migration status for kodi-pvr-argustv (- to 20.5.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-argustv kodi (not considered)
    • Depends: kodi-pvr-argustv kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-argustv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-dvblink (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-dvblink (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-dvblink kodi (not considered)
    • Depends: kodi-pvr-dvblink kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-dvblink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-dvbviewer (- to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-dvbviewer (- to 20.4.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-dvbviewer kodi (not considered)
    • Depends: kodi-pvr-dvbviewer kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-dvbviewer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-filmon (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-filmon (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-filmon kodi (not considered)
    • Depends: kodi-pvr-filmon kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-filmon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-hdhomerun (- to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-hdhomerun (- to 20.4.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-hdhomerun kodi (not considered)
    • Depends: kodi-pvr-hdhomerun kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-hdhomerun.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-hts (- to 20.6.0+ds1-1)
  • Migration status for kodi-pvr-hts (- to 20.6.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-hts kodi (not considered)
    • Depends: kodi-pvr-hts kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-hts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-mediaportal-tvserver (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-mediaportal-tvserver (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-mediaportal-tvserver kodi (not considered)
    • Depends: kodi-pvr-mediaportal-tvserver kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-mediaportal-tvserver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-mythtv (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-mythtv (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-mythtv kodi (not considered)
    • Depends: kodi-pvr-mythtv kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-mythtv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-njoy (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-njoy (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-njoy kodi (not considered)
    • Depends: kodi-pvr-njoy kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-njoy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-octonet (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-octonet (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-octonet kodi (not considered)
    • Depends: kodi-pvr-octonet kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-octonet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-pctv (- to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-pctv (- to 20.4.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-pctv kodi (not considered)
    • Depends: kodi-pvr-pctv kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-pctv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-sledovanitv-cz (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-sledovanitv-cz (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-sledovanitv-cz kodi (not considered)
    • Depends: kodi-pvr-sledovanitv-cz kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-sledovanitv-cz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-stalker (- to 20.3.1+ds1-1)
  • Migration status for kodi-pvr-stalker (- to 20.3.1+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-stalker kodi (not considered)
    • Depends: kodi-pvr-stalker kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-stalker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-vbox (- to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-vbox (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-vbox kodi (not considered)
    • Depends: kodi-pvr-vbox kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-vbox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-vdr-vnsi (- to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-vdr-vnsi (- to 20.4.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-vdr-vnsi kodi (not considered)
    • Depends: kodi-pvr-vdr-vnsi kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-vdr-vnsi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-waipu (- to 20.6.0+ds1-1)
  • Migration status for kodi-pvr-waipu (- to 20.6.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-waipu kodi (not considered)
    • Depends: kodi-pvr-waipu kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-waipu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-pvr-wmc (- to 20.3.0-1)
  • Migration status for kodi-pvr-wmc (- to 20.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-pvr-wmc kodi (not considered)
    • Depends: kodi-pvr-wmc kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-pvr-wmc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-screensaver-asteroids (- to 20.1.0+ds1-2)
  • Migration status for kodi-screensaver-asteroids (- to 20.1.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-screensaver-asteroids kodi (not considered)
    • Depends: kodi-screensaver-asteroids kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-screensaver-asteroids.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-screensaver-biogenesis (- to 20.1.0-2)
  • Migration status for kodi-screensaver-biogenesis (- to 20.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-screensaver-biogenesis kodi (not considered)
    • Depends: kodi-screensaver-biogenesis kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-screensaver-biogenesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-screensaver-greynetic (- to 20.1.0+ds1-2)
  • Migration status for kodi-screensaver-greynetic (- to 20.1.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-screensaver-greynetic kodi (not considered)
    • Depends: kodi-screensaver-greynetic kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-screensaver-greynetic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-screensaver-pingpong (- to 20.1.0+ds1-2)
  • Migration status for kodi-screensaver-pingpong (- to 20.1.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-screensaver-pingpong kodi (not considered)
    • Depends: kodi-screensaver-pingpong kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-screensaver-pingpong.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-screensaver-pyro (- to 20.1.0-2)
  • Migration status for kodi-screensaver-pyro (- to 20.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-screensaver-pyro kodi (not considered)
    • Depends: kodi-screensaver-pyro kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-screensaver-pyro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-screensaver-shadertoy (- to 20.1.0+ds1-2)
  • Migration status for kodi-screensaver-shadertoy (- to 20.1.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-screensaver-shadertoy kodi (not considered)
    • Depends: kodi-screensaver-shadertoy kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-screensaver-shadertoy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-vfs-libarchive (- to 20.2.0+ds1-1)
  • Migration status for kodi-vfs-libarchive (- to 20.2.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-vfs-libarchive kodi (not considered)
    • Depends: kodi-vfs-libarchive kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-vfs-libarchive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-vfs-sftp (- to 20.1.0+ds1-2)
  • Migration status for kodi-vfs-sftp (- to 20.1.0+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-vfs-sftp kodi (not considered)
    • Depends: kodi-vfs-sftp kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-vfs-sftp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-visualization-pictureit (- to 20.2.0+ds1-1)
  • Migration status for kodi-visualization-pictureit (- to 20.2.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-visualization-pictureit kodi (not considered)
    • Depends: kodi-visualization-pictureit kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-pictureit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-visualization-shadertoy (- to 20.3.0+ds1-1)
  • Migration status for kodi-visualization-shadertoy (- to 20.3.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-visualization-shadertoy kodi (not considered)
    • Depends: kodi-visualization-shadertoy kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-shadertoy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-visualization-spectrum (- to 20.2.0+ds1-1)
  • Migration status for kodi-visualization-spectrum (- to 20.2.0+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-visualization-spectrum kodi (not considered)
    • Depends: kodi-visualization-spectrum kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-spectrum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• kodi-visualization-waveform (- to 20.2.1+ds1-1)
  • Migration status for kodi-visualization-waveform (- to 20.2.1+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kodi-visualization-waveform kodi (not considered)
    • Depends: kodi-visualization-waveform kodi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-waveform.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• platformio (- to 4.3.4-3)
  • Migration status for platformio (- to 4.3.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating platformio would introduce bugs in testing: #1053285, #988716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformio.html
    • autopkgtest for platformio/4.3.4-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 417 days old (needed 5 days)
• el-get (- to 3.1-2)
  • Migration status for el-get (- to 3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating el-get would introduce bugs in testing: #912364, #916857
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/el-get.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 418 days old (needed 5 days)
• traittypes (- to 0.2.1-4)
  • Migration status for traittypes (- to 0.2.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): traittypes python-xarray (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/traittypes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 418 days old (needed 5 days)
• yaramod (- to 3.6.0-1.1)
  • Migration status for yaramod (- to 3.6.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yaramod would introduce bugs in testing: #1037908
    • autopkgtest for yaramod/3.6.0-1.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaramod.html
    • Reproducible on i386 - info ♻
    • 418 days old (needed 5 days)
• cool-retro-term (- to 1.2.0+ds2-1)
  • Migration status for cool-retro-term (- to 1.2.0+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cool-retro-term would introduce bugs in testing: #1042347
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cool-retro-term.html
    • 419 days old (needed 5 days)
• python-djvulibre (- to 0.8.8-3)
  • Migration status for python-djvulibre (- to 0.8.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-djvulibre would introduce bugs in testing: #1042661, #1056468, #1056854
    • autopkgtest for python-djvulibre/0.8.8-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-djvulibre.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 421 days old (needed 5 days)
• python-http-parser (- to 0.9.0-3)
  • Migration status for python-http-parser (- to 0.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-http-parser would introduce bugs in testing: #1055713
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-http-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 421 days old (needed 5 days)
• aws-checksums (- to 0.1.13-1)
  • Migration status for aws-checksums (- to 0.1.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libaws-checksums-dev/amd64 has unsatisfiable dependency
    • libaws-checksums1.0.0/amd64 has unsatisfiable dependency
    • Updating aws-checksums would introduce bugs in testing: #1029332, #1050400
    • aws-checksums unsatisfiable Build-Depends(-Arch) on amd64: libaws-c-common-dev
    • Not built on buildd: arch amd64 binaries uploaded by noahm
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/aws-checksums.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 423 days old (needed 5 days)
• fruit (- to 2.1.dfsg-10)
  • Migration status for fruit (- to 2.1.dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fruit would introduce bugs in testing: #1014187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fruit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 423 days old (needed 5 days)
• pstotext (- to 1.9-7)
  • Migration status for pstotext (- to 1.9-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pstotext would introduce bugs in testing: #895513
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pstotext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 423 days old (needed 5 days)
• salt (- to 3004.1+dfsg-2.2)
  • Migration status for salt (- to 3004.1+dfsg-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating salt would introduce bugs in testing: #1013872, #1021317, #1021920, #1022530, #1028421, #1033808, #1051504, #1055179
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): salt pytest-salt-factories
    • Build-Depends(-Arch): salt python-pyvmomi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/salt.html
    • 425 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-3.1)
  • Migration status for libjpeg6b (- to 1:6b2-3.1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • Build-Depends(-Arch): libjpeg6b automake1.11
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg6b.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 427 days old (needed 5 days)
• gamgi (- to 0.17.5-1)
  • Migration status for gamgi (- to 0.17.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gamgi gtkglext (not considered)
    • Depends: gamgi gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gamgi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 428 days old (needed 5 days)
• objcryst-fox (- to 2022.1-1)
  • Migration status for objcryst-fox (- to 2022.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): objcryst-fox newmat (not considered)
    • Depends: objcryst-fox newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/objcryst-fox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 429 days old (needed 5 days)
• python-redmine (- to 2.3.0-3)
  • Migration status for python-redmine (- to 2.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-redmine would introduce bugs in testing: #1056502, #1058134
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-redmine.html
    • autopkgtest for python-redmine/2.3.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 430 days old (needed 2 days)
• golang-github-blynn-nex (- to 0.0.0+git.2021.03.30.1a3320dab9-2)
  • Migration status for golang-github-blynn-nex (- to 0.0.0+git.2021.03.30.1a3320dab9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-blynn-nex would introduce bugs in testing: #1022957
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-blynn-nex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 432 days old (needed 5 days)
• pytest-services (- to 2.2.1+ds-3)
  • Migration status for pytest-services (- to 2.2.1+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytest-services/2.2.1+ds-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): pytest-services mysql-8.0
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-services.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 432 days old (needed 5 days)
• python-django-crispy-forms (- to 1.14.0-4)
  • Migration status for python-django-crispy-forms (- to 1.14.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-crispy-forms would introduce bugs in testing: #1052852
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-crispy-forms.html
    • autopkgtest for python-django-crispy-forms/1.14.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 435 days old (needed 2 days)
• python-plaster-pastedeploy (- to 0.5-5)
  • Migration status for python-plaster-pastedeploy (- to 0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-plaster-pastedeploy would introduce bugs in testing: #1052860
    • Build-Depends(-Arch): python-plaster-pastedeploy python-plaster
    • Depends: python-plaster-pastedeploy python-plaster
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-plaster-pastedeploy.html
    • autopkgtest for python-plaster-pastedeploy/0.5-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 435 days old (needed 2 days)
• python-pyramid-chameleon (- to 0.3-7)
  • Migration status for python-pyramid-chameleon (- to 0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-chameleon would introduce bugs in testing: #1052780, #1056499
    • Build-Depends(-Arch): python-pyramid-chameleon python-pyramid
    • Depends: python-pyramid-chameleon python-pyramid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-chameleon.html
    • autopkgtest for python-pyramid-chameleon/0.3-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 435 days old (needed 2 days)
• embree (- to 3.13.5+dfsg-2)
  • Migration status for embree (- to 3.13.5+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating embree would introduce bugs in testing: #1052881
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/embree.html
    • 436 days old (needed 5 days)
• golang-github-libvirt-libvirt-go-xml (- to 7.4.0-1)
  • Migration status for golang-github-libvirt-libvirt-go-xml (- to 7.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-libvirt-libvirt-go-xml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 436 days old (needed 5 days)
• python-django-crispy-forms-foundation (- to 0.9.0+ds-1)
  • Migration status for python-django-crispy-forms-foundation (- to 0.9.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-django-crispy-forms-foundation python-django-crispy-forms (not considered)
    • Depends: python-django-crispy-forms-foundation python-django-crispy-forms (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-crispy-forms-foundation.html
    • autopkgtest for python-django-crispy-forms-foundation/0.9.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 438 days old (needed 2 days)
• libvmod-re2 (- to 2.0.0-2)
  • Migration status for libvmod-re2 (- to 2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libvmod-re2 varnish (not considered)
    • Depends: libvmod-re2 varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-re2.html
    • autopkgtest for libvmod-re2/2.0.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 440 days old (needed 2 days)
• libvmod-selector (- to 2.6.0-3)
  • Migration status for libvmod-selector (- to 2.6.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libvmod-selector varnish (not considered)
    • Depends: libvmod-selector varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-selector.html
    • autopkgtest for libvmod-selector/2.6.0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 440 days old (needed 2 days)
• python-semantic-release (- to 7.32.2-1)
  • Migration status for python-semantic-release (- to 7.32.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-semantic-release would introduce bugs in testing: #1056503, #1058357
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-semantic-release.html
    • autopkgtest for python-semantic-release/7.32.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 441 days old (needed 2 days)
• courier-filter-perl (- to 0.200+ds-6)
  • Migration status for courier-filter-perl (- to 0.200+ds-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: courier-filter-perl courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-filter-perl.html
    • autopkgtest for courier-filter-perl/0.200+ds-6: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 442 days old (needed 5 days)
• python-rdata (- to 0.5-3)
  • Migration status for python-rdata (- to 0.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-rdata python-xarray (not considered)
    • Depends: python-rdata python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rdata.html
    • autopkgtest for python-rdata/0.5-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 442 days old (needed 5 days)
• pep517 (- to 0.13.0-2)
  • Migration status for pep517 (- to 0.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pep517 would introduce bugs in testing: #1050683
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pep517.html
    • autopkgtest for pep517/0.13.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 443 days old (needed 2 days)
• autolink (- to 0.10.0-1)
  • Migration status for autolink (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autolink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 447 days old (needed 5 days)
• devpi-common (- to 3.2.2-3)
  • Migration status for devpi-common (- to 3.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating devpi-common would introduce bugs in testing: #1030453
    • autopkgtest for devpi-common/3.2.2-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devpi-common.html
    • 447 days old (needed 5 days)
• dradio (- to 3.8-2.1)
  • Migration status for dradio (- to 3.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dradio would introduce bugs in testing: #1057554
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dradio.html
    • Reproducible on i386 - info ♻
    • 447 days old (needed 5 days)
• flufl.bounce (- to 4.0-3)
  • Migration status for flufl.bounce (- to 4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flufl.bounce would introduce bugs in testing: #1042674
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flufl.bounce.html
    • autopkgtest for flufl.bounce/4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 447 days old (needed 2 days)
• nwdiag (- to 2.0.0+dfsg-1.1)
  • Migration status for nwdiag (- to 2.0.0+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nwdiag would introduce bugs in testing: #1042235
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nwdiag.html
    • Reproducible on i386 - info ♻
    • 447 days old (needed 5 days)
• python-b2sdk (- to 1.17.3-2)
  • Migration status for python-b2sdk (- to 1.17.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-b2sdk would introduce bugs in testing: #1056458
    • autopkgtest for python-b2sdk/1.17.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-b2sdk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 447 days old (needed 5 days)
• subdownloader (- to 2.1.0-5)
  • Migration status for subdownloader (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating subdownloader would introduce bugs in testing: #1042355
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subdownloader.html
    • autopkgtest for subdownloader/2.1.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 447 days old (needed 2 days)
• analizo (- to 1.25.4-2)
  • Migration status for analizo (- to 1.25.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating analizo would introduce bugs in testing: #1051534
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/analizo.html
    • autopkgtest for analizo/1.25.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 449 days old (needed 2 days)
• fsprotect (- to 1.0.7+nmu1)
  • Migration status for fsprotect (- to 1.0.7+nmu1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fsprotect aufs (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsprotect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• lockdown (- to 0.2+nmu1)
  • Migration status for lockdown (- to 0.2+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lockdown would introduce bugs in testing: #958587
    • lockdown unsatisfiable Build-Depends(-Arch) on amd64: dh-systemd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lockdown.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 449 days old (needed 5 days)
• mailman-suite (- to 0+20200530-2.1)
  • Migration status for mailman-suite (- to 0+20200530-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mailman-suite postorius (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mailman-suite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• matrix-sydent (- to 2.5.1-1.1)
  • Migration status for matrix-sydent (- to 2.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matrix-sydent would introduce bugs in testing: #1029442, #1035844
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/matrix-sydent.html
  • Additional info:
    • autopkgtest for matrix-sydent/2.5.1-1.1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• mom (- to 0.6.0-2.1)
  • Migration status for mom (- to 0.6.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mom would introduce bugs in testing: #1014781
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• networking-mlnx (- to 1:16.0.0-3.1)
  • Migration status for networking-mlnx (- to 1:16.0.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating networking-mlnx would introduce bugs in testing: #1021924
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networking-mlnx.html
    • 449 days old (needed 5 days)
• openscap-daemon (- to 0.1.10-3.1)
  • Migration status for openscap-daemon (- to 0.1.10-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openscap-daemon/amd64 has unsatisfiable dependency
    • openscap-daemon/arm64 has unsatisfiable dependency
    • Updating openscap-daemon would introduce bugs in testing: #1035384
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openscap-daemon.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• prometheus-pgbouncer-exporter (- to 1.7-2.1)
  • Migration status for prometheus-pgbouncer-exporter (- to 1.7-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prometheus-pgbouncer-exporter would introduce bugs in testing: #991879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-pgbouncer-exporter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• python-ara (- to 1.5.8-1.1)
  • Migration status for python-ara (- to 1.5.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ara would introduce bugs in testing: #1038732
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-ara.html
  • Additional info:
    • 449 days old (needed 5 days)
• sopel (- to 6.6.9-2.1)
  • Migration status for sopel (- to 6.6.9-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sopel would introduce bugs in testing: #943405
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sopel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 449 days old (needed 5 days)
• bcbio (- to 1.2.9-2)
  • Migration status for bcbio (- to 1.2.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): bcbio logbook (not considered)
    • Depends: bcbio logbook (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for bcbio/1.2.9-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻
    • 451 days old (needed 5 days)
• libtoxcore (- to 0.2.18-1)
  • Migration status for libtoxcore (- to 0.2.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtoxcore would introduce bugs in testing: #1053501
    • autopkgtest for libtoxcore/0.2.18-1: amd64: Regression or new test ♻ , arm64: Pass, armel: Regression or new test ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtoxcore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 452 days old (needed 5 days)
• libvmod-redis (- to 15.1-1)
  • Migration status for libvmod-redis (- to 15.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libvmod-redis varnish (not considered)
    • Depends: libvmod-redis varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-redis.html
    • autopkgtest for libvmod-redis/15.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 452 days old (needed 2 days)
• telegram-cli (- to 1.3.1+git20160323.6547c0b21-3.1)
  • Migration status for telegram-cli (- to 1.3.1+git20160323.6547c0b21-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-cli would introduce bugs in testing: #1018754
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 452 days old (needed 5 days)
• mozillavpn (- to 2.9.0-1)
  • Migration status for mozillavpn (- to 2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mozillavpn would introduce bugs in testing: #1027506, #1043004
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mozillavpn.html
    • missing build on mips64el
  • Additional info:
    • 453 days old (needed 5 days)
• dde-store (- to 1.2.3+dfsg-2)
  • Migration status for dde-store (- to 1.2.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by sramacher
    • Trying to remove package, not update it
    • Updating dde-store would introduce bugs in testing: #1059237
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/amd64
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/arm64
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/armel
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/armhf
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/i386
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/mips64el
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/ppc64el
    • Impossible Depends: dde-store -> libappstreamqt2/0.16.4-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dde-store.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 454 days old (needed 5 days)
    • Remove hint for (transitive) dependency: dde-store
• rust-cradle (- to 0.2.2-2)
  • Migration status for rust-cradle (- to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cradle-dev/amd64 has unsatisfiable dependency
    • librust-cradle-dev/arm64 has unsatisfiable dependency
    • librust-cradle-dev/armel has unsatisfiable dependency
    • librust-cradle-dev/armhf has unsatisfiable dependency
    • librust-cradle-dev/i386 has unsatisfiable dependency
    • librust-cradle-dev/mips64el has unsatisfiable dependency
    • librust-cradle-dev/ppc64el has unsatisfiable dependency
    • librust-cradle-dev/s390x has unsatisfiable dependency
    • Updating rust-cradle would introduce bugs in testing: #1030989
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cradle.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 456 days old (needed 5 days)
• bettercap-caplets (- to 0+git20210429-1)
  • Migration status for bettercap-caplets (- to 0+git20210429-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bettercap-caplets/amd64 has unsatisfiable dependency
    • bettercap-caplets/arm64 has unsatisfiable dependency
    • Updating bettercap-caplets would introduce bugs in testing: #1053331
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bettercap-caplets.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 458 days old (needed 5 days)
• pantalaimon (- to 0.10.5-1)
  • Migration status for pantalaimon (- to 0.10.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pantalaimon would introduce bugs in testing: #1023971
    • Depends: pantalaimon logbook
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantalaimon.html
    • autopkgtest for pantalaimon/0.10.5-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 460 days old (needed 5 days)
• cclive (- to 0.9.3-0.3)
  • Migration status for cclive (- to 0.9.3-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclive would introduce bugs in testing: #1000076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cclive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 461 days old (needed 5 days)
• rust-matchers (- to 0.1.0-1)
  • Migration status for rust-matchers (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-matchers-dev/amd64 has unsatisfiable dependency
    • librust-matchers-dev/arm64 has unsatisfiable dependency
    • librust-matchers-dev/armel has unsatisfiable dependency
    • librust-matchers-dev/armhf has unsatisfiable dependency
    • librust-matchers-dev/i386 has unsatisfiable dependency
    • librust-matchers-dev/mips64el has unsatisfiable dependency
    • librust-matchers-dev/ppc64el has unsatisfiable dependency
    • librust-matchers-dev/s390x has unsatisfiable dependency
    • Updating rust-matchers would introduce bugs in testing: #1053420, #1054722
    • rust-matchers unsatisfiable Build-Depends(-Arch) on amd64: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on arm64: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on armel: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on armhf: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on i386: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on mips64el: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on ppc64el: librust-regex-automata-0.1+default-dev
    • rust-matchers unsatisfiable Build-Depends(-Arch) on s390x: librust-regex-automata-0.1+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-matchers.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 461 days old (needed 5 days)
• python-flanker (- to 0.9.14-3)
  • Migration status for python-flanker (- to 0.9.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-flanker would introduce bugs in testing: #1033714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flanker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 462 days old (needed 5 days)
• dcmstack (- to 0.9-1)
  • Migration status for dcmstack (- to 0.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dcmstack/0.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): dcmstack pydicom
    • Depends: dcmstack pydicom
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcmstack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 464 days old (needed 5 days)
• gpsshogi (- to 0.7.0-3.1)
  • Migration status for gpsshogi (- to 0.7.0-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gpsshogi poco (not considered)
    • Depends: gpsshogi poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpsshogi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 466 days old (needed 5 days)
• keras (- to 2.3.1+dfsg2-1)
  • Migration status for keras (- to 2.3.1+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-keras/amd64 has unsatisfiable dependency
    • python3-keras/arm64 has unsatisfiable dependency
    • Updating keras would introduce bugs in testing: #1026738
    • keras unsatisfiable Build-Depends(-Arch) on amd64: python3-theano
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/keras.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 471 days old (needed 5 days)
• emacspeak (- to 53.0+dfsg-2)
  • Migration status for emacspeak (- to 53.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacspeak would introduce bugs in testing: #1051402
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/emacspeak.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 474 days old (needed 5 days)
• packagesearch (- to 2.8.0)
  • Migration status for packagesearch (- to 2.8.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating packagesearch would introduce bugs in testing: #1050896
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packagesearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 475 days old (needed 5 days)
• bing (- to 1.3.5-5)
  • Migration status for bing (- to 1.3.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bing would introduce bugs in testing: #1054398
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 479 days old (needed 5 days)
• sylpheed (- to 3.8.0~beta1-1)
  • Migration status for sylpheed (- to 3.8.0~beta1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sylpheed would introduce bugs in testing: #1036424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sylpheed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 479 days old (needed 5 days)
• sagetex (- to 3.6.1+ds-1)
  • Migration status for sagetex (- to 3.6.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sagetex/3.6.1+ds-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): sagetex sagemath
    • Depends: sagetex sagemath
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagetex.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 483 days old (needed 5 days)
• watchman (- to 4.9.0-7)
  • Migration status for watchman (- to 4.9.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watchman would introduce bugs in testing: #999930
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 483 days old (needed 5 days)
• roger-router (- to 2.4.2-3)
  • Migration status for roger-router (- to 2.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • roger-router/amd64 has unsatisfiable dependency
    • roger-router/arm64 has unsatisfiable dependency
    • roger-router/armel has unsatisfiable dependency
    • roger-router/armhf has unsatisfiable dependency
    • roger-router/i386 has unsatisfiable dependency
    • roger-router/mips64el has unsatisfiable dependency
    • roger-router/ppc64el has unsatisfiable dependency
    • roger-router/s390x has unsatisfiable dependency
    • Updating roger-router would introduce bugs in testing: #1019303
    • Build-Depends(-Arch): roger-router librm
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/roger-router.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 487 days old (needed 5 days)
• libgovirt (- to 0.3.9-2)
  • Migration status for libgovirt (- to 0.3.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgovirt would introduce bugs in testing: #1030904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgovirt.html
    • Reproducible on arm64 - info ♻
    • 488 days old (needed 5 days)
• librm (- to 2.2.3-1)
  • Migration status for librm (- to 2.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librm0/amd64 has unsatisfiable dependency
    • librm0/arm64 has unsatisfiable dependency
    • librm0/armel has unsatisfiable dependency
    • librm0/armhf has unsatisfiable dependency
    • librm0/i386 has unsatisfiable dependency
    • librm0/mips64el has unsatisfiable dependency
    • librm0/ppc64el has unsatisfiable dependency
    • librm0/s390x has unsatisfiable dependency
    • Updating librm would introduce bugs in testing: #1022008, #1037392
    • librm unsatisfiable Build-Depends(-Arch) on amd64: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on amd64: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on arm64: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on arm64: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armel: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armel: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armhf: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armhf: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on i386: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on i386: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on mips64el: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on mips64el: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on ppc64el: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on ppc64el: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on s390x: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on s390x: libgssdp-1.2-dev | libgssdp-1.0-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libr/librm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 496 days old (needed 5 days)
• gnome-subtitles (- to 1.8-1)
  • Migration status for gnome-subtitles (- to 1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-subtitles would introduce bugs in testing: #1053529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-subtitles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 500 days old (needed 5 days)
• pandoc-citeproc-preamble (- to 1.7-1)
  • Migration status for pandoc-citeproc-preamble (- to 1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pandoc-citeproc-preamble would introduce bugs in testing: #1054770
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandoc-citeproc-preamble.html
    • autopkgtest for pandoc-citeproc-preamble/1.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 503 days old (needed 2 days)
• django-cachalot (- to 2.4.3-2)
  • Migration status for django-cachalot (- to 2.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-django-cachalot/amd64 has unsatisfiable dependency
    • python3-django-cachalot/arm64 has unsatisfiable dependency
    • Updating django-cachalot would introduce bugs in testing: #1055207
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/django-cachalot.html
    • django-cachalot unsatisfiable Build-Depends(-Arch) on amd64: python3-django (<< 3:3.3~)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 509 days old (needed 5 days)
• varnish-modules (- to 0.20.0-2)
  • Migration status for varnish-modules (- to 0.20.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): varnish-modules varnish (not considered)
    • Depends: varnish-modules varnish (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varnish-modules.html
    • autopkgtest for varnish-modules/0.20.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 512 days old (needed 2 days)
• debian-design (- to 3.0.27)
  • Migration status for debian-design (- to 3.0.27): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-design blender (not considered)
    • Invalidated by dependency
    • Depends: debian-design bookletimposer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-design.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 513 days old (needed 5 days)
• s3ql (- to 3.7.3+dfsg-2)
  • Migration status for s3ql (- to 3.7.3+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): s3ql python-dugong (not considered)
    • Depends: s3ql python-dugong (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/s3ql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 514 days old (needed 5 days)
• medialibrary (- to 0.12.3-1)
  • Migration status for medialibrary (- to 0.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating medialibrary would introduce bugs in testing: #1042710, #949532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/medialibrary.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 515 days old (needed 5 days)
• haskell-happstack-authenticate (- to 2.6.1-1)
  • Migration status for haskell-happstack-authenticate (- to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-happstack-authenticate-dev/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-doc/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-doc/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/armel has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/armel has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/armhf has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/armhf has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/i386 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/i386 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/mips64el has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/mips64el has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/ppc64el has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/ppc64el has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/s390x has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/s390x has unsatisfiable dependency
    • Updating haskell-happstack-authenticate would introduce bugs in testing: #1054957, #1057719
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-shakespeare-dev (<< 2.1)
    • Build-Depends(-Arch): haskell-happstack-authenticate haskell-userid
    • Build-Depends-Indep: haskell-happstack-authenticate haskell-userid
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-happstack-authenticate.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 516 days old (needed 5 days)
• smlsharp (- to 4.0.0+git20211227.5af5945b-2)
  • Migration status for smlsharp (- to 4.0.0+git20211227.5af5945b-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): smlsharp massivethreads (not considered)
    • Depends: smlsharp massivethreads (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlsharp.html
    • 521 days old (needed 5 days)
• xir (- to 2.5-1)
  • Migration status for xir (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xir would introduce bugs in testing: #1037901
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xir.html
    • 521 days old (needed 5 days)
• gnome-online-miners (- to 3.34.0-6)
  • Migration status for gnome-online-miners (- to 3.34.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-online-miners would introduce bugs in testing: #1014461
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-online-miners.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 522 days old (needed 5 days)
• haskell-userid (- to 0.1.3.7-1)
  • Migration status for haskell-userid (- to 0.1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-userid-dev/amd64 has unsatisfiable dependency
    • libghc-userid-doc/amd64 has unsatisfiable dependency
    • libghc-userid-prof/amd64 has unsatisfiable dependency
    • libghc-userid-dev/arm64 has unsatisfiable dependency
    • libghc-userid-doc/arm64 has unsatisfiable dependency
    • libghc-userid-prof/arm64 has unsatisfiable dependency
    • libghc-userid-dev/armel has unsatisfiable dependency
    • libghc-userid-prof/armel has unsatisfiable dependency
    • libghc-userid-dev/armhf has unsatisfiable dependency
    • libghc-userid-prof/armhf has unsatisfiable dependency
    • libghc-userid-dev/i386 has unsatisfiable dependency
    • libghc-userid-prof/i386 has unsatisfiable dependency
    • libghc-userid-dev/mips64el has unsatisfiable dependency
    • libghc-userid-prof/mips64el has unsatisfiable dependency
    • libghc-userid-dev/ppc64el has unsatisfiable dependency
    • libghc-userid-prof/ppc64el has unsatisfiable dependency
    • libghc-userid-dev/s390x has unsatisfiable dependency
    • libghc-userid-prof/s390x has unsatisfiable dependency
    • Updating haskell-userid would introduce bugs in testing: #1054977, #1057718
    • haskell-userid unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on armel: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on mips64el: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on s390x: libghc-aeson-dev (<< 2.1)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-userid.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 524 days old (needed 5 days)
• ortools (- to 8.2+ds-6)
  • Migration status for ortools (- to 8.2+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libortools8/amd64 has unsatisfiable dependency
    • ortools-samples/amd64 has unsatisfiable dependency
    • python3-ortools/amd64 has unsatisfiable dependency
    • libortools8/arm64 has unsatisfiable dependency
    • ortools-samples/arm64 has unsatisfiable dependency
    • python3-ortools/arm64 has unsatisfiable dependency
    • libortools8/ppc64el has unsatisfiable dependency
    • ortools-samples/ppc64el has unsatisfiable dependency
    • python3-ortools/ppc64el has unsatisfiable dependency
    • Updating ortools would introduce bugs in testing: #1024790, #1040564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/ortools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 524 days old (needed 5 days)
• python-django-rest-hooks (- to 1.6.0-3)
  • Migration status for python-django-rest-hooks (- to 1.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-rest-hooks would introduce bugs in testing: #1056466, #1058107
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-rest-hooks.html
    • autopkgtest for python-django-rest-hooks/1.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 524 days old (needed 2 days)
• haskell-hindent (- to 5.3.4-1)
  • Migration status for haskell-hindent (- to 5.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hindent-doc/amd64 has unsatisfiable dependency
    • libghc-hindent-doc/arm64 has unsatisfiable dependency
    • libghc-hindent-dev/mips64el has unsatisfiable dependency
    • libghc-hindent-prof/mips64el has unsatisfiable dependency
    • Updating haskell-hindent would introduce bugs in testing: #1053982
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 525 days old (needed 5 days)
• haskell-hsyaml (- to 0.2.1.1-2)
  • Migration status for haskell-hsyaml (- to 0.2.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsyaml-dev/amd64 has unsatisfiable dependency
    • libghc-hsyaml-doc/amd64 has unsatisfiable dependency
    • libghc-hsyaml-prof/amd64 has unsatisfiable dependency
    • libghc-hsyaml-dev/arm64 has unsatisfiable dependency
    • libghc-hsyaml-doc/arm64 has unsatisfiable dependency
    • libghc-hsyaml-prof/arm64 has unsatisfiable dependency
    • libghc-hsyaml-dev/armel has unsatisfiable dependency
    • libghc-hsyaml-prof/armel has unsatisfiable dependency
    • libghc-hsyaml-dev/armhf has unsatisfiable dependency
    • libghc-hsyaml-prof/armhf has unsatisfiable dependency
    • libghc-hsyaml-dev/i386 has unsatisfiable dependency
    • libghc-hsyaml-prof/i386 has unsatisfiable dependency
    • libghc-hsyaml-dev/mips64el has unsatisfiable dependency
    • libghc-hsyaml-prof/mips64el has unsatisfiable dependency
    • libghc-hsyaml-dev/ppc64el has unsatisfiable dependency
    • libghc-hsyaml-prof/ppc64el has unsatisfiable dependency
    • libghc-hsyaml-dev/s390x has unsatisfiable dependency
    • libghc-hsyaml-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsyaml would introduce bugs in testing: #1054863
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsyaml.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 526 days old (needed 5 days)
• nfft (- to 3.5.3-1)
  • Migration status for nfft (- to 3.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nfft would introduce bugs in testing: #1016377, #1016378, #1016379
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nfft.html
    • autopkgtest for nfft/3.5.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 527 days old (needed 2 days)
• go-mode.el (- to 3:1.6.0-1)
  • Migration status for go-mode.el (- to 3:1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-mode.el would introduce bugs in testing: #1052922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-mode.el.html
    • Reproducible on i386 - info ♻
    • 528 days old (needed 5 days)
• micropython (- to 1.19.1+ds-1)
  • Migration status for micropython (- to 1.19.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating micropython would introduce bugs in testing: #1042992
    • autopkgtest for micropython/1.19.1+ds-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , i386: Regression or new test ♻
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/micropython.html
    • Reproducible on i386 - info ♻
    • 531 days old (needed 5 days)
• haskell-ircbot (- to 0.6.6.1-1)
  • Migration status for haskell-ircbot (- to 0.6.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-ircbot-dev/amd64 has unsatisfiable dependency
    • libghc-ircbot-doc/amd64 has unsatisfiable dependency
    • libghc-ircbot-prof/amd64 has unsatisfiable dependency
    • libghc-ircbot-dev/arm64 has unsatisfiable dependency
    • libghc-ircbot-doc/arm64 has unsatisfiable dependency
    • libghc-ircbot-prof/arm64 has unsatisfiable dependency
    • libghc-ircbot-dev/armel has unsatisfiable dependency
    • libghc-ircbot-prof/armel has unsatisfiable dependency
    • libghc-ircbot-dev/armhf has unsatisfiable dependency
    • libghc-ircbot-prof/armhf has unsatisfiable dependency
    • libghc-ircbot-dev/i386 has unsatisfiable dependency
    • libghc-ircbot-prof/i386 has unsatisfiable dependency
    • libghc-ircbot-dev/mips64el has unsatisfiable dependency
    • libghc-ircbot-prof/mips64el has unsatisfiable dependency
    • libghc-ircbot-dev/ppc64el has unsatisfiable dependency
    • libghc-ircbot-prof/ppc64el has unsatisfiable dependency
    • libghc-ircbot-dev/s390x has unsatisfiable dependency
    • libghc-ircbot-prof/s390x has unsatisfiable dependency
    • Updating haskell-ircbot would introduce bugs in testing: #1054947, #1057720
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on amd64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on arm64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on armel: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on armhf: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on i386: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on mips64el: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on s390x: libghc-optparse-applicative-dev (<< 0.17)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-ircbot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 532 days old (needed 5 days)
• maildrop (- to 2.9.3-2.1)
  • Migration status for maildrop (- to 2.9.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating maildrop would introduce bugs in testing: #1000129
    • Build-Depends(-Arch): maildrop courier-authlib
    • Depends: maildrop courier-authlib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maildrop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 532 days old (needed 5 days)
• threadscope (- to 0.2.14.1-1)
  • Migration status for threadscope (- to 0.2.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating threadscope would introduce bugs in testing: #1054939
    • threadscope unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on armel: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on mips64el: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on s390x: libghc-ghc-events-dev (<< 0.18)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/threadscope.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 532 days old (needed 5 days)
• haskell-reform-hsp (- to 0.2.7.2-2)
  • Migration status for haskell-reform-hsp (- to 0.2.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-dev/armel has unsatisfiable dependency
    • libghc-reform-hsp-prof/armel has unsatisfiable dependency
    • libghc-reform-hsp-dev/armhf has unsatisfiable dependency
    • libghc-reform-hsp-prof/armhf has unsatisfiable dependency
    • libghc-reform-hsp-dev/i386 has unsatisfiable dependency
    • libghc-reform-hsp-prof/i386 has unsatisfiable dependency
    • libghc-reform-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-reform-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-reform-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-hsp-dev/s390x has unsatisfiable dependency
    • libghc-reform-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform-hsp would introduce bugs in testing: #1054865, #1056758
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-reform-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• haskell-tidal (- to 1.7.10-1)
  • Migration status for haskell-tidal (- to 1.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-tidal-dev/amd64 has unsatisfiable dependency
    • libghc-tidal-doc/amd64 has unsatisfiable dependency
    • libghc-tidal-prof/amd64 has unsatisfiable dependency
    • libghc-tidal-dev/arm64 has unsatisfiable dependency
    • libghc-tidal-doc/arm64 has unsatisfiable dependency
    • libghc-tidal-prof/arm64 has unsatisfiable dependency
    • libghc-tidal-dev/armel has unsatisfiable dependency
    • libghc-tidal-prof/armel has unsatisfiable dependency
    • libghc-tidal-dev/armhf has unsatisfiable dependency
    • libghc-tidal-prof/armhf has unsatisfiable dependency
    • libghc-tidal-dev/i386 has unsatisfiable dependency
    • libghc-tidal-prof/i386 has unsatisfiable dependency
    • libghc-tidal-dev/mips64el has unsatisfiable dependency
    • libghc-tidal-prof/mips64el has unsatisfiable dependency
    • libghc-tidal-dev/ppc64el has unsatisfiable dependency
    • libghc-tidal-prof/ppc64el has unsatisfiable dependency
    • libghc-tidal-dev/s390x has unsatisfiable dependency
    • libghc-tidal-prof/s390x has unsatisfiable dependency
    • Updating haskell-tidal would introduce bugs in testing: #1054931, #1057722
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on amd64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on amd64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on arm64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on arm64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armel: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armel: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armhf: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armhf: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on i386: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on i386: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on mips64el: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on s390x: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on s390x: libghc-primitive-dev (<< 0.8)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-tidal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• ruby-jekyll-coffeescript (- to 1.2.2-3)
  • Migration status for ruby-jekyll-coffeescript (- to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-coffeescript would introduce bugs in testing: #1030873
    • Depends: ruby-jekyll-coffeescript ruby-coffee-script
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-coffeescript.html
    • autopkgtest for ruby-jekyll-coffeescript/1.2.2-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• gcc-10-doc (- to 10.4.0-1)
  • Migration status for gcc-10-doc (- to 10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10-doc would introduce bugs in testing: #1032733
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 537 days old (needed 5 days)
• gcc-11-doc (- to 11.3.0-1)
  • Migration status for gcc-11-doc (- to 11.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-doc would introduce bugs in testing: #1057560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 537 days old (needed 5 days)
• pyrcb2 (- to 0.6.2-2)
  • Migration status for pyrcb2 (- to 0.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyrcb2 would introduce bugs in testing: #1056441, #1058431
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrcb2.html
    • autopkgtest for pyrcb2/0.6.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 539 days old (needed 2 days)
• php-fig-link-util (- to 1.2.0-1)
  • Migration status for php-fig-link-util (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fig-link-util would introduce bugs in testing: #947346
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fig-link-util.html
    • autopkgtest for php-fig-link-util/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 546 days old (needed 2 days)
• php-horde-rpc (- to 2.1.9-2)
  • Migration status for php-horde-rpc (- to 2.1.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-rpc php-horde-dav (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 548 days old (needed 5 days)
• apertium-cy-en (- to 0.1.1~r57554-9)
  • Migration status for apertium-cy-en (- to 0.1.1~r57554-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-cy-en would introduce bugs in testing: #1016320
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-cy-en.html
    • autopkgtest for apertium-cy-en/0.1.1~r57554-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 550 days old (needed 2 days)
• apertium-mlt-ara (- to 0.2.0~r62623-3)
  • Migration status for apertium-mlt-ara (- to 0.2.0~r62623-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-mlt-ara would introduce bugs in testing: #1016336
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-mlt-ara.html
    • 551 days old (needed 5 days)
• chemps2 (- to 1.8.12-1)
  • Migration status for chemps2 (- to 1.8.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chemps2 would introduce bugs in testing: #1042629, #1056794
    • autopkgtest for chemps2/1.8.12-1: arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for chemps2/blocked-on-ci-infra: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chemps2.html
    • 553 days old (needed 5 days)
• python-restless (- to 2.2.0-2)
  • Migration status for python-restless (- to 2.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-restless python-pyramid (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-restless.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 553 days old (needed 5 days)
• libnet-jabber-loudmouth-perl (- to 0.07-4)
  • Migration status for libnet-jabber-loudmouth-perl (- to 0.07-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libnet-jabber-loudmouth-perl libnet-jabber-perl (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-jabber-loudmouth-perl.html
    • autopkgtest for libnet-jabber-loudmouth-perl/0.07-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 555 days old (needed 2 days)
• qtox (- to 1.17.6-0.1)
  • Migration status for qtox (- to 1.17.6-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for qtox/1.17.6-0.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): qtox libtoxcore
    • Depends: qtox libtoxcore
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 555 days old (needed 5 days)
• ippsample (- to 0.0~git20220607.72f89b3-1)
  • Migration status for ippsample (- to 0.0~git20220607.72f89b3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ippsample would introduce bugs in testing: #1042570
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 565 days old (needed 5 days)
• kel-agent (- to 0.4.6-2)
  • Migration status for kel-agent (- to 0.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kel-agent would introduce bugs in testing: #1033710
    • autopkgtest for kel-agent/0.4.6-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kel-agent.html
    • 565 days old (needed 5 days)
• quark-sphinx-theme (- to 0.5.1-3)
  • Migration status for quark-sphinx-theme (- to 0.5.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quark-sphinx-theme would introduce bugs in testing: #1042679
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quark-sphinx-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 565 days old (needed 5 days)
• python-plaster (- to 1.0-3)
  • Migration status for python-plaster (- to 1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-plaster would introduce bugs in testing: #1052866
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-plaster.html
    • autopkgtest for python-plaster/1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 566 days old (needed 2 days)
• python-libguess (- to 1.1-5)
  • Migration status for python-libguess (- to 1.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-libguess libguess (not considered)
    • Depends: python-libguess libguess (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libguess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 567 days old (needed 5 days)
• apertium-crh-tur (- to 0.3.0-2)
  • Migration status for apertium-crh-tur (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-crh-tur would introduce bugs in testing: #1016319
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-crh-tur.html
    • 568 days old (needed 5 days)
• libnet-jabber-perl (- to 2.0-9)
  • Migration status for libnet-jabber-perl (- to 2.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libnet-jabber-perl libnet-xmpp-perl (not considered)
    • Depends: libnet-jabber-perl libnet-xmpp-perl (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-jabber-perl.html
    • autopkgtest for libnet-jabber-perl/2.0-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 569 days old (needed 2 days)
• libnet-xmpp-perl (- to 1.05-2)
  • Migration status for libnet-xmpp-perl (- to 1.05-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libnet-xmpp-perl would introduce bugs in testing: #1050336
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-xmpp-perl.html
    • autopkgtest for libnet-xmpp-perl/1.05-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 569 days old (needed 2 days)
• pytest-bdd (- to 5.0.0-1)
  • Migration status for pytest-bdd (- to 5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-bdd would introduce bugs in testing: #1042332
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-bdd.html
    • autopkgtest for pytest-bdd/5.0.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 569 days old (needed 5 days)
• howdoi (- to 1.1.9-1.1)
  • Migration status for howdoi (- to 1.1.9-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating howdoi would introduce bugs in testing: #1051370
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/howdoi.html
    • autopkgtest for howdoi/1.1.9-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 572 days old (needed 2 days)
• libdevel-bt-perl (- to 0.06-5)
  • Migration status for libdevel-bt-perl (- to 0.06-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdevel-bt-perl would introduce bugs in testing: #1022133
    • autopkgtest for libdevel-bt-perl/0.06-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdevel-bt-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 572 days old (needed 5 days)
• ruby-eye (- to 0.7-5.1)
  • Migration status for ruby-eye (- to 0.7-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-eye would introduce bugs in testing: #1031479
    • autopkgtest for ruby-eye/0.7-5.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-eye ruby-celluloid-io
    • Depends: ruby-eye ruby-celluloid-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-eye.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 572 days old (needed 5 days)
• autofill-forms (- to 1.1.3-1.1)
  • Migration status for autofill-forms (- to 1.1.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autofill-forms would introduce bugs in testing: #899309
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autofill-forms.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 573 days old (needed 5 days)
• celery-haystack-ng (- to 0.20.post2-1.1)
  • Migration status for celery-haystack-ng (- to 0.20.post2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating celery-haystack-ng would introduce bugs in testing: #999908
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/celery-haystack-ng.html
    • Reproducible on i386 - info ♻
    • 573 days old (needed 5 days)
• python-pyepsg (- to 0.4.0-1)
  • Migration status for python-pyepsg (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyepsg would introduce bugs in testing: #1033851
    • autopkgtest for python-pyepsg/0.4.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyepsg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 575 days old (needed 5 days)
• lmod (- to 8.6.19-1)
  • Migration status for lmod (- to 8.6.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lmod would introduce bugs in testing: #1052807
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lmod.html
    • autopkgtest for lmod/8.6.19-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 579 days old (needed 2 days)
• dynamic-motd (- to 0.04-1)
  • Migration status for dynamic-motd (- to 0.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dynamic-motd would introduce bugs in testing: #1029394
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dynamic-motd.html
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 580 days old (needed 5 days)
• golang-github-bsm-pool (- to 0.8.0-6)
  • Migration status for golang-github-bsm-pool (- to 0.8.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-bsm-pool would introduce bugs in testing: #1017816
    • autopkgtest for golang-github-bsm-pool/0.8.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-pool.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 581 days old (needed 5 days)
• ripe-atlas-sagan (- to 1.2.2-3)
  • Migration status for ripe-atlas-sagan (- to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ripe-atlas-sagan would introduce bugs in testing: #1026529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-sagan.html
    • 581 days old (needed 5 days)
• wikitrans (- to 1.3-2)
  • Migration status for wikitrans (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wikitrans would introduce bugs in testing: #1056360
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wikitrans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 581 days old (needed 5 days)
• python-morris (- to 1.2-3)
  • Migration status for python-morris (- to 1.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-morris would introduce bugs in testing: #1026584
    • autopkgtest for python-morris/1.2-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-morris.html
    • 582 days old (needed 5 days)
• python-padme (- to 1.1.1-4)
  • Migration status for python-padme (- to 1.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-padme would introduce bugs in testing: #1042700
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-padme.html
    • autopkgtest for python-padme/1.1.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 582 days old (needed 2 days)
• python-shade (- to 1.30.0-4)
  • Migration status for python-shade (- to 1.30.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-shade would introduce bugs in testing: #1013524
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-shade.html
    • 582 days old (needed 5 days)
• python-amqplib (- to 1.0.2-3)
  • Migration status for python-amqplib (- to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-amqplib would introduce bugs in testing: #1054744
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-amqplib.html
    • autopkgtest for python-amqplib/1.0.2-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 583 days old (needed 5 days)
• python-django-etcd-settings (- to 0.1.13+dfsg-4)
  • Migration status for python-django-etcd-settings (- to 0.1.13+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-etcd-settings would introduce bugs in testing: #1042333
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-etcd-settings.html
    • Reproducible on i386 - info ♻
    • 583 days old (needed 5 days)
• rust-ioctl-sys (- to 0.8.0-1)
  • Migration status for rust-ioctl-sys (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ioctl-sys/0.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ioctl-sys.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 584 days old (needed 5 days)
• golang-github-bsm-redeo (- to 2.1.1-5)
  • Migration status for golang-github-bsm-redeo (- to 2.1.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-bsm-redeo golang-github-bsm-pool (not considered)
    • Depends: golang-github-bsm-redeo golang-github-bsm-pool (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-redeo.html
    • autopkgtest for golang-github-bsm-redeo/2.1.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 585 days old (needed 2 days)
• tiny-dnn (- to 1.0.0a3+ds-3)
  • Migration status for tiny-dnn (- to 1.0.0a3+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tiny-dnn would introduce bugs in testing: #1041134
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiny-dnn.html
    • 587 days old (needed 5 days)
• flufl.enum (- to 4.1.1-5)
  • Migration status for flufl.enum (- to 4.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flufl.enum would introduce bugs in testing: #1042664
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flufl.enum.html
    • autopkgtest for flufl.enum/4.1.1-5: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 589 days old (needed 5 days)
• libnet-jabber-bot-perl (- to 2.1.7-2)
  • Migration status for libnet-jabber-bot-perl (- to 2.1.7-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libnet-jabber-bot-perl libnet-jabber-perl (not considered)
    • Depends: libnet-jabber-bot-perl libnet-jabber-perl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-jabber-bot-perl.html
    • autopkgtest for libnet-jabber-bot-perl/2.1.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 589 days old (needed 2 days)
• flufl.i18n (- to 3.0.1-3)
  • Migration status for flufl.i18n (- to 3.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flufl.i18n would introduce bugs in testing: #1042620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flufl.i18n.html
    • autopkgtest for flufl.i18n/3.0.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 590 days old (needed 2 days)
• flask-testing (- to 0.8.1-2)
  • Migration status for flask-testing (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-testing would introduce bugs in testing: #1026543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-testing.html
    • 591 days old (needed 5 days)
• flufl.password (- to 1.3-5)
  • Migration status for flufl.password (- to 1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flufl.password would introduce bugs in testing: #1042685
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flufl.password.html
    • autopkgtest for flufl.password/1.3-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 591 days old (needed 2 days)
• node-matrix-js-sdk (- to 9.11.0+~cs9.9.16-2)
  • Migration status for node-matrix-js-sdk (- to 9.11.0+~cs9.9.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-matrix-js-sdk would introduce bugs in testing: #1018970, #1021136, #1033621, #958692, #994213
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-matrix-js-sdk.html
    • autopkgtest for node-matrix-js-sdk/9.11.0+~cs9.9.16-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 591 days old (needed 5 days)
• golang-github-siddontang-goredis (- to 0.0~git20150324.0.760763f-6)
  • Migration status for golang-github-siddontang-goredis (- to 0.0~git20150324.0.760763f-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-siddontang-goredis golang-github-alicebob-miniredis (not considered)
    • Depends: golang-github-siddontang-goredis golang-github-alicebob-miniredis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-siddontang-goredis.html
    • autopkgtest for golang-github-siddontang-goredis/0.0~git20150324.0.760763f-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 592 days old (needed 2 days)
• python-aiohttp-apispec (- to 3.0.0~b2+ds1-2)
  • Migration status for python-aiohttp-apispec (- to 3.0.0~b2+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-aiohttp-apispec python-webargs (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiohttp-apispec.html
    • autopkgtest for python-aiohttp-apispec/3.0.0~b2+ds1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 592 days old (needed 5 days)
• autoconf2.64 (- to 2.64+dfsg-1.1)
  • Migration status for autoconf2.64 (- to 2.64+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoconf2.64 would introduce bugs in testing: #1039531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoconf2.64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 596 days old (needed 5 days)
• provean (- to 1.1.5+ds-2)
  • Migration status for provean (- to 1.1.5+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating provean would introduce bugs in testing: #1042769
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/provean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 599 days old (needed 5 days)
• cider (- to 0.19.0+dfsg-3)
  • Migration status for cider (- to 0.19.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cider would introduce bugs in testing: #1017834
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cider.html
    • autopkgtest for cider/0.19.0+dfsg-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): cider clojure-mode
    • Depends: cider clojure-mode
  • Additional info:
    • Waiting for reproducibility test results on i386 - info ♻
    • 606 days old (needed 5 days)
• mysql-connector-python (- to 8.0.15-3)
  • Migration status for mysql-connector-python (- to 8.0.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-connector-python would introduce bugs in testing: #923347
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-connector-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 613 days old (needed 5 days)
• openjdk-11-jre-dcevm (- to 11.0.15+1-1)
  • Migration status for openjdk-11-jre-dcevm (- to 11.0.15+1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-11-jre-dcevm/11.0.15+1-1: amd64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): openjdk-11-jre-dcevm openjdk-11
    • Depends: openjdk-11-jre-dcevm openjdk-11
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11-jre-dcevm.html
    • New but not reproducible on amd64 - info ♻
    • 613 days old (needed 5 days)
• pulseaudio-dlna (- to 0.6.4.1-0.1)
  • Migration status for pulseaudio-dlna (- to 0.6.4.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pulseaudio-dlna would introduce bugs in testing: #1016288
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pulseaudio-dlna.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 614 days old (needed 5 days)
• django-macaddress (- to 1.5.0-3)
  • Migration status for django-macaddress (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-macaddress would introduce bugs in testing: #1054372
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-macaddress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 622 days old (needed 5 days)
• bernhard (- to 0.2.6-3)
  • Migration status for bernhard (- to 0.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bernhard would introduce bugs in testing: #1028371
    • autopkgtest for bernhard/0.2.6-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bernhard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 625 days old (needed 5 days)
• cerealizer (- to 0.8.1-4)
  • Migration status for cerealizer (- to 0.8.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cerealizer would introduce bugs in testing: #1026587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cerealizer.html
    • 625 days old (needed 5 days)
• pytest-salt-factories (- to 0.907.0-4)
  • Migration status for pytest-salt-factories (- to 0.907.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-salt-factories would introduce bugs in testing: #1009804
    • autopkgtest for pytest-salt-factories/0.907.0-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-salt-factories.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 631 days old (needed 5 days)
• aiocoap (- to 0.4.3-0.1)
  • Migration status for aiocoap (- to 0.4.3-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiocoap would introduce bugs in testing: #1013528
    • autopkgtest for aiocoap/0.4.3-0.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiocoap.html
    • 632 days old (needed 5 days)
• dap-mode (- to 0.7-3)
  • Migration status for dap-mode (- to 0.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dap-mode lsp-mode (not considered)
    • Invalidated by dependency
    • Depends: dap-mode lsp-treemacs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dap-mode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 632 days old (needed 5 days)
• glean-parser (- to 5.1.2-1)
  • Migration status for glean-parser (- to 5.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glean-parser would introduce bugs in testing: #1026750
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glean-parser.html
    • 632 days old (needed 5 days)
• lsp-java (- to 0.20211124-2)
  • Migration status for lsp-java (- to 0.20211124-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lsp-java lsp-mode (not considered)
    • Invalidated by dependency
    • Depends: lsp-java dap-mode
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 632 days old (needed 5 days)
• lsp-treemacs (- to 0.4-3)
  • Migration status for lsp-treemacs (- to 0.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lsp-treemacs lsp-mode (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-treemacs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 632 days old (needed 5 days)
• coyote (- to 2022.04.12-1)
  • Migration status for coyote (- to 2022.04.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coyote/2022.04.12-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coyote.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 633 days old (needed 5 days)
• ntopng (- to 5.2.1+dfsg1-1)
  • Migration status for ntopng (- to 5.2.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ntopng would introduce bugs in testing: #1013302
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntopng.html
    • 633 days old (needed 5 days)
• courier-authlib (- to 0.71.4-1)
  • Migration status for courier-authlib (- to 0.71.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating courier-authlib would introduce bugs in testing: #987009
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-authlib.html
    • autopkgtest for courier-authlib/0.71.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 634 days old (needed 2 days)
• redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1)
  • Migration status for redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-custom-css redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-custom-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 635 days old (needed 5 days)
• lives (- to 3.0.2-1.2)
  • Migration status for lives (- to 3.0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lives/amd64 has unsatisfiable dependency
    • lives-plugins/amd64 has unsatisfiable dependency
    • lives/arm64 has unsatisfiable dependency
    • lives-plugins/arm64 has unsatisfiable dependency
    • lives/armel has unsatisfiable dependency
    • lives-plugins/armel has unsatisfiable dependency
    • lives/armhf has unsatisfiable dependency
    • lives-plugins/armhf has unsatisfiable dependency
    • lives/i386 has unsatisfiable dependency
    • lives-plugins/i386 has unsatisfiable dependency
    • lives/mips64el has unsatisfiable dependency
    • lives-plugins/mips64el has unsatisfiable dependency
    • lives/ppc64el has unsatisfiable dependency
    • lives-plugins/ppc64el has unsatisfiable dependency
    • lives/s390x has unsatisfiable dependency
    • lives-plugins/s390x has unsatisfiable dependency
    • Updating lives would introduce bugs in testing: #1013421, #1057362
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lives.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 637 days old (needed 5 days)
• android-platform-dalvik (- to 10.0.0+r36-4)
  • Migration status for android-platform-dalvik (- to 10.0.0+r36-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-platform-dalvik android-framework-23 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-dalvik.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 639 days old (needed 5 days)
• php-fpdf (- to 3:1.8.4.dfsg-1)
  • Migration status for php-fpdf (- to 3:1.8.4.dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fpdf would introduce bugs in testing: #1054829
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fpdf.html
    • Reproducible on i386 - info ♻
    • 640 days old (needed 5 days)
• i2masschroq (- to 0.4.54-1)
  • Migration status for i2masschroq (- to 0.4.54-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • i2masschroq/amd64 has unsatisfiable dependency
    • i2masschroq/arm64 has unsatisfiable dependency
    • i2masschroq/armel has unsatisfiable dependency
    • i2masschroq/armhf has unsatisfiable dependency
    • i2masschroq/i386 has unsatisfiable dependency
    • i2masschroq/mips64el has unsatisfiable dependency
    • i2masschroq/ppc64el has unsatisfiable dependency
    • i2masschroq/s390x has unsatisfiable dependency
    • Updating i2masschroq would introduce bugs in testing: #1028527
    • Not built on buildd: arch amd64 binaries uploaded by lopippo
    • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/i2masschroq.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 646 days old (needed 5 days)
• bully (- to 1.4.00-2)
  • Migration status for bully (- to 1.4.00-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bully aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bully.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 647 days old (needed 5 days)
• xrstools (- to 0.15.0+git20210910+c147919d-3)
  • Migration status for xrstools (- to 0.15.0+git20210910+c147919d-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-xrstools/amd64 has unsatisfiable dependency
    • Updating xrstools would introduce bugs in testing: #1022504, #1056895
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/x/xrstools.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • 650 days old (needed 5 days)
• node-node-forge (- to 1.3.0~dfsg-1)
  • Migration status for node-node-forge (- to 1.3.0~dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-forge would introduce bugs in testing: #1002861
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-forge.html
    • autopkgtest for node-node-forge/1.3.0~dfsg-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 655 days old (needed 5 days)
• obs-ptz (- to 0.10.4-1)
  • Migration status for obs-ptz (- to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-ptz would introduce bugs in testing: #1022361
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-ptz.html
    • 655 days old (needed 5 days)
• node-mermaid (- to 8.14.0+~cs11.4.14-1)
  • Migration status for node-mermaid (- to 8.14.0+~cs11.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mermaid would introduce bugs in testing: #1001549, #1022630, #1036688
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mermaid.html
    • autopkgtest for node-mermaid/8.14.0+~cs11.4.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 657 days old (needed 2 days)
• emacsql-sqlite3 (- to 1.0.2+git20220304.1.2113618-1)
  • Migration status for emacsql-sqlite3 (- to 1.0.2+git20220304.1.2113618-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacsql-sqlite3 would introduce bugs in testing: #1052967
    • autopkgtest for emacsql-sqlite3/1.0.2+git20220304.1.2113618-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacsql-sqlite3.html
    • Reproducible on i386 - info ♻
    • 665 days old (needed 5 days)
• qiskit-ibmq-provider (- to 0.4.6-4)
  • Migration status for qiskit-ibmq-provider (- to 0.4.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiskit-ibmq-provider would introduce bugs in testing: #1025181
    • autopkgtest for qiskit-ibmq-provider/0.4.6-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): qiskit-ibmq-provider qiskit-terra
    • Depends: qiskit-ibmq-provider qiskit-terra
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiskit-ibmq-provider.html
    • 665 days old (needed 5 days)
• qiskit-terra (- to 0.12.0-4)
  • Migration status for qiskit-terra (- to 0.12.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiskit-terra would introduce bugs in testing: #1027203, #1056878
    • autopkgtest for qiskit-terra/0.12.0-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiskit-terra.html
    • 665 days old (needed 5 days)
• aplpy (- to 2.1.0-1)
  • Migration status for aplpy (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aplpy would introduce bugs in testing: #1056227
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aplpy.html
    • autopkgtest for aplpy/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 667 days old (needed 2 days)
• rust-weedle (- to 0.12.0-2)
  • Migration status for rust-weedle (- to 0.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-weedle would introduce bugs in testing: #1007026
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-weedle.html
    • autopkgtest for rust-weedle/0.12.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 670 days old (needed 2 days)
• gm-assistant (- to 1.2.4-1)
  • Migration status for gm-assistant (- to 1.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gm-assistant poco (not considered)
    • Depends: gm-assistant poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gm-assistant.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 675 days old (needed 5 days)
• notcurses (- to 3.0.7+dfsg.1-1)
  • Migration status for notcurses (- to 3.0.7+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notcurses would introduce bugs in testing: #1001661, #1015747
    • autopkgtest for notcurses/3.0.7+dfsg.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 685 days old (needed 5 days)
• thin-provisioning-tools (- to 0.9.0-2)
  • Migration status for thin-provisioning-tools (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating thin-provisioning-tools would introduce bugs in testing: #1041089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thin-provisioning-tools.html
    • Reproducible on i386 - info ♻
    • 687 days old (needed 5 days)
• freeart (- to 3.3.0+ds1-3)
  • Migration status for freeart (- to 3.3.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freeart/amd64 has unsatisfiable dependency
    • python3-freeart/arm64 has unsatisfiable dependency
    • python3-freeart/armel has unsatisfiable dependency
    • python3-freeart/armhf has unsatisfiable dependency
    • python3-freeart/i386 has unsatisfiable dependency
    • python3-freeart/mips64el has unsatisfiable dependency
    • python3-freeart/ppc64el has unsatisfiable dependency
    • Updating freeart would introduce bugs in testing: #1013606, #1056801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/freeart.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 689 days old (needed 5 days)
• bqplot (- to 0.12.32-2)
  • Migration status for bqplot (- to 0.12.32-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bqplot traittypes (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bqplot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 690 days old (needed 5 days)
• gsmartcontrol (- to 1.1.4-1)
  • Migration status for gsmartcontrol (- to 1.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gsmartcontrol would introduce bugs in testing: #1000074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsmartcontrol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 692 days old (needed 5 days)
• scala-mode-el (- to 1:1.1.0-3)
  • Migration status for scala-mode-el (- to 1:1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scala-mode-el would introduce bugs in testing: #1052917
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-mode-el.html
    • autopkgtest for scala-mode-el/1:1.1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 692 days old (needed 2 days)
• node-devtools-protocol (- to 0.0.801017-1)
  • Migration status for node-devtools-protocol (- to 0.0.801017-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-devtools-protocol.html
    • autopkgtest for node-devtools-protocol/0.0.801017-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 693 days old (needed 5 days)
• node-functional.js (- to 0.8.0-1)
  • Migration status for node-functional.js (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-functional.js would introduce bugs in testing: #1014605
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-functional.js.html
    • autopkgtest for node-functional.js/0.8.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 693 days old (needed 5 days)
• node-grunt-timer (- to 0.6.0-1)
  • Migration status for node-grunt-timer (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-grunt-timer node-functional.js
    • Depends: node-grunt-timer node-functional.js
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-grunt-timer.html
    • autopkgtest for node-grunt-timer/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 693 days old (needed 2 days)
• guacamole-server (- to 1.3.0-1.1)
  • Migration status for guacamole-server (- to 1.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guacamole-server would introduce bugs in testing: #1005154
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guacamole-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 698 days old (needed 5 days)
• asterisk-flite (- to 3.0-4)
  • Migration status for asterisk-flite (- to 3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): asterisk-flite asterisk (not considered)
    • Depends: asterisk-flite asterisk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-flite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 700 days old (needed 5 days)
• clamfs (- to 1.2.0-2.1)
  • Migration status for clamfs (- to 1.2.0-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): clamfs poco (not considered)
    • Depends: clamfs poco (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clamfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 702 days old (needed 5 days)
• libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.1)
  • Migration status for libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsynthesis would introduce bugs in testing: #1000047
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsynthesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 702 days old (needed 5 days)
• dioptas (- to 0.5.2-4)
  • Migration status for dioptas (- to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dioptas would introduce bugs in testing: #1056798
    • Build-Depends(-Arch): dioptas extra-data
    • Build-Depends(-Arch): dioptas pyfai
    • Depends: dioptas extra-data
    • Depends: dioptas pyfai
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dioptas.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 704 days old (needed 5 days)
• extra-data (- to 1.7.0-5)
  • Migration status for extra-data (- to 1.7.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): extra-data python-xarray (not considered)
    • Depends: extra-data python-xarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extra-data.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 704 days old (needed 5 days)
• tomogui (- to 0.3.1-2)
  • Migration status for tomogui (- to 0.3.1-2): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tomogui.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 704 days old (needed 5 days)
• python-pyknon (- to 1.2-5)
  • Migration status for python-pyknon (- to 1.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyknon would introduce bugs in testing: #1056496, #1058445
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyknon.html
    • autopkgtest for python-pyknon/1.2-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 709 days old (needed 2 days)
• rust-proc-quote (- to 0.4.0-1)
  • Migration status for rust-proc-quote (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-proc-quote/0.4.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-quote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 709 days old (needed 5 days)
• mysqmail (- to 0.4.9-10.3)
  • Migration status for mysqmail (- to 0.4.9-10.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mysqmail courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysqmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 710 days old (needed 5 days)
• fwbuilder (- to 5.3.7-5)
  • Migration status for fwbuilder (- to 5.3.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fwbuilder would introduce bugs in testing: #1049951
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fwbuilder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 712 days old (needed 5 days)
• moviepy (- to 1.0.3-2)
  • Migration status for moviepy (- to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating moviepy would introduce bugs in testing: #1004642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moviepy.html
    • 712 days old (needed 5 days)
• shadowsocks-v2ray-plugin (- to 1.3.1-4)
  • Migration status for shadowsocks-v2ray-plugin (- to 1.3.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: shadowsocks-v2ray-plugin shadowsocks-libev (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shadowsocks-v2ray-plugin.html
    • autopkgtest for shadowsocks-v2ray-plugin/1.3.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 717 days old (needed 2 days)
• fbtftp (- to 0.5-2)
  • Migration status for fbtftp (- to 0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fbtftp would introduce bugs in testing: #1056245
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbtftp.html
    • autopkgtest for fbtftp/0.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 718 days old (needed 2 days)
• imdbpy (- to 2021.04.18-3)
  • Migration status for imdbpy (- to 2021.04.18-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating imdbpy would introduce bugs in testing: #1017747
    • autopkgtest for imdbpy/2021.04.18-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imdbpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 718 days old (needed 5 days)
• xcb (- to 2.4-8)
  • Migration status for xcb (- to 2.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcb would introduce bugs in testing: #1050607
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 718 days old (needed 5 days)
• libpam-ssh (- to 2.3+ds-6)
  • Migration status for libpam-ssh (- to 2.3+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-ssh would introduce bugs in testing: #994992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-ssh.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 723 days old (needed 5 days)
• growlight (- to 1.2.38-5)
  • Migration status for growlight (- to 1.2.38-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): growlight notcurses (not considered)
    • Depends: growlight notcurses (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/growlight.html
    • autopkgtest for growlight/1.2.38-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 725 days old (needed 2 days)
• massivethreads (- to 1.00-4)
  • Migration status for massivethreads (- to 1.00-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating massivethreads would introduce bugs in testing: #1014566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massivethreads.html
    • 728 days old (needed 5 days)
• rust-wasm-bindgen-webidl (- to 0.2.75-1)
  • Migration status for rust-wasm-bindgen-webidl (- to 0.2.75-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-wasm-bindgen-webidl-dev/amd64 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/arm64 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/armel has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/armhf has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/i386 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/mips64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/ppc64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/s390x has unsatisfiable dependency
    • Updating rust-wasm-bindgen-webidl would introduce bugs in testing: #1035417
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on amd64: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on amd64: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on arm64: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on arm64: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armel: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armel: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armhf: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armhf: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on i386: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on i386: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mips64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mips64el: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on ppc64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on ppc64el: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on s390x: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on s390x: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/amd64
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/arm64
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/armel
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/armhf
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/i386
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/mips64el
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/ppc64el
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/s390x
    • Build-Depends(-Arch): rust-wasm-bindgen-webidl rust-weedle
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-wasm-bindgen-webidl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 728 days old (needed 5 days)
• golang-github-go-redis-redis (- to 6.15.0-2)
  • Migration status for golang-github-go-redis-redis (- to 6.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-go-redis-redis would introduce bugs in testing: #985011
    • autopkgtest for golang-github-go-redis-redis/blocked-on-ci-infra: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-redis-redis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 729 days old (needed 5 days)
• mlton (- to 20210117+dfsg-3)
  • Migration status for mlton (- to 20210117+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlton would introduce bugs in testing: #917644, #998156
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch arm64 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch armel binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch armhf binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch i386 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch mips64el binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch s390x binaries uploaded by ryanakca@kubuntu.org
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlton.html
    • Reproducible on amd64 - info ♻
    • 731 days old (needed 5 days)
• emacs-lsp-haskell (- to 1.0.20211214-1)
  • Migration status for emacs-lsp-haskell (- to 1.0.20211214-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: emacs-lsp-haskell lsp-mode (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lsp-haskell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 732 days old (needed 5 days)
• emacs-lsp-ui (- to 8.0.0-1)
  • Migration status for emacs-lsp-ui (- to 8.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: emacs-lsp-ui lsp-mode (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lsp-ui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 734 days old (needed 5 days)
• tiledarray (- to 1.0.0-1)
  • Migration status for tiledarray (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tiledarray would introduce bugs in testing: #1050355
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): tiledarray btas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 734 days old (needed 5 days)
• mlucas (- to 20.1.1-1)
  • Migration status for mlucas (- to 20.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlucas would introduce bugs in testing: #1013910, #1014547, #1027776
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlucas.html
    • Reproducible on amd64 - info ♻
    • 735 days old (needed 5 days)
• xtide (- to 2.15.2-1.1)
  • Migration status for xtide (- to 2.15.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xtide would introduce bugs in testing: #1026439
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtide.html
    • 738 days old (needed 5 days)
• zmodemjs (- to 0.1.10+dfsg-2)
  • Migration status for zmodemjs (- to 0.1.10+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zmodemjs would introduce bugs in testing: #1005454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zmodemjs.html
    • 738 days old (needed 5 days)
• pplacer (- to 1.1~alpha19-6)
  • Migration status for pplacer (- to 1.1~alpha19-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pplacer would introduce bugs in testing: #1024889
    • pplacer unsatisfiable Build-Depends(-Arch) on amd64: libmcl-ocaml-dev
    • pplacer unsatisfiable Build-Depends(-Arch) on arm64: libmcl-ocaml-dev
    • pplacer unsatisfiable Build-Depends(-Arch) on ppc64el: libmcl-ocaml-dev
    • pplacer unsatisfiable Build-Depends(-Arch) on s390x: libmcl-ocaml-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplacer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 746 days old (needed 5 days)
• kore (- to 4.1.0-6)
  • Migration status for kore (- to 4.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kore would introduce bugs in testing: #1033711
    • autopkgtest for kore/4.1.0-6: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 749 days old (needed 5 days)
• django-dynamic-preferences (- to 1.10.1-1)
  • Migration status for django-dynamic-preferences (- to 1.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
    • Depends: django-dynamic-preferences python-persisting-theory
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-dynamic-preferences.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 750 days old (needed 5 days)
• pixmap (- to 2.6.6-1)
  • Migration status for pixmap (- to 2.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pixmap would introduce bugs in testing: #1054698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pixmap.html
    • Reproducible on i386 - info ♻
    • 751 days old (needed 5 days)
• mate-optimus (- to 21.04.0-1)
  • Migration status for mate-optimus (- to 21.04.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mate-optimus would introduce bugs in testing: #987819
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-optimus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 754 days old (needed 5 days)
• behave (- to 1.2.6-4)
  • Migration status for behave (- to 1.2.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating behave would introduce bugs in testing: #1042610, #1054974
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/behave.html
    • autopkgtest for behave/1.2.6-4: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 758 days old (needed 5 days)
• libguess (- to 1.2-5)
  • Migration status for libguess (- to 1.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libguess gauche (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libguess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 761 days old (needed 5 days)
• epigrass (- to 3.0.3+dfsg-2)
  • Migration status for epigrass (- to 3.0.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epigrass would introduce bugs in testing: #995966, #998265
    • autopkgtest for epigrass/3.0.3+dfsg-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epigrass.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 762 days old (needed 5 days)
• radare2 (- to 5.5.0+dfsg-1)
  • Migration status for radare2 (- to 5.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating radare2 would introduce bugs in testing: #1014478, #950372
    • Build-Depends(-Arch): radare2 freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 767 days old (needed 5 days)
• poco (- to 1.11.0-3)
  • Migration status for poco (- to 1.11.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating poco would introduce bugs in testing: #999989
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poco.html
    • 771 days old (needed 5 days)
• netopeer2 (- to 2.0.35-1)
  • Migration status for netopeer2 (- to 2.0.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netopeer2 would introduce bugs in testing: #1001796, #1035287, #981761
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/netopeer2.html
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): netopeer2 sysrepo
    • Depends: netopeer2 sysrepo
  • Additional info:
    • 772 days old (needed 5 days)
• php-sabredav (- to 1.8.12-10)
  • Migration status for php-sabredav (- to 1.8.12-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-sabredav php-sabre-vobject (not considered)
    • Depends: php-sabredav php-sabre-vobject (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
    • autopkgtest for php-sabredav/1.8.12-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 772 days old (needed 2 days)
• ruby-diaspora-federation (- to 0.2.7-1)
  • Migration status for ruby-diaspora-federation (- to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-diaspora-federation would introduce bugs in testing: #1006031
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-diaspora-federation.html
    • autopkgtest for ruby-diaspora-federation/0.2.7-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 772 days old (needed 5 days)
• ruby-diaspora-federation-rails (- to 0.2.7-1)
  • Migration status for ruby-diaspora-federation-rails (- to 0.2.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-diaspora-federation-rails ruby-diaspora-federation (not considered)
    • Depends: ruby-diaspora-federation-rails ruby-diaspora-federation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-diaspora-federation-rails.html
    • autopkgtest for ruby-diaspora-federation-rails/0.2.7-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 772 days old (needed 5 days)
• sysrepo (- to 2.0.53-6)
  • Migration status for sysrepo (- to 2.0.53-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sysrepo would introduce bugs in testing: #1037068, #996847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysrepo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 772 days old (needed 5 days)
• paper-css (- to 0.4.1+ds-1)
  • Migration status for paper-css (- to 0.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paper-css.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 776 days old (needed 5 days)
• node-mongodb (- to 3.6.4+~cs11.13.19-2)
  • Migration status for node-mongodb (- to 3.6.4+~cs11.13.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mongodb would introduce bugs in testing: #1033817
    • autopkgtest for node-mongodb/3.6.4+~cs11.13.19-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 777 days old (needed 5 days)
• python-intbitset (- to 2.3.0-3.2)
  • Migration status for python-intbitset (- to 2.3.0-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-intbitset would introduce bugs in testing: #1042615, #1056860
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-intbitset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 777 days old (needed 5 days)
• python-rocksdb (- to 0.8.0~rc3-2)
  • Migration status for python-rocksdb (- to 0.8.0~rc3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rocksdb/amd64 has unsatisfiable dependency
    • python3-rocksdb/arm64 has unsatisfiable dependency
    • python3-rocksdb/i386 has unsatisfiable dependency
    • python3-rocksdb/mips64el has unsatisfiable dependency
    • python3-rocksdb/ppc64el has unsatisfiable dependency
    • python3-rocksdb/s390x has unsatisfiable dependency
    • Updating python-rocksdb would introduce bugs in testing: #1012074, #1056870
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-rocksdb.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 777 days old (needed 5 days)
• jquery-datetimepicker (- to 2.5.20+ds-1)
  • Migration status for jquery-datetimepicker (- to 2.5.20+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-datetimepicker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 778 days old (needed 5 days)
• jquery-sortablejs (- to 1.0.0-1)
  • Migration status for jquery-sortablejs (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-sortablejs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 778 days old (needed 5 days)
• materialize (- to 1.1.0~alpha+ds-1)
  • Migration status for materialize (- to 1.1.0~alpha+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materialize would introduce bugs in testing: #1012320
    • materialize unsatisfiable Build-Depends(-Arch) on amd64: libjs-anime
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materialize.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 778 days old (needed 5 days)
• python-dmidecode (- to 3.12.2-13)
  • Migration status for python-dmidecode (- to 3.12.2-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dmidecode would introduce bugs in testing: #1054813
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dmidecode.html
    • 778 days old (needed 5 days)
• syncevolution (- to 2.0.0-3)
  • Migration status for syncevolution (- to 2.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): syncevolution libsynthesis (not considered)
    • Depends: syncevolution libsynthesis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncevolution.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 778 days old (needed 5 days)
• node-solid-keychain (- to 0.1.3-3.1)
  • Migration status for node-solid-keychain (- to 0.1.3-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-solid-keychain/0.1.3-3.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): node-solid-keychain node-trust-webcrypto
    • Depends: node-solid-keychain node-trust-webcrypto
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-solid-keychain.html
    • 782 days old (needed 5 days)
• cpl-plugin-xshoo (- to 3.5.3+dfsg-1)
  • Migration status for cpl-plugin-xshoo (- to 3.5.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-xshoo would introduce bugs in testing: #1035786
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-xshoo.html
    • autopkgtest for cpl-plugin-xshoo/3.5.3+dfsg-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 785 days old (needed 5 days)
• ruby-roxml (- to 4.2.0-1)
  • Migration status for ruby-roxml (- to 4.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-roxml would introduce bugs in testing: #1050580
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-roxml.html
    • autopkgtest for ruby-roxml/4.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 786 days old (needed 2 days)
• golang-github-intel-go-cpuid (- to 0.0~git20210602.5747e5c-2)
  • Migration status for golang-github-intel-go-cpuid (- to 0.0~git20210602.5747e5c-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-intel-go-cpuid/0.0~git20210602.5747e5c-2: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-intel-go-cpuid.html
    • Reproducible on amd64 - info ♻
    • 792 days old (needed 5 days)
• mbdyn (- to 1.7.3-1)
  • Migration status for mbdyn (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mbdyn would introduce bugs in testing: #999554
    • Not built on buildd: arch amd64 binaries uploaded by andrius.merkys@gmail.com
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbdyn.html
    • 792 days old (needed 5 days)
• python-calendarweek (- to 0.5.0-1)
  • Migration status for python-calendarweek (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendarweek.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 792 days old (needed 5 days)
• django-dbbackup (- to 3.3.0-1)
  • Migration status for django-dbbackup (- to 3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-dbbackup.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 795 days old (needed 5 days)
• django-favicon-plus-reloaded (- to 1.1.3-1)
  • Migration status for django-favicon-plus-reloaded (- to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-favicon-plus-reloaded.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 795 days old (needed 5 days)
• django-otp-yubikey (- to 1.0.0.post1-1)
  • Migration status for django-otp-yubikey (- to 1.0.0.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-otp-yubikey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 795 days old (needed 5 days)
• django-titofisto (- to 0.1.2.post1-1)
  • Migration status for django-titofisto (- to 0.1.2.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-titofisto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 795 days old (needed 5 days)
• django-widget-tweaks (- to 1.4.8-1)
  • Migration status for django-widget-tweaks (- to 1.4.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-widget-tweaks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 795 days old (needed 5 days)
• cpl-plugin-fors (- to 5.5.7+dfsg-2)
  • Migration status for cpl-plugin-fors (- to 5.5.7+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-fors would introduce bugs in testing: #1035696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-fors.html
    • autopkgtest for cpl-plugin-fors/5.5.7+dfsg-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 796 days old (needed 5 days)
• python-sshoot (- to 1.4.2-2)
  • Migration status for python-sshoot (- to 1.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-sshoot would introduce bugs in testing: #1013601
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sshoot.html
    • autopkgtest for python-sshoot/1.4.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 797 days old (needed 2 days)
• vast (- to 2021.05.27-8)
  • Migration status for vast (- to 2021.05.27-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vast/amd64 has unsatisfiable dependency
    • vast/arm64 has unsatisfiable dependency
    • vast/ppc64el has unsatisfiable dependency
    • vast/s390x has unsatisfiable dependency
    • Updating vast would introduce bugs in testing: #1001527
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vast.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 798 days old (needed 5 days)
• ganglia (- to 3.7.2-6)
  • Migration status for ganglia (- to 3.7.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganglia would introduce bugs in testing: #1000041
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia.html
    • autopkgtest for ganglia/3.7.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 799 days old (needed 2 days)
• golang-github-gambol99-go-marathon (- to 0.7.1-1)
  • Migration status for golang-github-gambol99-go-marathon (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alois@micard.lu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gambol99-go-marathon.html
    • autopkgtest for golang-github-gambol99-go-marathon/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 800 days old (needed 2 days)
• python-gear (- to 0.5.8-6)
  • Migration status for python-gear (- to 0.5.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-gear would introduce bugs in testing: #1002430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gear.html
    • 801 days old (needed 5 days)
• laminar (- to 1.1-1)
  • Migration status for laminar (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating laminar would introduce bugs in testing: #1019455
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/laminar.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 804 days old (needed 5 days)
• toxic (- to 0.11.1-3)
  • Migration status for toxic (- to 0.11.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): toxic libtoxcore (not considered)
    • Depends: toxic libtoxcore (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toxic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 812 days old (needed 5 days)
• grok (- to 1.20110708.1-7)
  • Migration status for grok (- to 1.20110708.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grok would introduce bugs in testing: #1000065
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • autopkgtest for grok/1.20110708.1-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 814 days old (needed 2 days)
• obs-websocket (- to 4.9.0-2)
  • Migration status for obs-websocket (- to 4.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-websocket would introduce bugs in testing: #1006040
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-websocket.html
    • 814 days old (needed 5 days)
• prads (- to 0.3.3-7)
  • Migration status for prads (- to 0.3.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prads would introduce bugs in testing: #999984
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • autopkgtest for prads/0.3.3-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 814 days old (needed 2 days)
• gabedit (- to 2.5.1+ds-1)
  • Migration status for gabedit (- to 2.5.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gabedit gtkglext (not considered)
    • Depends: gabedit gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gabedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 815 days old (needed 5 days)
• upx-ucl (- to 3.96-3)
  • Migration status for upx-ucl (- to 3.96-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating upx-ucl would introduce bugs in testing: #1031874, #1033258
    • autopkgtest for upx-ucl/3.96-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/upx-ucl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 815 days old (needed 5 days)
• php-webimpress-safe-writer (- to 2.2.0-1)
  • Migration status for php-webimpress-safe-writer (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-webimpress-safe-writer would introduce bugs in testing: #981233
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-webimpress-safe-writer.html
    • autopkgtest for php-webimpress-safe-writer/2.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 816 days old (needed 2 days)
• info-beamer (- to 1.0~pre3+dfsg-0.2)
  • Migration status for info-beamer (- to 1.0~pre3+dfsg-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • info-beamer/amd64 has unsatisfiable dependency
    • info-beamer/arm64 has unsatisfiable dependency
    • info-beamer/armel has unsatisfiable dependency
    • info-beamer/armhf has unsatisfiable dependency
    • info-beamer/i386 has unsatisfiable dependency
    • info-beamer/mips64el has unsatisfiable dependency
    • info-beamer/ppc64el has unsatisfiable dependency
    • info-beamer/s390x has unsatisfiable dependency
    • Updating info-beamer would introduce bugs in testing: #1004823
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/info-beamer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 818 days old (needed 5 days)
• python-persisting-theory (- to 0.2.1-1)
  • Migration status for python-persisting-theory (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-persisting-theory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 818 days old (needed 5 days)
• sphinx-rst-builder (- to 0.0.3-3)
  • Migration status for sphinx-rst-builder (- to 0.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sphinx-rst-builder would introduce bugs in testing: #1042587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-rst-builder.html
    • Reproducible on i386 - info ♻
    • 820 days old (needed 5 days)
• anfo (- to 0.98-9)
  • Migration status for anfo (- to 0.98-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • anfo/amd64 has unsatisfiable dependency
    • libanfo0/amd64 has unsatisfiable dependency
    • anfo/arm64 has unsatisfiable dependency
    • libanfo0/arm64 has unsatisfiable dependency
    • anfo/armel has unsatisfiable dependency
    • libanfo0/armel has unsatisfiable dependency
    • anfo/armhf has unsatisfiable dependency
    • libanfo0/armhf has unsatisfiable dependency
    • anfo/i386 has unsatisfiable dependency
    • libanfo0/i386 has unsatisfiable dependency
    • anfo/mips64el has unsatisfiable dependency
    • libanfo0/mips64el has unsatisfiable dependency
    • anfo/ppc64el has unsatisfiable dependency
    • libanfo0/ppc64el has unsatisfiable dependency
    • anfo/s390x has unsatisfiable dependency
    • libanfo0/s390x has unsatisfiable dependency
    • Updating anfo would introduce bugs in testing: #1012893
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/anfo.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 823 days old (needed 5 days)
• nvchecker (- to 2.5-1)
  • Migration status for nvchecker (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nvchecker/2.5-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvchecker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 825 days old (needed 5 days)
• basemap (- to 1.2.2+dfsg-2)
  • Migration status for basemap (- to 1.2.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mpltoolkits.basemap/amd64 has unsatisfiable dependency
    • python3-mpltoolkits.basemap/arm64 has unsatisfiable dependency
    • python3-mpltoolkits.basemap/armel has unsatisfiable dependency
    • python3-mpltoolkits.basemap/armhf has unsatisfiable dependency
    • python3-mpltoolkits.basemap/i386 has unsatisfiable dependency
    • python3-mpltoolkits.basemap/mips64el has unsatisfiable dependency
    • python3-mpltoolkits.basemap/ppc64el has unsatisfiable dependency
    • python3-mpltoolkits.basemap/s390x has unsatisfiable dependency
    • Updating basemap would introduce bugs in testing: #1009424, #1056789
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/basemap.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 828 days old (needed 5 days)
• ggcov (- to 0.10-4)
  • Migration status for ggcov (- to 0.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ggcov would introduce bugs in testing: #1020263
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ggcov.html
    • 829 days old (needed 5 days)
• vim-scripts (- to 20210124.2)
  • Migration status for vim-scripts (- to 20210124.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-scripts would introduce bugs in testing: #1051063
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-scripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 833 days old (needed 5 days)
• blastem (- to 0.6.3.4-1)
  • Migration status for blastem (- to 0.6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating blastem would introduce bugs in testing: #1054661
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blastem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 834 days old (needed 5 days)
• python-miio (- to 0.5.0.1-2)
  • Migration status for python-miio (- to 0.5.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-miio would introduce bugs in testing: #1042325
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-miio.html
    • 843 days old (needed 5 days)
• discodos (- to 1.0~rc2-2)
  • Migration status for discodos (- to 1.0~rc2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating discodos would introduce bugs in testing: #966115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/discodos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 844 days old (needed 5 days)
• mdk3 (- to 6.0-8)
  • Migration status for mdk3 (- to 6.0-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mdk3 aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdk3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 846 days old (needed 5 days)
• mdk4 (- to 4.2-3)
  • Migration status for mdk4 (- to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mdk4 aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdk4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 846 days old (needed 5 days)
• shotdetect (- to 1.0.86-6)
  • Migration status for shotdetect (- to 1.0.86-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shotdetect/amd64 has unsatisfiable dependency
    • shotdetect/arm64 has unsatisfiable dependency
    • shotdetect/armel has unsatisfiable dependency
    • shotdetect/armhf has unsatisfiable dependency
    • shotdetect/i386 has unsatisfiable dependency
    • shotdetect/mips64el has unsatisfiable dependency
    • shotdetect/ppc64el has unsatisfiable dependency
    • shotdetect/s390x has unsatisfiable dependency
    • Updating shotdetect would introduce bugs in testing: #1004719
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/shotdetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 847 days old (needed 5 days)
• backupchecker (- to 1.7-3)
  • Migration status for backupchecker (- to 1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backupchecker would introduce bugs in testing: #1002409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backupchecker.html
    • 850 days old (needed 5 days)
• snort (- to 2.9.15.1-6)
  • Migration status for snort (- to 2.9.15.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • snort-common-libraries/ppc64el has unsatisfiable dependency
    • Updating snort would introduce bugs in testing: #1019230, #1021276, #999956
    • snort unsatisfiable Build-Depends(-Arch) on ppc64el: libluajit-5.1-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snort.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 853 days old (needed 5 days)
• pysmbc (- to 1.0.23-2)
  • Migration status for pysmbc (- to 1.0.23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pysmbc would introduce bugs in testing: #1055560
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysmbc.html
    • autopkgtest for pysmbc/1.0.23-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 854 days old (needed 5 days)
• eclipse-tracecompass (- to 7.0.0+repack-1)
  • Migration status for eclipse-tracecompass (- to 7.0.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eclipse-tracecompass/amd64 has unsatisfiable dependency
    • eclipse-tracecompass/arm64 has unsatisfiable dependency
    • Updating eclipse-tracecompass would introduce bugs in testing: #1010983, #1035594
    • eclipse-tracecompass unsatisfiable Build-Depends(-Arch) on amd64: libequinox-p2-ui-sdk-java
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-cdt
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-remote
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/eclipse-tracecompass.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 859 days old (needed 5 days)
• gcc-9-doc (- to 9.4.0-1)
  • Migration status for gcc-9-doc (- to 9.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-doc would introduce bugs in testing: #995061
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 866 days old (needed 5 days)
• libglade2 (- to 1:2.6.4-2.4)
  • Migration status for libglade2 (- to 1:2.6.4-2.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libglade2 would introduce bugs in testing: #895517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libglade2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 866 days old (needed 5 days)
• onedrivesdk (- to 1.1.8-3)
  • Migration status for onedrivesdk (- to 1.1.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating onedrivesdk would introduce bugs in testing: #1025016
    • autopkgtest for onedrivesdk/1.1.8-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onedrivesdk.html
    • 866 days old (needed 5 days)
• morty (- to 0.2.0-3)
  • Migration status for morty (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morty would introduce bugs in testing: #1052139
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morty.html
    • autopkgtest for morty/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 869 days old (needed 2 days)
• purify (- to 2.0.0-6)
  • Migration status for purify (- to 2.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpurify2.0/amd64 has unsatisfiable dependency
    • purify/amd64 has unsatisfiable dependency
    • libpurify2.0/arm64 has unsatisfiable dependency
    • purify/arm64 has unsatisfiable dependency
    • libpurify2.0/armel has unsatisfiable dependency
    • purify/armel has unsatisfiable dependency
    • libpurify2.0/armhf has unsatisfiable dependency
    • purify/armhf has unsatisfiable dependency
    • libpurify2.0/i386 has unsatisfiable dependency
    • purify/i386 has unsatisfiable dependency
    • libpurify2.0/ppc64el has unsatisfiable dependency
    • purify/ppc64el has unsatisfiable dependency
    • libpurify2.0/s390x has unsatisfiable dependency
    • purify/s390x has unsatisfiable dependency
    • Updating purify would introduce bugs in testing: #1001528
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/purify.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 875 days old (needed 5 days)
• libpam-tacplus (- to 1.3.8-2.1)
  • Migration status for libpam-tacplus (- to 1.3.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-tacplus would introduce bugs in testing: #1009966
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-tacplus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 887 days old (needed 5 days)
• ganglia-modules-linux (- to 1.3.6-5)
  • Migration status for ganglia-modules-linux (- to 1.3.6-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ganglia-modules-linux ganglia (not considered)
    • Depends: ganglia-modules-linux ganglia (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia-modules-linux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 903 days old (needed 5 days)
• qiskit-aer (- to 0.4.1-2)
  • Migration status for qiskit-aer (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-qiskit-aer/amd64 has unsatisfiable dependency
    • python3-qiskit-aer/arm64 has unsatisfiable dependency
    • python3-qiskit-aer/armhf has unsatisfiable dependency
    • python3-qiskit-aer/i386 has unsatisfiable dependency
    • python3-qiskit-aer/mips64el has unsatisfiable dependency
    • python3-qiskit-aer/ppc64el has unsatisfiable dependency
    • Updating qiskit-aer would introduce bugs in testing: #1027206, #1028896, #1056881
    • Build-Depends(-Arch): qiskit-aer qiskit-terra
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/qiskit-aer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 920 days old (needed 5 days)
• squid-deb-proxy (- to 0.8.15+nmu1)
  • Migration status for squid-deb-proxy (- to 0.8.15+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squid-deb-proxy would introduce bugs in testing: #932501, #999646
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squid-deb-proxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 933 days old (needed 5 days)
• autoradio (- to 3.4-4)
  • Migration status for autoradio (- to 3.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoradio would introduce bugs in testing: #1052737
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoradio.html
    • Reproducible on armhf - info ♻
    • 949 days old (needed 5 days)
• mialmpick (- to 0.2.15-2)
  • Migration status for mialmpick (- to 0.2.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mialmpick libglade2 (not considered)
    • Depends: mialmpick libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): mialmpick gtkglext
    • Depends: mialmpick gtkglext
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mialmpick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 949 days old (needed 5 days)
• diaspora-installer (- to 0.7.15.0+debian1)
  • Migration status for diaspora-installer (- to 0.7.15.0+debian1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating diaspora-installer would introduce bugs in testing: #1006547
    • autopkgtest for diaspora-installer/0.7.15.0+debian1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diaspora-installer.html
    • 953 days old (needed 5 days)
• slic3r (- to 1.3.0+dfsg1-5)
  • Migration status for slic3r (- to 1.3.0+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slic3r would introduce bugs in testing: #1034848
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 986 days old (needed 5 days)
• davs2 (- to 1.6-1)
  • Migration status for davs2 (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating davs2 would introduce bugs in testing: #1024722
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/davs2.html
    • New but not reproducible on amd64 - info ♻
    • 1000 days old (needed 5 days)
• xavs2 (- to 1.3-1)
  • Migration status for xavs2 (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xavs2 would introduce bugs in testing: #1024723
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xavs2.html
    • New but not reproducible on amd64 - info ♻
    • 1000 days old (needed 5 days)
• dstat (- to 0.7.4-6.1)
  • Migration status for dstat (- to 0.7.4-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dstat would introduce bugs in testing: #1034856
    • autopkgtest for dstat/0.7.4-6.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1004 days old (needed 5 days)
• spdx-licenses (- to 3.8+dfsg-3)
  • Migration status for spdx-licenses (- to 3.8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spdx-licenses would introduce bugs in testing: #975120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spdx-licenses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1005 days old (needed 5 days)
• mpdecimal (- to 2.5.1-2)
  • Migration status for mpdecimal (- to 2.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mpdecimal would introduce bugs in testing: #1013395
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpdecimal.html
    • 1018 days old (needed 5 days)
• gtkglext (- to 1.2.0-11)
  • Migration status for gtkglext (- to 1.2.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkglext would introduce bugs in testing: #1054392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkglext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1022 days old (needed 5 days)
• eiskaltdcpp (- to 2.4.2-1)
  • Migration status for eiskaltdcpp (- to 2.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eiskaltdcpp would introduce bugs in testing: #1000100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eiskaltdcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1040 days old (needed 5 days)
• enigmail (- to 2:2.2.4-0.3)
  • Migration status for enigmail (- to 2:2.2.4-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating enigmail would introduce bugs in testing: #1030186, #975926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enigmail.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • 1041 days old (needed 5 days)
• rust-rust-code-analysis-cli (- to 0.0.19-1)
  • Migration status for rust-rust-code-analysis-cli (- to 0.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rust-code-analysis-cli would introduce bugs in testing: #1017649
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-0.7+default-dev
    • Build-Depends(-Arch): rust-rust-code-analysis-cli rust-rust-code-analysis
    • Built-Using: rust-rust-code-analysis-cli rust-rust-code-analysis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis-cli.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1049 days old (needed 5 days)
• hotspot (- to 1.3.0-2)
  • Migration status for hotspot (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hotspot would introduce bugs in testing: #1025573
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hotspot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1050 days old (needed 5 days)
• libvma (- to 9.2.2-1)
  • Migration status for libvma (- to 9.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libvma would introduce bugs in testing: #1021852
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvma.html
    • 1050 days old (needed 5 days)
• utox (- to 0.18.1-1)
  • Migration status for utox (- to 0.18.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): utox libtoxcore (not considered)
    • Depends: utox libtoxcore (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utox.html
    • autopkgtest for utox/0.18.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1052 days old (needed 2 days)
• fonts-cascadia-code (- to 2102.03-1)
  • Migration status for fonts-cascadia-code (- to 2102.03-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-cascadia-code would introduce bugs in testing: #997317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-cascadia-code.html
    • 1054 days old (needed 5 days)
• php-facedetect (- to 1.1.0-19-g135c72a-2)
  • Migration status for php-facedetect (- to 1.1.0-19-g135c72a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-facedetect/amd64 has unsatisfiable dependency
    • php-facedetect/arm64 has unsatisfiable dependency
    • php-facedetect/armel has unsatisfiable dependency
    • php-facedetect/armhf has unsatisfiable dependency
    • php-facedetect/i386 has unsatisfiable dependency
    • php-facedetect/mips64el has unsatisfiable dependency
    • php-facedetect/ppc64el has unsatisfiable dependency
    • php-facedetect/s390x has unsatisfiable dependency
    • Updating php-facedetect would introduce bugs in testing: #1020977
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-facedetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1056 days old (needed 5 days)
• aiorwlock (- to 1.0.0-0.2)
  • Migration status for aiorwlock (- to 1.0.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiorwlock would introduce bugs in testing: #997106
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiorwlock.html
    • autopkgtest for aiorwlock/1.0.0-0.2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 1061 days old (needed 5 days)
• mydumper (- to 0.10.1-1)
  • Migration status for mydumper (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mydumper would introduce bugs in testing: #1000014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mydumper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1061 days old (needed 5 days)
• nattable (- to 2.0.0+dfsg-1)
  • Migration status for nattable (- to 2.0.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nattable eclipse-collections (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nattable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1062 days old (needed 5 days)
• zeek (- to 3.2.3+ds2-2)
  • Migration status for zeek (- to 3.2.3+ds2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • zeek/amd64 has unsatisfiable dependency
    • zeek/arm64 has unsatisfiable dependency
    • zeek/armel has unsatisfiable dependency
    • zeek/armhf has unsatisfiable dependency
    • zeek/i386 has unsatisfiable dependency
    • zeek/mips64el has unsatisfiable dependency
    • zeek/ppc64el has unsatisfiable dependency
    • zeek/s390x has unsatisfiable dependency
    • Updating zeek would introduce bugs in testing: #1002760
    • Build-Depends(-Arch): zeek broker
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/z/zeek.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1062 days old (needed 5 days)
• spyder-memory-profiler (- to 0.2.1-1)
  • Migration status for spyder-memory-profiler (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spyder-memory-profiler would introduce bugs in testing: #1035493
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-memory-profiler.html
    • autopkgtest for spyder-memory-profiler/0.2.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • 1063 days old (needed 5 days)
• performous-composer (- to 2.0+20181009-gitbeeea23-2.1)
  • Migration status for performous-composer (- to 2.0+20181009-gitbeeea23-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • performous-composer/amd64 has unsatisfiable dependency
    • performous-composer/arm64 has unsatisfiable dependency
    • performous-composer/armel has unsatisfiable dependency
    • performous-composer/armhf has unsatisfiable dependency
    • performous-composer/i386 has unsatisfiable dependency
    • performous-composer/mips64el has unsatisfiable dependency
    • performous-composer/ppc64el has unsatisfiable dependency
    • performous-composer/s390x has unsatisfiable dependency
    • Updating performous-composer would introduce bugs in testing: #1004816
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/performous-composer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1064 days old (needed 5 days)
• scmail (- to 1.3-4.1)
  • Migration status for scmail (- to 1.3-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scmail gauche (not considered)
    • Depends: scmail gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1064 days old (needed 5 days)
• ruby-upr (- to 0.3.0-3)
  • Migration status for ruby-upr (- to 0.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-upr would introduce bugs in testing: #1030689
    • autopkgtest for ruby-upr/0.3.0-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-upr ruby-moneta
    • Depends: ruby-upr ruby-moneta
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-upr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1065 days old (needed 5 days)
• apertium-kaz-tat (- to 0.2.1-1)
  • Migration status for apertium-kaz-tat (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-kaz-tat would introduce bugs in testing: #1005670
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-kaz-tat.html
    • 1066 days old (needed 5 days)
• apertium-sme-nob (- to 0.6.1+ds.1-2)
  • Migration status for apertium-sme-nob (- to 0.6.1+ds.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-sme-nob would introduce bugs in testing: #1008348
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-sme-nob.html
    • 1066 days old (needed 5 days)
• plaso (- to 20201007-2)
  • Migration status for plaso (- to 20201007-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): plaso dfvfs (not considered)
    • Depends: plaso dfvfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plaso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1066 days old (needed 5 days)
• rust-libnotcurses-sys (- to 2.1.8-1)
  • Migration status for rust-libnotcurses-sys (- to 2.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-libnotcurses-sys would introduce bugs in testing: #985813
    • autopkgtest for rust-libnotcurses-sys/blocked-on-ci-infra: amd64: Regression or new test ♻
    • Build-Depends(-Arch): rust-libnotcurses-sys notcurses
    • Depends: rust-libnotcurses-sys notcurses
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libnotcurses-sys.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 1066 days old (needed 5 days)
• cadvisor (- to 0.38.7+ds1-2)
  • Migration status for cadvisor (- to 0.38.7+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cadvisor would introduce bugs in testing: #1005678, #1027994
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/armel has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/armel has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/armhf has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/armhf has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/i386 has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/i386 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • cadvisor/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/s390x has unsatisfiable Built-Using on golang-github-willf-bitset 1.1.11-1
    • cadvisor/s390x has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadvisor.html
    • autopkgtest for cadvisor/0.38.7+ds1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1067 days old (needed 2 days)
• picprog (- to 1.9.1-5)
  • Migration status for picprog (- to 1.9.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating picprog would introduce bugs in testing: #946039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picprog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1067 days old (needed 5 days)
• golang-github-alicebob-miniredis (- to 2.2.1-5)
  • Migration status for golang-github-alicebob-miniredis (- to 2.2.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Depends: golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alicebob-miniredis.html
    • autopkgtest for golang-github-alicebob-miniredis/2.2.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1068 days old (needed 2 days)
• actdiag (- to 2.0.0+dfsg-1)
  • Migration status for actdiag (- to 2.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating actdiag would introduce bugs in testing: #1042159
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/actdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1069 days old (needed 5 days)
• pantomime-clojure (- to 2.1.0+dfsg-2)
  • Migration status for pantomime-clojure (- to 2.1.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pantomime-clojure tika (not considered)
    • Depends: pantomime-clojure tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantomime-clojure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1069 days old (needed 5 days)
• sphinxcontrib-actdiag (- to 2.0.0-1)
  • Migration status for sphinxcontrib-actdiag (- to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sphinxcontrib-actdiag actdiag (not considered)
    • Depends: sphinxcontrib-actdiag actdiag (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-actdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1069 days old (needed 5 days)
• sphinxcontrib-nwdiag (- to 2.0.0-1)
  • Migration status for sphinxcontrib-nwdiag (- to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sphinxcontrib-nwdiag nwdiag (not considered)
    • Depends: sphinxcontrib-nwdiag nwdiag (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-nwdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1069 days old (needed 5 days)
• tika (- to 1.22-2)
  • Migration status for tika (- to 1.22-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tika would introduce bugs in testing: #1011492
    • Build-Depends(-Arch): tika vorbis-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tika.html
    • 1069 days old (needed 5 days)
• backdoor-factory (- to 3.4.2+dfsg-5)
  • Migration status for backdoor-factory (- to 3.4.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backdoor-factory would introduce bugs in testing: #1027037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backdoor-factory.html
    • autopkgtest for backdoor-factory/3.4.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1070 days old (needed 2 days)
• pympler (- to 0.9+dfsg1-2)
  • Migration status for pympler (- to 0.9+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympler would introduce bugs in testing: #1002173
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
    • autopkgtest for pympler/0.9+dfsg1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 1072 days old (needed 5 days)
• dfvfs (- to 20201219-1)
  • Migration status for dfvfs (- to 20201219-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dfvfs would introduce bugs in testing: #998527
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dfvfs.html
    • 1074 days old (needed 5 days)
• js2-mode (- to 0~20201220-1)
  • Migration status for js2-mode (- to 0~20201220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating js2-mode would introduce bugs in testing: #1052865
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/js2-mode.html
    • Reproducible on i386 - info ♻
    • 1074 days old (needed 5 days)
• libscout (- to 2.3.2-3)
  • Migration status for libscout (- to 2.3.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libscout android-framework-23 (not considered)
    • Depends: libscout android-framework-23 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libscout.html
    • autopkgtest for libscout/2.3.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1074 days old (needed 2 days)
• emacs-db (- to 0.0.6+git20140421.b3a423f-3)
  • Migration status for emacs-db (- to 0.0.6+git20140421.b3a423f-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): emacs-db emacs-kv (not considered)
    • Depends: emacs-db emacs-kv (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-db.html
    • autopkgtest for emacs-db/0.0.6+git20140421.b3a423f-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1075 days old (needed 2 days)
• emacs-kv (- to 0.0.19+git20140108.7211484-4)
  • Migration status for emacs-kv (- to 0.0.19+git20140108.7211484-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-kv would introduce bugs in testing: #1052933
    • autopkgtest for emacs-kv/0.0.19+git20140108.7211484-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-kv.html
    • Reproducible on i386 - info ♻
    • 1075 days old (needed 5 days)
• sagan (- to 1.2.0-1.2)
  • Migration status for sagan (- to 1.2.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagan would introduce bugs in testing: #999968
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagan.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1075 days old (needed 5 days)
• vg (- to 1.30.0+ds-1)
  • Migration status for vg (- to 1.30.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vg/amd64 has unsatisfiable dependency
    • vg/mips64el has unsatisfiable dependency
    • Updating vg would introduce bugs in testing: #1013061
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 1075 days old (needed 5 days)
• persp-projectile (- to 1:0.2.0-4)
  • Migration status for persp-projectile (- to 1:0.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating persp-projectile would introduce bugs in testing: #919035
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/persp-projectile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1078 days old (needed 5 days)
• srslte (- to 18.06.1+ds.1-1)
  • Migration status for srslte (- to 18.06.1+ds.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • srsenb/amd64 has unsatisfiable dependency
    • srsepc/amd64 has unsatisfiable dependency
    • srslte-core/amd64 has unsatisfiable dependency
    • srsue/amd64 has unsatisfiable dependency
    • srsenb/arm64 has unsatisfiable dependency
    • srsepc/arm64 has unsatisfiable dependency
    • srslte-core/arm64 has unsatisfiable dependency
    • srsue/arm64 has unsatisfiable dependency
    • srsenb/armel has unsatisfiable dependency
    • srsepc/armel has unsatisfiable dependency
    • srslte-core/armel has unsatisfiable dependency
    • srsue/armel has unsatisfiable dependency
    • srsenb/armhf has unsatisfiable dependency
    • srsepc/armhf has unsatisfiable dependency
    • srslte-core/armhf has unsatisfiable dependency
    • srsue/armhf has unsatisfiable dependency
    • srsenb/i386 has unsatisfiable dependency
    • srsepc/i386 has unsatisfiable dependency
    • srslte-core/i386 has unsatisfiable dependency
    • srsue/i386 has unsatisfiable dependency
    • srsenb/mips64el has unsatisfiable dependency
    • srsepc/mips64el has unsatisfiable dependency
    • srslte-core/mips64el has unsatisfiable dependency
    • srsue/mips64el has unsatisfiable dependency
    • srsenb/ppc64el has unsatisfiable dependency
    • srsepc/ppc64el has unsatisfiable dependency
    • srslte-core/ppc64el has unsatisfiable dependency
    • srsue/ppc64el has unsatisfiable dependency
    • srsenb/s390x has unsatisfiable dependency
    • srsepc/s390x has unsatisfiable dependency
    • srslte-core/s390x has unsatisfiable dependency
    • srsue/s390x has unsatisfiable dependency
    • Updating srslte would introduce bugs in testing: #982113, #993701
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/srslte.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1078 days old (needed 5 days)
• python-dugong (- to 3.8.1+dfsg-1)
  • Migration status for python-dugong (- to 3.8.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dugong would introduce bugs in testing: #1002102
    • autopkgtest for python-dugong/blocked-on-ci-infra: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dugong.html
    • 1079 days old (needed 5 days)
• stylish-haskell (- to 0.12.2.0-1)
  • Migration status for stylish-haskell (- to 0.12.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stylish-haskell would introduce bugs in testing: #1017205
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-strict-dev (<< 0.5)
    • Build-Depends(-Arch): stylish-haskell haskell-hsyaml
    • Build-Depends(-Arch): stylish-haskell haskell-hsyaml-aeson
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stylish-haskell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1084 days old (needed 5 days)
• golang-github-manyminds-api2go (- to 1.0-RC4-1)
  • Migration status for golang-github-manyminds-api2go (- to 1.0-RC4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-manyminds-api2go would introduce bugs in testing: #1008425
    • autopkgtest for golang-github-manyminds-api2go/1.0-RC4-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-manyminds-api2go.html
    • 1085 days old (needed 5 days)
• gauche-c-wrapper (- to 0.6.1-12)
  • Migration status for gauche-c-wrapper (- to 0.6.1-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche-c-wrapper gauche (not considered)
    • Depends: gauche-c-wrapper gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche-c-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1087 days old (needed 5 days)
• khronos-opencl-man (- to 1.0~svn33624-5)
  • Migration status for khronos-opencl-man (- to 1.0~svn33624-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): khronos-opencl-man w3-dtd-mathml (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opencl-man.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1087 days old (needed 5 days)
• subvertpy (- to 0.11.0-1)
  • Migration status for subvertpy (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-subvertpy/amd64 has unsatisfiable dependency
    • python3-subvertpy/arm64 has unsatisfiable dependency
    • python3-subvertpy/armel has unsatisfiable dependency
    • python3-subvertpy/armhf has unsatisfiable dependency
    • python3-subvertpy/i386 has unsatisfiable dependency
    • python3-subvertpy/mips64el has unsatisfiable dependency
    • python3-subvertpy/ppc64el has unsatisfiable dependency
    • python3-subvertpy/s390x has unsatisfiable dependency
    • Updating subvertpy would introduce bugs in testing: #1009423
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/subvertpy.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1091 days old (needed 5 days)
• golang-github-ajg-form (- to 1.5+git20160822.523a5da-1.1)
  • Migration status for golang-github-ajg-form (- to 1.5+git20160822.523a5da-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-ajg-form would introduce bugs in testing: #997539
    • autopkgtest for golang-github-ajg-form/1.5+git20160822.523a5da-1.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ajg-form.html
    • 1092 days old (needed 5 days)
• lsdb (- to 0.11-10.2)
  • Migration status for lsdb (- to 0.11-10.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lsdb would introduce bugs in testing: #965706
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsdb.html
    • 1092 days old (needed 5 days)
• ruby-ami (- to 2.4.0-1.1)
  • Migration status for ruby-ami (- to 2.4.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-ami ruby-celluloid-io (not considered)
    • Depends: ruby-ami ruby-celluloid-io (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-ami.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1092 days old (needed 5 days)
• tldjs (- to 2.3.1-1.1)
  • Migration status for tldjs (- to 2.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tldjs would introduce bugs in testing: #986436
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tldjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1092 days old (needed 5 days)
• android-platform-external-doclava (- to 6.0.1+r55-1.1)
  • Migration status for android-platform-external-doclava (- to 6.0.1+r55-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-doclava would introduce bugs in testing: #1012103
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-doclava.html
    • 1093 days old (needed 5 days)
• jabber-querybot (- to 0.1.0-1.1)
  • Migration status for jabber-querybot (- to 0.1.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jabber-querybot libnet-jabber-perl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jabber-querybot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1093 days old (needed 5 days)
• jodd (- to 3.8.6-1.1)
  • Migration status for jodd (- to 3.8.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jodd would introduce bugs in testing: #961298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jodd.html
    • 1093 days old (needed 5 days)
• xneur (- to 0.20.0-3)
  • Migration status for xneur (- to 0.20.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xneur would introduce bugs in testing: #1037902, #999922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xneur.html
    • Reproducible on i386 - info ♻
    • 1093 days old (needed 5 days)
• focalinux (- to 2010-09-3.1)
  • Migration status for focalinux (- to 2010-09-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating focalinux would introduce bugs in testing: #1051055
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/focalinux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1094 days old (needed 5 days)
• giblib (- to 1.2.4-13)
  • Migration status for giblib (- to 1.2.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating giblib would introduce bugs in testing: #1018021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giblib.html
    • 1094 days old (needed 5 days)
• jquery-simpletreemenu (- to 1.5.0-2.1)
  • Migration status for jquery-simpletreemenu (- to 1.5.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jquery-simpletreemenu would introduce bugs in testing: #979940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-simpletreemenu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1094 days old (needed 5 days)
• golang-github-filosottile-b2 (- to 0.0~git20170207.b197f7a-1)
  • Migration status for golang-github-filosottile-b2 (- to 0.0~git20170207.b197f7a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-filosottile-b2.html
    • autopkgtest for golang-github-filosottile-b2/0.0~git20170207.b197f7a-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1095 days old (needed 2 days)
• golang-github-gopherjs-jsbuiltin (- to 0.0~git20180426.5009155-1)
  • Migration status for golang-github-gopherjs-jsbuiltin (- to 0.0~git20180426.5009155-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gopherjs-jsbuiltin.html
    • autopkgtest for golang-github-gopherjs-jsbuiltin/0.0~git20180426.5009155-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1095 days old (needed 2 days)
• golang-github-nf-cr2 (- to 0.0~git20180623.4699471-1)
  • Migration status for golang-github-nf-cr2 (- to 0.0~git20180623.4699471-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-nf-cr2.html
    • autopkgtest for golang-github-nf-cr2/0.0~git20180623.4699471-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1095 days old (needed 2 days)
• golang-github-tomnomnom-linkheader (- to 0.1.0+git20180905.02ca582-1)
  • Migration status for golang-github-tomnomnom-linkheader (- to 0.1.0+git20180905.02ca582-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tomnomnom-linkheader.html
    • autopkgtest for golang-github-tomnomnom-linkheader/0.1.0+git20180905.02ca582-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1095 days old (needed 2 days)
• graypy (- to 2.1.0-1)
  • Migration status for graypy (- to 2.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): graypy python-amqplib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graypy.html
    • autopkgtest for graypy/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1095 days old (needed 2 days)
• jwchat (- to 1.0+dfsg-1.5)
  • Migration status for jwchat (- to 1.0+dfsg-1.5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jwchat jsjac (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jwchat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1095 days old (needed 5 days)
• ruby-omniauth-bitbucket (- to 0.0.2-1.1)
  • Migration status for ruby-omniauth-bitbucket (- to 0.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-bitbucket would introduce bugs in testing: #1030812
    • autopkgtest for ruby-omniauth-bitbucket/0.0.2-1.1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-bitbucket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1095 days old (needed 5 days)
• gpt (- to 1.1-7)
  • Migration status for gpt (- to 1.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpt would introduce bugs in testing: #1000126
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1096 days old (needed 5 days)
• octave-brain2mesh (- to 0.7.9-2)
  • Migration status for octave-brain2mesh (- to 0.7.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-brain2mesh would introduce bugs in testing: #1013597
    • Depends: octave-brain2mesh octave-iso2mesh
    • Depends: octave-brain2mesh octave-jnifti
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-brain2mesh.html
    • 1096 days old (needed 5 days)
• ripe-atlas-tools (- to 2.3.0-2.1)
  • Migration status for ripe-atlas-tools (- to 2.3.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ripe-atlas-tools would introduce bugs in testing: #997379
    • Build-Depends(-Arch): ripe-atlas-tools ripe-atlas-sagan
    • Depends: ripe-atlas-tools ripe-atlas-sagan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 1096 days old (needed 5 days)
• automake1.11 (- to 1:1.11.6-6)
  • Migration status for automake1.11 (- to 1:1.11.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating automake1.11 would introduce bugs in testing: #1038944
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/automake1.11.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1097 days old (needed 5 days)
• jsjac (- to 1.3.4+dfsg-3)
  • Migration status for jsjac (- to 1.3.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsjac would introduce bugs in testing: #1006027
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsjac.html
    • New but not reproducible on arm64 - info ♻
    • 1097 days old (needed 5 days)
• lua5.1-policy (- to 33+nmu1)
  • Migration status for lua5.1-policy (- to 33+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lua5.1-policy would introduce bugs in testing: #965710
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua5.1-policy.html
    • 1097 days old (needed 5 days)
• mess-desktop-entries (- to 0.2-4.1)
  • Migration status for mess-desktop-entries (- to 0.2-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mess-desktop-entries mame (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mess-desktop-entries.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1097 days old (needed 5 days)
• php-net-ipv6 (- to 1.3.0b4-1.1)
  • Migration status for php-net-ipv6 (- to 1.3.0b4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-ipv6 would introduce bugs in testing: #1004531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ipv6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1097 days old (needed 5 days)
• wiliki (- to 0.6.2-1.1)
  • Migration status for wiliki (- to 0.6.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wiliki gauche (not considered)
    • Depends: wiliki gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wiliki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1098 days old (needed 5 days)
• android-framework-23 (- to 6.0.1+r72-6)
  • Migration status for android-framework-23 (- to 6.0.1+r72-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-framework-23 would introduce bugs in testing: #1011567
    • Build-Depends(-Arch): android-framework-23 android-platform-build
    • Build-Depends(-Arch): android-framework-23 android-platform-external-doclava
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-framework-23.html
    • autopkgtest for android-framework-23/6.0.1+r72-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1099 days old (needed 2 days)
• android-platform-build (- to 1:10.0.0+r36-1)
  • Migration status for android-platform-build (- to 1:10.0.0+r36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-build would introduce bugs in testing: #1042042, #1050437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-build.html
    • Reproducible on i386 - info ♻
    • 1099 days old (needed 5 days)
• leap-archive-keyring (- to 2017.11.24+nmu1)
  • Migration status for leap-archive-keyring (- to 2017.11.24+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leap-archive-keyring would introduce bugs in testing: #880220
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leap-archive-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1099 days old (needed 5 days)
• monkeysphere (- to 0.43-3.1)
  • Migration status for monkeysphere (- to 0.43-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating monkeysphere would introduce bugs in testing: #1011900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monkeysphere.html
    • autopkgtest for monkeysphere/0.43-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1099 days old (needed 2 days)
• nautilus-scripts-manager (- to 2.0-1.1)
  • Migration status for nautilus-scripts-manager (- to 2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nautilus-scripts-manager would introduce bugs in testing: #1033761
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-scripts-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1099 days old (needed 5 days)
• pafy (- to 0.5.2-2.1)
  • Migration status for pafy (- to 0.5.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pafy would introduce bugs in testing: #1016520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pafy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1099 days old (needed 5 days)
• pysolfc-cardsets (- to 2.0+dfsg2-2.1)
  • Migration status for pysolfc-cardsets (- to 2.0+dfsg2-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pysolfc-cardsets pysolfc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc-cardsets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1099 days old (needed 5 days)
• resvg (- to 0.8.0-4)
  • Migration status for resvg (- to 0.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-resvg-dev/amd64 has unsatisfiable dependency
    • librust-usvg-dev/amd64 has unsatisfiable dependency
    • librust-resvg-dev/arm64 has unsatisfiable dependency
    • librust-usvg-dev/arm64 has unsatisfiable dependency
    • librust-resvg-dev/armhf has unsatisfiable dependency
    • librust-usvg-dev/armhf has unsatisfiable dependency
    • librust-resvg-dev/i386 has unsatisfiable dependency
    • librust-usvg-dev/i386 has unsatisfiable dependency
    • librust-resvg-dev/mips64el has unsatisfiable dependency
    • librust-usvg-dev/mips64el has unsatisfiable dependency
    • librust-resvg-dev/ppc64el has unsatisfiable dependency
    • librust-usvg-dev/ppc64el has unsatisfiable dependency
    • librust-resvg-dev/s390x has unsatisfiable dependency
    • librust-usvg-dev/s390x has unsatisfiable dependency
    • Updating resvg would introduce bugs in testing: #1002188
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-roxmltree-0.7+default-dev
    • Impossible Build-Depends(-Arch): resvg -> patchelf/0.14.3-1+b1/mips64el
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/resvg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1099 days old (needed 5 days)
• w3-dtd-mathml (- to 2.0.0.0-5.1)
  • Migration status for w3-dtd-mathml (- to 2.0.0.0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3-dtd-mathml would introduce bugs in testing: #994795
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3-dtd-mathml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1099 days old (needed 5 days)
• vlogger (- to 1.3-4.1)
  • Migration status for vlogger (- to 1.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vlogger would introduce bugs in testing: #965867
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlogger.html
    • 1100 days old (needed 5 days)
• libirclib-java (- to 1.10-4)
  • Migration status for libirclib-java (- to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libirclib-java would introduce bugs in testing: #1026625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libirclib-java.html
    • 1101 days old (needed 5 days)
• zeek-aux (- to 0.45-1)
  • Migration status for zeek-aux (- to 0.45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zeek-aux would introduce bugs in testing: #985522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeek-aux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1102 days old (needed 5 days)
• errbot (- to 6.1.7+ds-1)
  • Migration status for errbot (- to 6.1.7+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating errbot would introduce bugs in testing: #1054729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/errbot.html
    • 1103 days old (needed 5 days)
• cecil (- to 0.9.5+dfsg-5.1)
  • Migration status for cecil (- to 0.9.5+dfsg-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cecil would introduce bugs in testing: #1053554
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1104 days old (needed 5 days)
• asterisk-prompt-de (- to 2.0-1.2)
  • Migration status for asterisk-prompt-de (- to 2.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: asterisk-prompt-de asterisk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-prompt-de.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1107 days old (needed 5 days)
• broker (- to 1.4.0+ds1-1)
  • Migration status for broker (- to 1.4.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating broker would introduce bugs in testing: #1037597
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/broker.html
    • 1107 days old (needed 5 days)
• cycle-quotes (- to 0.1-4)
  • Migration status for cycle-quotes (- to 0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cycle-quotes would introduce bugs in testing: #1020192
    • autopkgtest for cycle-quotes/0.1-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cycle-quotes.html
    • 1107 days old (needed 5 days)
• node-node-localstorage (- to 2.1.5-1)
  • Migration status for node-node-localstorage (- to 2.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-localstorage would introduce bugs in testing: #1013621
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-localstorage.html
    • autopkgtest for node-node-localstorage/2.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1107 days old (needed 2 days)
• pypuppetdb (- to 2.2.0-1)
  • Migration status for pypuppetdb (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pypuppetdb would introduce bugs in testing: #1052771
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypuppetdb.html
    • autopkgtest for pypuppetdb/2.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1107 days old (needed 2 days)
• gauche (- to 0.9.10-3)
  • Migration status for gauche (- to 0.9.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gauche would introduce bugs in testing: #1023035
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1110 days old (needed 5 days)
• adabrowse (- to 4.0.3-14)
  • Migration status for adabrowse (- to 4.0.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adabrowse would introduce bugs in testing: #1008980
    • autopkgtest for adabrowse/4.0.3-14: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): adabrowse asis
    • Depends: adabrowse asis
    • Depends: adabrowse gcc-10
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adabrowse.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1113 days old (needed 5 days)
• spyder-reports (- to 0.1.1-4)
  • Migration status for spyder-reports (- to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spyder-reports would introduce bugs in testing: #982647
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-reports.html
    • autopkgtest for spyder-reports/0.1.1-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • 1115 days old (needed 5 days)
• clippoly (- to 0.11-10)
  • Migration status for clippoly (- to 0.11-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clippoly would introduce bugs in testing: #976540
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clippoly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1118 days old (needed 5 days)
• adacontrol (- to 1.21r6b-7)
  • Migration status for adacontrol (- to 1.21r6b-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • adacontrol/amd64 has unsatisfiable dependency
    • adacontrol/arm64 has unsatisfiable dependency
    • adacontrol/armel has unsatisfiable dependency
    • adacontrol/armhf has unsatisfiable dependency
    • adacontrol/i386 has unsatisfiable dependency
    • adacontrol/mips64el has unsatisfiable dependency
    • adacontrol/ppc64el has unsatisfiable dependency
    • adacontrol/s390x has unsatisfiable dependency
    • Updating adacontrol would introduce bugs in testing: #1008982
    • adacontrol unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • Build-Depends(-Arch): adacontrol asis
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adacontrol.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1119 days old (needed 5 days)
• asis (- to 2019-5)
  • Migration status for asis (- to 2019-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • asis-programs/amd64 has unsatisfiable dependency
    • asis-programs/arm64 has unsatisfiable dependency
    • asis-programs/armel has unsatisfiable dependency
    • asis-programs/armhf has unsatisfiable dependency
    • asis-programs/i386 has unsatisfiable dependency
    • asis-programs/mips64el has unsatisfiable dependency
    • asis-programs/ppc64el has unsatisfiable dependency
    • asis-programs/s390x has unsatisfiable dependency
    • Updating asis would introduce bugs in testing: #1008979
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/asis.html
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlezout8-dev
    • Build-Depends(-Arch): asis gcc-10
    • Depends: asis gcc-10
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1119 days old (needed 5 days)
• libaws (- to 20.2-2)
  • Migration status for libaws (- to 20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libaws-bin/amd64 has unsatisfiable dependency
    • libaws20-dev/amd64 has unsatisfiable dependency
    • libaws6/amd64 has unsatisfiable dependency
    • libaws-bin/arm64 has unsatisfiable dependency
    • libaws20-dev/arm64 has unsatisfiable dependency
    • libaws6/arm64 has unsatisfiable dependency
    • libaws-bin/armel has unsatisfiable dependency
    • libaws20-dev/armel has unsatisfiable dependency
    • libaws6/armel has unsatisfiable dependency
    • libaws-bin/armhf has unsatisfiable dependency
    • libaws20-dev/armhf has unsatisfiable dependency
    • libaws6/armhf has unsatisfiable dependency
    • libaws-bin/i386 has unsatisfiable dependency
    • libaws20-dev/i386 has unsatisfiable dependency
    • libaws6/i386 has unsatisfiable dependency
    • libaws-bin/mips64el has unsatisfiable dependency
    • libaws20-dev/mips64el has unsatisfiable dependency
    • libaws6/mips64el has unsatisfiable dependency
    • libaws-bin/ppc64el has unsatisfiable dependency
    • libaws20-dev/ppc64el has unsatisfiable dependency
    • libaws6/ppc64el has unsatisfiable dependency
    • libaws-bin/s390x has unsatisfiable dependency
    • libaws20-dev/s390x has unsatisfiable dependency
    • libaws6/s390x has unsatisfiable dependency
    • Updating libaws would introduce bugs in testing: #1008981, #1023114, #997457
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode10-dev (>= 21)
    • Build-Depends(-Arch): libaws asis
    • Build-Depends(-Arch): libaws gcc-10
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libaws.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1119 days old (needed 5 days)
• libhandy (- to 0.0.13-3)
  • Migration status for libhandy (- to 0.0.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libhandy would introduce bugs in testing: #991036
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhandy.html
    • autopkgtest for libhandy/0.0.13-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1121 days old (needed 2 days)
• anki (- to 2.1.15+dfsg-3)
  • Migration status for anki (- to 2.1.15+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating anki would introduce bugs in testing: #1053541, #958853
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anki.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1124 days old (needed 5 days)
• py-lz4framed (- to 0.14.0-1)
  • Migration status for py-lz4framed (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating py-lz4framed would introduce bugs in testing: #978287
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-lz4framed.html
    • autopkgtest for py-lz4framed/0.14.0-1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1128 days old (needed 5 days)
• leaflet-image (- to 0.4.0~dfsg-3)
  • Migration status for leaflet-image (- to 0.4.0~dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leaflet-image would introduce bugs in testing: #1003260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leaflet-image.html
    • autopkgtest for leaflet-image/0.4.0~dfsg-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 1129 days old (needed 5 days)
• rust-tcmalloc (- to 0.3.0-2)
  • Migration status for rust-tcmalloc (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-tcmalloc would introduce bugs in testing: #981869
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tcmalloc.html
    • autopkgtest for rust-tcmalloc/0.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1134 days old (needed 2 days)
• rust-rust-code-analysis (- to 0.0.18-2)
  • Migration status for rust-rust-code-analysis (- to 0.0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rust-code-analysis-dev/amd64 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/arm64 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/armel has unsatisfiable dependency
    • librust-rust-code-analysis-dev/armhf has unsatisfiable dependency
    • librust-rust-code-analysis-dev/i386 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/mips64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/ppc64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/s390x has unsatisfiable dependency
    • Updating rust-rust-code-analysis would introduce bugs in testing: #1031013
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-0.17+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1136 days old (needed 5 days)
• chibi-scheme (- to 0.9.1-3)
  • Migration status for chibi-scheme (- to 0.9.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chibi-scheme would introduce bugs in testing: #981762
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/chibi-scheme.html
  • Additional info:
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for chibi-scheme/0.9.1-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1137 days old (needed 2 days)
• python-opentracing (- to 2.4.0-1)
  • Migration status for python-opentracing (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-opentracing would introduce bugs in testing: #1026729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-opentracing.html
    • 1139 days old (needed 5 days)
• octave-jnifti (- to 0.6-2)
  • Migration status for octave-jnifti (- to 0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-jnifti would introduce bugs in testing: #1013592
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-jnifti.html
    • 1149 days old (needed 5 days)
• ibutils (- to 1.5.7+0.2.gbd7e502-3)
  • Migration status for ibutils (- to 1.5.7+0.2.gbd7e502-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ibutils opensm (not considered)
    • Depends: ibutils opensm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1151 days old (needed 5 days)
• qwertone (- to 0.3.0-2)
  • Migration status for qwertone (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qwertone would introduce bugs in testing: #1002148
    • qwertone unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on i386: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk-0.7+v3-22-dev (>= 0.7-~~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qwertone.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1151 days old (needed 5 days)
• libzorpll (- to 7.0.4.0-2)
  • Migration status for libzorpll (- to 7.0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libzorpll-7.0-4/amd64 has unsatisfiable dependency
    • libzorpll-7.0-4/arm64 has unsatisfiable dependency
    • libzorpll-7.0-4/armel has unsatisfiable dependency
    • libzorpll-7.0-4/armhf has unsatisfiable dependency
    • libzorpll-7.0-4/i386 has unsatisfiable dependency
    • libzorpll-7.0-4/mips64el has unsatisfiable dependency
    • libzorpll-7.0-4/ppc64el has unsatisfiable dependency
    • libzorpll-7.0-4/s390x has unsatisfiable dependency
    • Updating libzorpll would introduce bugs in testing: #1006506
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libz/libzorpll.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1167 days old (needed 5 days)
• intel-hdcp (- to 20.3.0-1)
  • Migration status for intel-hdcp (- to 20.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-hdcp would introduce bugs in testing: #1052643
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-hdcp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1169 days old (needed 5 days)
• php-horde-mail-autoconfig (- to 1.0.3-10)
  • Migration status for php-horde-mail-autoconfig (- to 1.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mail-autoconfig/1.0.3-10: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Depends: php-horde-mail-autoconfig php-net-dns2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mail-autoconfig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1172 days old (needed 5 days)
• php-horde-mnemo (- to 4.2.14-10)
  • Migration status for php-horde-mnemo (- to 4.2.14-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-mnemo php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mnemo.html
    • autopkgtest for php-horde-mnemo/4.2.14-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1172 days old (needed 2 days)
• python-acora (- to 2.2-1.3)
  • Migration status for python-acora (- to 2.2-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-acora would introduce bugs in testing: #1055707, #1056849
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-acora.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 1173 days old (needed 5 days)
• php-net-dns2 (- to 1.5.0-1)
  • Migration status for php-net-dns2 (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dns2 would introduce bugs in testing: #1042457
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dns2.html
    • autopkgtest for php-net-dns2/1.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1174 days old (needed 2 days)
• rust-mdl (- to 1.0.4-1)
  • Migration status for rust-mdl (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-mdl would introduce bugs in testing: #1052952
    • autopkgtest for rust-mdl/1.0.4-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-mdl.html
    • Reproducible on i386 - info ♻
    • 1174 days old (needed 5 days)
• gdis (- to 0.90-6)
  • Migration status for gdis (- to 0.90-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gdis gtkglext (not considered)
    • Depends: gdis gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdis.html
    • autopkgtest for gdis/0.90-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1181 days old (needed 2 days)
• plm (- to 2.9.2-1)
  • Migration status for plm (- to 2.9.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plm jruby (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1182 days old (needed 5 days)
• sardana (- to 3.0.3-1)
  • Migration status for sardana (- to 3.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sardana would introduce bugs in testing: #1030905
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sardana.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1186 days old (needed 5 days)
• rust-rspotify (- to 0.7.0-3)
  • Migration status for rust-rspotify (- to 0.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rspotify-dev/amd64 has unsatisfiable dependency
    • librust-rspotify-dev/arm64 has unsatisfiable dependency
    • librust-rspotify-dev/armel has unsatisfiable dependency
    • librust-rspotify-dev/armhf has unsatisfiable dependency
    • librust-rspotify-dev/i386 has unsatisfiable dependency
    • librust-rspotify-dev/mips64el has unsatisfiable dependency
    • librust-rspotify-dev/ppc64el has unsatisfiable dependency
    • librust-rspotify-dev/s390x has unsatisfiable dependency
    • Updating rust-rspotify would introduce bugs in testing: #1031072
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-webbrowser-0.5+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rspotify.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1189 days old (needed 5 days)
• xjig (- to 2.4-14.2)
  • Migration status for xjig (- to 2.4-14.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xjig/amd64 has unsatisfiable dependency
    • xjig/arm64 has unsatisfiable dependency
    • xjig/armel has unsatisfiable dependency
    • xjig/armhf has unsatisfiable dependency
    • xjig/i386 has unsatisfiable dependency
    • xjig/mips64el has unsatisfiable dependency
    • xjig/ppc64el has unsatisfiable dependency
    • xjig/s390x has unsatisfiable dependency
    • Updating xjig would introduce bugs in testing: #1014623, #1016403
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xjig.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1189 days old (needed 5 days)
• php-horde-nag (- to 4.2.19-6)
  • Migration status for php-horde-nag (- to 4.2.19-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-nag php-horde-dav (not considered)
    • Invalidated by dependency
    • Depends: php-horde-nag php-horde
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nag.html
    • autopkgtest for php-horde-nag/4.2.19-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1190 days old (needed 2 days)
• ruby-rails-assets-fine-uploader (- to 5.13.0-2)
  • Migration status for ruby-rails-assets-fine-uploader (- to 5.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-fine-uploader would introduce bugs in testing: #1034027
    • autopkgtest for ruby-rails-assets-fine-uploader/5.13.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-fine-uploader.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1206 days old (needed 5 days)
• eclipse-cdt (- to 9.9.0-5)
  • Migration status for eclipse-cdt (- to 9.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eclipse-cdt would introduce bugs in testing: #1022294
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-cdt.html
    • 1219 days old (needed 5 days)
• fweb (- to 1.62-14)
  • Migration status for fweb (- to 1.62-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fweb would introduce bugs in testing: #1030350
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fweb.html
    • 1227 days old (needed 5 days)
• github-backup (- to 1.20200721-2)
  • Migration status for github-backup (- to 1.20200721-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating github-backup would introduce bugs in testing: #1017298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/github-backup.html
    • 1228 days old (needed 5 days)
• ruby-rails-assets-blueimp-gallery (- to 2.33.0-2)
  • Migration status for ruby-rails-assets-blueimp-gallery (- to 2.33.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-blueimp-gallery would introduce bugs in testing: #1033914
    • autopkgtest for ruby-rails-assets-blueimp-gallery/2.33.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-blueimp-gallery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1230 days old (needed 5 days)
• gnome-video-arcade (- to 0.8.8-5)
  • Migration status for gnome-video-arcade (- to 0.8.8-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnome-video-arcade mame (not considered)
    • Depends: gnome-video-arcade mame (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-video-arcade.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1231 days old (needed 5 days)
• yrmcds (- to 1.1.9-1)
  • Migration status for yrmcds (- to 1.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yrmcds would introduce bugs in testing: #1037907
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yrmcds.html
    • Reproducible on i386 - info ♻
    • 1233 days old (needed 5 days)
• prayer (- to 1.3.5-dfsg1-8)
  • Migration status for prayer (- to 1.3.5-dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prayer would introduce bugs in testing: #1010066
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prayer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1239 days old (needed 5 days)
• ruby-rails-assets-highlightjs (- to 9.12.0-3)
  • Migration status for ruby-rails-assets-highlightjs (- to 9.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-highlightjs would introduce bugs in testing: #946846
    • autopkgtest for ruby-rails-assets-highlightjs/9.12.0-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-highlightjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1240 days old (needed 5 days)
• virtaal (- to 0.7.1+git20191021+ds1-2)
  • Migration status for virtaal (- to 0.7.1+git20191021+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtaal would introduce bugs in testing: #1030008
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtaal.html
    • autopkgtest for virtaal/0.7.1+git20191021+ds1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1240 days old (needed 5 days)
• fonts-pecita (- to 5.4-2)
  • Migration status for fonts-pecita (- to 5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-pecita would introduce bugs in testing: #975810
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-pecita.html
    • 1241 days old (needed 5 days)
• calculix-cgx (- to 2.17+dfsg-2)
  • Migration status for calculix-cgx (- to 2.17+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calculix-cgx would introduce bugs in testing: #1049440
    • Build-Depends(-Arch): calculix-cgx mesa
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-cgx.html
    • autopkgtest for calculix-cgx/2.17+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1244 days old (needed 2 days)
• d1x-rebirth (- to 0.58.1-1.2)
  • Migration status for d1x-rebirth (- to 0.58.1-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating d1x-rebirth would introduce bugs in testing: #1057551
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1248 days old (needed 5 days)
• d2x-rebirth (- to 0.58.1-1.3)
  • Migration status for d2x-rebirth (- to 0.58.1-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating d2x-rebirth would introduce bugs in testing: #1057552
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1248 days old (needed 5 days)
• redmine-plugin-redhopper (- to 2.0.0-2)
  • Migration status for redmine-plugin-redhopper (- to 2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-redhopper redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-redhopper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1248 days old (needed 5 days)
• nastran (- to 0.1.95-2)
  • Migration status for nastran (- to 0.1.95-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nastran would introduce bugs in testing: #1054241
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1252 days old (needed 5 days)
• opensm (- to 3.3.23-2)
  • Migration status for opensm (- to 3.3.23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensm would introduce bugs in testing: #1052380
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1255 days old (needed 5 days)
• crazydiskinfo (- to 1.1.0-2)
  • Migration status for crazydiskinfo (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crazydiskinfo would introduce bugs in testing: #997156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crazydiskinfo.html
    • 1262 days old (needed 5 days)
• kwin-effect-xrdesktop (- to 0.15.1-1)
  • Migration status for kwin-effect-xrdesktop (- to 0.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kwin-effect-xrdesktop/amd64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/arm64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/armel has unsatisfiable dependency
    • kwin-effect-xrdesktop/armhf has unsatisfiable dependency
    • kwin-effect-xrdesktop/i386 has unsatisfiable dependency
    • kwin-effect-xrdesktop/mips64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/ppc64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/s390x has unsatisfiable dependency
    • Updating kwin-effect-xrdesktop would introduce bugs in testing: #1037382, #993015
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kwin-effect-xrdesktop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1262 days old (needed 5 days)
• effcee (- to 2019.1-1)
  • Migration status for effcee (- to 2019.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating effcee would introduce bugs in testing: #984048
    • autopkgtest for effcee/2019.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/amd64
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/arm64
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/armel
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/armhf
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/i386
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/mips64el
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/ppc64el
    • Impossible Depends: effcee -> libre2-9/20220601+dfsg-1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/effcee.html
    • 1264 days old (needed 5 days)
• bashtop (- to 0.9.25-1)
  • Migration status for bashtop (- to 0.9.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bashtop would introduce bugs in testing: #968381
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bashtop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1265 days old (needed 5 days)
• fonts-kacst (- to 2.01+mry-15)
  • Migration status for fonts-kacst (- to 2.01+mry-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-kacst would introduce bugs in testing: #1041017
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-kacst.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1268 days old (needed 5 days)
• eclipse-remote (- to 2.1.0-2)
  • Migration status for eclipse-remote (- to 2.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): eclipse-remote eclipse-cdt (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-remote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1269 days old (needed 5 days)
• git-repair (- to 1.20200102-2)
  • Migration status for git-repair (- to 1.20200102-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git-repair would introduce bugs in testing: #1054816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-repair.html
    • 1270 days old (needed 5 days)
• dune-pdelab (- to 2.7~20200605-2)
  • Migration status for dune-pdelab (- to 2.7~20200605-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdune-pdelab-dev/amd64 has unsatisfiable dependency
    • libdune-pdelab-dev/arm64 has unsatisfiable dependency
    • libdune-pdelab-dev/armel has unsatisfiable dependency
    • libdune-pdelab-dev/armhf has unsatisfiable dependency
    • libdune-pdelab-dev/i386 has unsatisfiable dependency
    • libdune-pdelab-dev/mips64el has unsatisfiable dependency
    • libdune-pdelab-dev/ppc64el has unsatisfiable dependency
    • libdune-pdelab-dev/s390x has unsatisfiable dependency
    • Updating dune-pdelab would introduce bugs in testing: #1023356, #976499
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dune-pdelab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1271 days old (needed 5 days)
• openrocket (- to 15.03.6)
  • Migration status for openrocket (- to 15.03.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openrocket would introduce bugs in testing: #984609
    • Depends: openrocket openjdk-8
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1271 days old (needed 5 days)
• php-horde-whups (- to 3.0.12-7)
  • Migration status for php-horde-whups (- to 3.0.12-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-whups php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1281 days old (needed 5 days)
• php-horde-gollem (- to 3.0.13-5)
  • Migration status for php-horde-gollem (- to 3.0.13-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-gollem php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-gollem php-horde-editor
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-gollem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1282 days old (needed 5 days)
• php-horde-trean (- to 1.1.10-3)
  • Migration status for php-horde-trean (- to 1.1.10-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-trean php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1282 days old (needed 5 days)
• php-horde-dav (- to 1.1.4-6)
  • Migration status for php-horde-dav (- to 1.1.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-dav php-sabredav (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 days)
• php-horde-editor (- to 2.0.5+debian0-5)
  • Migration status for php-horde-editor (- to 2.0.5+debian0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-editor would introduce bugs in testing: #1042715
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 days)
• php-horde-groupware (- to 5.2.22-6)
  • Migration status for php-horde-groupware (- to 5.2.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-groupware php-horde-turba (not considered)
    • Invalidated by dependency
    • Depends: php-horde-groupware php-horde
    • Depends: php-horde-groupware php-horde-gollem
    • Depends: php-horde-groupware php-horde-kronolith
    • Depends: php-horde-groupware php-horde-mnemo
    • Depends: php-horde-groupware php-horde-nag
    • Depends: php-horde-groupware php-horde-trean
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-groupware.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 days)
• php-horde-mongo (- to 1.1.0-6)
  • Migration status for php-horde-mongo (- to 1.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mongo would introduce bugs in testing: #820091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mongo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 days)
• php-horde-webmail (- to 5.2.22-6)
  • Migration status for php-horde-webmail (- to 5.2.22-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-webmail php-horde-turba (not considered)
    • Invalidated by dependency
    • Depends: php-horde-webmail php-horde
    • Depends: php-horde-webmail php-horde-gollem
    • Depends: php-horde-webmail php-horde-imp
    • Depends: php-horde-webmail php-horde-ingo
    • Depends: php-horde-webmail php-horde-kronolith
    • Depends: php-horde-webmail php-horde-mnemo
    • Depends: php-horde-webmail php-horde-nag
    • Depends: php-horde-webmail php-horde-trean
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-webmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 days)
• mkcue (- to 1-7)
  • Migration status for mkcue (- to 1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mkcue would introduce bugs in testing: #984237
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkcue.html
    • 1292 days old (needed 5 days)
• lix (- to 0.9.29-1.1)
  • Migration status for lix (- to 0.9.29-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lix/amd64 has unsatisfiable dependency
    • lix/arm64 has unsatisfiable dependency
    • lix/armhf has unsatisfiable dependency
    • lix/i386 has unsatisfiable dependency
    • Updating lix would introduce bugs in testing: #999750
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lix.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • 1304 days old (needed 5 days)
• iptables-converter (- to 0.9.8-1.2)
  • Migration status for iptables-converter (- to 0.9.8-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iptables-converter would introduce bugs in testing: #997602
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptables-converter.html
    • 1307 days old (needed 5 days)
• breezy-loom (- to 3.0.0+bzr167-1)
  • Migration status for breezy-loom (- to 3.0.0+bzr167-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating breezy-loom would introduce bugs in testing: #988156
    • autopkgtest for breezy-loom/3.0.0+bzr167-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy-loom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1316 days old (needed 5 days)
• octave-mpi (- to 3.1.0-1)
  • Migration status for octave-mpi (- to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-mpi/amd64 has unsatisfiable dependency
    • octave-mpi/arm64 has unsatisfiable dependency
    • octave-mpi/armel has unsatisfiable dependency
    • octave-mpi/armhf has unsatisfiable dependency
    • octave-mpi/i386 has unsatisfiable dependency
    • octave-mpi/mips64el has unsatisfiable dependency
    • octave-mpi/ppc64el has unsatisfiable dependency
    • octave-mpi/s390x has unsatisfiable dependency
    • Updating octave-mpi would introduce bugs in testing: #1009133
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/octave-mpi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1318 days old (needed 5 days)
• nautilus-filename-repairer (- to 0.2.0-3)
  • Migration status for nautilus-filename-repairer (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • nautilus-filename-repairer/amd64 has unsatisfiable dependency
    • nautilus-filename-repairer/arm64 has unsatisfiable dependency
    • nautilus-filename-repairer/armel has unsatisfiable dependency
    • nautilus-filename-repairer/armhf has unsatisfiable dependency
    • nautilus-filename-repairer/i386 has unsatisfiable dependency
    • nautilus-filename-repairer/mips64el has unsatisfiable dependency
    • nautilus-filename-repairer/ppc64el has unsatisfiable dependency
    • nautilus-filename-repairer/s390x has unsatisfiable dependency
    • Updating nautilus-filename-repairer would introduce bugs in testing: #1017623
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/nautilus-filename-repairer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1322 days old (needed 5 days)
• fakeroot-ng (- to 0.18-4.1)
  • Migration status for fakeroot-ng (- to 0.18-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fakeroot-ng would introduce bugs in testing: #1016266
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fakeroot-ng.html
    • 1326 days old (needed 5 days)
• telegram-purple (- to 1.4.3-3)
  • Migration status for telegram-purple (- to 1.4.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-purple would introduce bugs in testing: #1011846, #1040074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-purple.html
    • 1329 days old (needed 5 days)
• binutils64 (- to 1+c3)
  • Migration status for binutils64 (- to 1+c3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils64 would introduce bugs in testing: #987525, #987526
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1333 days old (needed 5 days)
• cpufrequtils (- to 008-2)
  • Migration status for cpufrequtils (- to 008-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpufrequtils would introduce bugs in testing: #877016
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpufrequtils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1342 days old (needed 5 days)
• sipxtapi (- to 3.3.0~test18+dfsg.1-0.1)
  • Migration status for sipxtapi (- to 3.3.0~test18+dfsg.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsipxtapi/amd64 has unsatisfiable dependency
    • libsipxtapi/arm64 has unsatisfiable dependency
    • libsipxtapi/armel has unsatisfiable dependency
    • libsipxtapi/armhf has unsatisfiable dependency
    • libsipxtapi/i386 has unsatisfiable dependency
    • libsipxtapi/mips64el has unsatisfiable dependency
    • libsipxtapi/ppc64el has unsatisfiable dependency
    • libsipxtapi/s390x has unsatisfiable dependency
    • Updating sipxtapi would introduce bugs in testing: #1058941, #984331, #986494, #999960
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sipxtapi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1344 days old (needed 5 days)
• ruby-jekyll-asciidoc (- to 3.0.0-2)
  • Migration status for ruby-jekyll-asciidoc (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-asciidoc would introduce bugs in testing: #1030465
    • autopkgtest for ruby-jekyll-asciidoc/3.0.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-asciidoc.html
    • 1354 days old (needed 5 days)
• rust-librespot-protocol (- to 0.1.0-2)
  • Migration status for rust-librespot-protocol (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-librespot-protocol would introduce bugs in testing: #1002238
    • autopkgtest for rust-librespot-protocol/0.1.0-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-librespot-protocol.html
    • 1355 days old (needed 5 days)
• graphite-api (- to 1.1.3-6)
  • Migration status for graphite-api (- to 1.1.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graphite-api would introduce bugs in testing: #1026609
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graphite-api.html
    • 1356 days old (needed 5 days)
• cclib-data (- to 1.6.2-2)
  • Migration status for cclib-data (- to 1.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclib-data would introduce bugs in testing: #1057547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1365 days old (needed 5 days)
• libkqueue (- to 2.3.1-1)
  • Migration status for libkqueue (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libkqueue/2.3.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , ppc64el: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkqueue.html
    • Reproducible on arm64 - info ♻
    • 1365 days old (needed 5 days)
• ruby-thinking-sphinx (- to 4.1.0-3)
  • Migration status for ruby-thinking-sphinx (- to 4.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-thinking-sphinx ruby-riddle (not considered)
    • Depends: ruby-thinking-sphinx ruby-riddle (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-thinking-sphinx.html
    • autopkgtest for ruby-thinking-sphinx/4.1.0-3: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1365 days old (needed 5 days)
• sdaps (- to 1.9.8-0.1)
  • Migration status for sdaps (- to 1.9.8-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sdaps would introduce bugs in testing: #1001643
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdaps.html
    • autopkgtest for sdaps/1.9.8-0.1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 1365 days old (needed 5 days)
• ecb (- to 2.50+git20170628-1)
  • Migration status for ecb (- to 2.50+git20170628-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ecb would introduce bugs in testing: #1020168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecb.html
    • 1368 days old (needed 5 days)
• gcc-python-plugin (- to 0.17-6)
  • Migration status for gcc-python-plugin (- to 0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gcc-python3-dbg-plugin/amd64 has unsatisfiable dependency
    • gcc-python3-dbg-plugin/arm64 has unsatisfiable dependency
    • gcc-python3-dbg-plugin/armel has unsatisfiable dependency
    • gcc-python3-dbg-plugin/armhf has unsatisfiable dependency
    • gcc-python3-dbg-plugin/i386 has unsatisfiable dependency
    • gcc-python3-dbg-plugin/mips64el has unsatisfiable dependency
    • gcc-python3-dbg-plugin/ppc64el has unsatisfiable dependency
    • gcc-python3-dbg-plugin/s390x has unsatisfiable dependency
    • Updating gcc-python-plugin would introduce bugs in testing: #1000213, #963999, #978511
    • Build-Depends(-Arch): gcc-python-plugin gcc-10
    • Build-Depends(-Arch): gcc-python-plugin gcc-9
    • Depends: gcc-python-plugin gcc-9
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gcc-python-plugin.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1371 days old (needed 5 days)
• openexr-viewers (- to 2.3.0-1)
  • Migration status for openexr-viewers (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openexr-viewers/amd64 has unsatisfiable dependency
    • openexr-viewers/arm64 has unsatisfiable dependency
    • openexr-viewers/armel has unsatisfiable dependency
    • openexr-viewers/armhf has unsatisfiable dependency
    • openexr-viewers/i386 has unsatisfiable dependency
    • openexr-viewers/mips64el has unsatisfiable dependency
    • openexr-viewers/ppc64el has unsatisfiable dependency
    • openexr-viewers/s390x has unsatisfiable dependency
    • Updating openexr-viewers would introduce bugs in testing: #1017547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openexr-viewers.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1372 days old (needed 5 days)
• airport-utils (- to 2-8)
  • Migration status for airport-utils (- to 2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating airport-utils would introduce bugs in testing: #414092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/airport-utils.html
    • autopkgtest for airport-utils/2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1378 days old (needed 2 days)
• gcc-9-cross-mipsen (- to 4+c2)
  • Migration status for gcc-9-cross-mipsen (- to 4+c2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpp-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • Updating gcc-9-cross-mipsen would introduce bugs in testing: #946352, #963998
    • Build-Depends(-Arch): gcc-9-cross-mipsen autoconf2.64
    • Build-Depends(-Arch): gcc-9-cross-mipsen gcc-9
    • Built-Using: gcc-9-cross-mipsen gcc-9
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gcc-9-cross-mipsen.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1382 days old (needed 5 days)
• umatrix (- to 1.4.0+dfsg-1)
  • Migration status for umatrix (- to 1.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umatrix would introduce bugs in testing: #976697, #991344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umatrix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1386 days old (needed 5 days)
• libneo4j-client (- to 2.2.0-1.1)
  • Migration status for libneo4j-client (- to 2.2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libneo4j-client11/amd64 has unsatisfiable dependency
    • libneo4j-client11/arm64 has unsatisfiable dependency
    • libneo4j-client11/armel has unsatisfiable dependency
    • libneo4j-client11/armhf has unsatisfiable dependency
    • libneo4j-client11/i386 has unsatisfiable dependency
    • libneo4j-client11/mips64el has unsatisfiable dependency
    • libneo4j-client11/ppc64el has unsatisfiable dependency
    • libneo4j-client11/s390x has unsatisfiable dependency
    • Updating libneo4j-client would introduce bugs in testing: #984187
    • Build-Depends(-Arch): libneo4j-client libcypher-parser
    • Depends: libneo4j-client libcypher-parser
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libn/libneo4j-client.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1394 days old (needed 5 days)
• mahimahi (- to 0.98-1.1)
  • Migration status for mahimahi (- to 0.98-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mahimahi/amd64 has unsatisfiable dependency
    • mahimahi/arm64 has unsatisfiable dependency
    • mahimahi/armel has unsatisfiable dependency
    • mahimahi/armhf has unsatisfiable dependency
    • mahimahi/i386 has unsatisfiable dependency
    • mahimahi/mips64el has unsatisfiable dependency
    • mahimahi/ppc64el has unsatisfiable dependency
    • mahimahi/s390x has unsatisfiable dependency
    • Updating mahimahi would introduce bugs in testing: #977684, #984228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mahimahi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1399 days old (needed 5 days)
• aboot (- to 1.0~pre20200212-1)
  • Migration status for aboot (- to 1.0~pre20200212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aboot-cross/amd64 has unsatisfiable dependency
    • aboot-cross/arm64 has unsatisfiable dependency
    • aboot-cross/armel has unsatisfiable dependency
    • aboot-cross/armhf has unsatisfiable dependency
    • aboot-cross/i386 has unsatisfiable dependency
    • aboot-cross/mips64el has unsatisfiable dependency
    • aboot-cross/ppc64el has unsatisfiable dependency
    • aboot-cross/s390x has unsatisfiable dependency
    • Updating aboot would introduce bugs in testing: #805988
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/aboot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1401 days old (needed 5 days)
• ruby-jekyll-mentions (- to 1.6.0-1)
  • Migration status for ruby-jekyll-mentions (- to 1.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-mentions ruby-html-pipeline (not considered)
    • Depends: ruby-jekyll-mentions ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-mentions.html
    • autopkgtest for ruby-jekyll-mentions/1.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1402 days old (needed 2 days)
• win-iconv (- to 0.0.8-4)
  • Migration status for win-iconv (- to 0.0.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating win-iconv would introduce bugs in testing: #921904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win-iconv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1402 days old (needed 5 days)
• ruby-rubydns (- to 1.0.3-3)
  • Migration status for ruby-rubydns (- to 1.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rubydns would introduce bugs in testing: #1031468
    • autopkgtest for ruby-rubydns/1.0.3-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-rubydns ruby-celluloid-io
    • Depends: ruby-rubydns ruby-celluloid-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-rubydns.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1409 days old (needed 5 days)
• gnat-gps (- to 19.2-3)
  • Migration status for gnat-gps (- to 19.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnat-gps/amd64 has unsatisfiable dependency
    • gnat-gps/arm64 has unsatisfiable dependency
    • gnat-gps/mips64el has unsatisfiable dependency
    • gnat-gps/ppc64el has unsatisfiable dependency
    • gnat-gps/s390x has unsatisfiable dependency
    • Updating gnat-gps would introduce bugs in testing: #936624, #979146
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode9-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnat-gps.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1411 days old (needed 5 days)
• sassphp (- to 0.7-1)
  • Migration status for sassphp (- to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-sass/amd64 has unsatisfiable dependency
    • php-sass/arm64 has unsatisfiable dependency
    • php-sass/armel has unsatisfiable dependency
    • php-sass/armhf has unsatisfiable dependency
    • php-sass/i386 has unsatisfiable dependency
    • php-sass/mips64el has unsatisfiable dependency
    • php-sass/ppc64el has unsatisfiable dependency
    • php-sass/s390x has unsatisfiable dependency
    • Updating sassphp would introduce bugs in testing: #1035552
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sassphp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1411 days old (needed 5 days)
• mod-gnutls (- to 0.9.0-1.1)
  • Migration status for mod-gnutls (- to 0.9.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mod-gnutls would introduce bugs in testing: #1050670, #942737
    • Build-Depends(-Arch): mod-gnutls monkeysphere
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mod-gnutls.html
    • Reproducible on i386 - info ♻
    • 1413 days old (needed 5 days)
• pysolfc (- to 2.6.4-3)
  • Migration status for pysolfc (- to 2.6.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pysolfc would introduce bugs in testing: #1008708
    • autopkgtest for pysolfc/2.6.4-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc.html
    • 1417 days old (needed 5 days)
• ruby-google-cloud-translate (- to 1.3.0-2)
  • Migration status for ruby-google-cloud-translate (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-google-cloud-translate/amd64 has unsatisfiable dependency
    • ruby-google-cloud-translate/arm64 has unsatisfiable dependency
    • Updating ruby-google-cloud-translate would introduce bugs in testing: #964607
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-google-cloud-translate.html
    • ruby-google-cloud-translate unsatisfiable Build-Depends(-Arch) on amd64: ruby-googleauth (<< 0.10.0)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1427 days old (needed 5 days)
• kcov (- to 38+dfsg-1)
  • Migration status for kcov (- to 38+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcov would introduce bugs in testing: #964654
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcov.html
    • 1428 days old (needed 5 days)
• fonts-rit-sundar (- to 2.0.0+20170909-2)
  • Migration status for fonts-rit-sundar (- to 2.0.0+20170909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-rit-sundar would introduce bugs in testing: #1033698
    • autopkgtest for fonts-rit-sundar/2.0.0+20170909-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-rit-sundar.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1435 days old (needed 5 days)
• vagrant-bindfs (- to 1.1.6-1)
  • Migration status for vagrant-bindfs (- to 1.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vagrant-bindfs would introduce bugs in testing: #953226
    • autopkgtest for vagrant-bindfs/1.1.6-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-bindfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1435 days old (needed 5 days)
• seriousproton (- to 2020.01.15+dfsg-1)
  • Migration status for seriousproton (- to 2020.01.15+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating seriousproton would introduce bugs in testing: #1057114, #997264
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-audio2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-graphics2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-network2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-system2.5/2.5.1+dfsg-2+b2/s390x
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/amd64
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/arm64
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/armel
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/armhf
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/i386
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/mips64el
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/ppc64el
    • Impossible Depends: seriousproton -> libsfml-window2.5/2.5.1+dfsg-2+b2/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seriousproton.html
    • 1437 days old (needed 5 days)
• ghemical (- to 3.0.0-5)
  • Migration status for ghemical (- to 3.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ghemical libglade2 (not considered)
    • Depends: ghemical libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ghemical gtkglext
    • Depends: ghemical gtkglext
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghemical.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1445 days old (needed 5 days)
• dafny (- to 2.3.0+dfsg-0.1)
  • Migration status for dafny (- to 2.3.0+dfsg-0.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dafny boogie (not considered)
    • Depends: dafny boogie (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dafny.html
    • autopkgtest for dafny/2.3.0+dfsg-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1448 days old (needed 2 days)
• dltlyse (- to 1.1-1.1)
  • Migration status for dltlyse (- to 1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dltlyse would introduce bugs in testing: #966926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dltlyse.html
    • 1450 days old (needed 5 days)
• hilive (- to 2.0a-3)
  • Migration status for hilive (- to 2.0a-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hilive would introduce bugs in testing: #1053499
    • autopkgtest for hilive/2.0a-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hilive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1452 days old (needed 5 days)
• watson (- to 1.8.0-0.1)
  • Migration status for watson (- to 1.8.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watson would introduce bugs in testing: #997487
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watson.html
    • autopkgtest for watson/1.8.0-0.1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • 1461 days old (needed 5 days)
• pyhoca-gui (- to 0.6.1.1-1)
  • Migration status for pyhoca-gui (- to 0.6.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyhoca-gui would introduce bugs in testing: #1054832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyhoca-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1466 days old (needed 5 days)
• boogie (- to 2.4.1+dfsg-0.1)
  • Migration status for boogie (- to 2.4.1+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating boogie would introduce bugs in testing: #1052886
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boogie.html
    • autopkgtest for boogie/2.4.1+dfsg-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1471 days old (needed 2 days)
• dirspec (- to 13.10-1.1)
  • Migration status for dirspec (- to 13.10-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dirspec would introduce bugs in testing: #949937
    • dirspec unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dirspec.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 1476 days old (needed 5 days)
• python-efilter (- to 1.5-2.1)
  • Migration status for python-efilter (- to 1.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-efilter would introduce bugs in testing: #1042316
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-efilter.html
    • Reproducible on i386 - info ♻
    • 1476 days old (needed 5 days)
• opensta (- to 0~20191111gitc018cb2+dfsg-1)
  • Migration status for opensta (- to 0~20191111gitc018cb2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensta would introduce bugs in testing: #1037806
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensta.html
    • Reproducible on i386 - info ♻
    • 1477 days old (needed 5 days)
• pdfrw (- to 0.4-2.1)
  • Migration status for pdfrw (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdfrw would introduce bugs in testing: #958362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfrw.html
    • autopkgtest for pdfrw/0.4-2.1: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1478 days old (needed 5 days)
• zfec (- to 1.5.2-2.1)
  • Migration status for zfec (- to 1.5.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zfec would introduce bugs in testing: #1055545
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zfec.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1478 days old (needed 5 days)
• golang-github-throttled-throttled (- to 2.2.4-1)
  • Migration status for golang-github-throttled-throttled (- to 2.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-throttled-throttled golang-github-go-redis-redis (not considered)
    • Depends: golang-github-throttled-throttled golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-throttled-throttled.html
    • autopkgtest for golang-github-throttled-throttled/2.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1479 days old (needed 2 days)
• python-ospurge (- to 2.0.0+2019.10.11.git.990287677b-2)
  • Migration status for python-ospurge (- to 2.0.0+2019.10.11.git.990287677b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ospurge would introduce bugs in testing: #1022392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ospurge.html
    • 1481 days old (needed 5 days)
• simulavr (- to 1.0.0+git20160221.e53413b-2)
  • Migration status for simulavr (- to 1.0.0+git20160221.e53413b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simulavr would introduce bugs in testing: #975138
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simulavr.html
    • 1481 days old (needed 5 days)
• check-all-the-things (- to 2017.05.20+nmu1)
  • Migration status for check-all-the-things (- to 2017.05.20+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating check-all-the-things would introduce bugs in testing: #862378
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-all-the-things.html
    • 1484 days old (needed 5 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Depends: golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1497 days old (needed 2 days)
• thawab (- to 4.1-2)
  • Migration status for thawab (- to 4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating thawab would introduce bugs in testing: #990746
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1511 days old (needed 5 days)
• golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2)
  • Migration status for golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-getlantern-errors/0.0~git20190325.abdb3e3-2: amd64: Pass, arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-getlantern-errors golang-github-getlantern-ops
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-errors.html
    • Reproducible on amd64 - info ♻
    • 1515 days old (needed 5 days)
• ruby-coffee-script (- to 2.4.1-2)
  • Migration status for ruby-coffee-script (- to 2.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-coffee-script would introduce bugs in testing: #1019927
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-coffee-script.html
    • autopkgtest for ruby-coffee-script/2.4.1-2: amd64: No tests, superficial or marked flaky ♻ , arm64: No tests, superficial or marked flaky ♻ , armel: No tests, superficial or marked flaky ♻ , armhf: No tests, superficial or marked flaky ♻ , i386: No tests, superficial or marked flaky ♻ , ppc64el: No tests, superficial or marked flaky ♻ , s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1518 days old (needed 5 days)
• gr-dab (- to 0.4-2)
  • Migration status for gr-dab (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gr-dab/amd64 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/amd64 has unsatisfiable dependency
    • gr-dab/arm64 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/arm64 has unsatisfiable dependency
    • gr-dab/armel has unsatisfiable dependency
    • libgnuradio-dab3.8.0/armel has unsatisfiable dependency
    • gr-dab/armhf has unsatisfiable dependency
    • libgnuradio-dab3.8.0/armhf has unsatisfiable dependency
    • gr-dab/i386 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/i386 has unsatisfiable dependency
    • gr-dab/mips64el has unsatisfiable dependency
    • libgnuradio-dab3.8.0/mips64el has unsatisfiable dependency
    • gr-dab/ppc64el has unsatisfiable dependency
    • libgnuradio-dab3.8.0/ppc64el has unsatisfiable dependency
    • gr-dab/s390x has unsatisfiable dependency
    • libgnuradio-dab3.8.0/s390x has unsatisfiable dependency
    • Updating gr-dab would introduce bugs in testing: #1002106, #1031346
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gr-dab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1521 days old (needed 5 days)
• jsunit (- to 0.2.2-2)
  • Migration status for jsunit (- to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsunit would introduce bugs in testing: #974083
    • autopkgtest for jsunit/blocked-on-ci-infra: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsunit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1523 days old (needed 5 days)
• termtris (- to 1.3-1)
  • Migration status for termtris (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating termtris would introduce bugs in testing: #966877
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termtris.html
    • 1528 days old (needed 5 days)
• backup2swift (- to 0.8-1.1)
  • Migration status for backup2swift (- to 0.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backup2swift would introduce bugs in testing: #949942
    • backup2swift unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backup2swift.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1532 days old (needed 5 days)
• gandi-cli (- to 1.5-1)
  • Migration status for gandi-cli (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gandi-cli would introduce bugs in testing: #922420
    • autopkgtest for gandi-cli/1.5-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gandi-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1532 days old (needed 5 days)
• aufs (- to 5.2+20190909-1.1)
  • Migration status for aufs (- to 5.2+20190909-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aufs would introduce bugs in testing: #948087
    • aufs unsatisfiable Build-Depends(-Arch) on amd64: linux-kbuild-5.2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aufs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1537 days old (needed 5 days)
• irsim (- to 9.7.104-1)
  • Migration status for irsim (- to 9.7.104-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating irsim would introduce bugs in testing: #997299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irsim.html
    • 1540 days old (needed 5 days)
• myhdl (- to 0.11-1)
  • Migration status for myhdl (- to 0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating myhdl would introduce bugs in testing: #991212
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/myhdl.html
    • autopkgtest for myhdl/0.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1541 days old (needed 2 days)
• beanbag (- to 1.9.2-1.2)
  • Migration status for beanbag (- to 1.9.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating beanbag would introduce bugs in testing: #977056
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beanbag.html
    • 1542 days old (needed 5 days)
• frozen-flask (- to 0.11-3.1)
  • Migration status for frozen-flask (- to 0.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating frozen-flask would introduce bugs in testing: #1009968, #997354
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frozen-flask.html
    • 1546 days old (needed 5 days)
• python-lepl (- to 5.1.3-2.1)
  • Migration status for python-lepl (- to 5.1.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-lepl would introduce bugs in testing: #950059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lepl.html
    • 1547 days old (needed 5 days)
• socket-activate (- to 0.1-2)
  • Migration status for socket-activate (- to 0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socket-activate would introduce bugs in testing: #922504
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket-activate.html
    • 1555 days old (needed 5 days)
• haskell98-tutorial (- to 200006-2-3)
  • Migration status for haskell98-tutorial (- to 200006-2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell98-tutorial would introduce bugs in testing: #965577
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell98-tutorial.html
    • 1558 days old (needed 5 days)
• python-pyramid-tm (- to 0.5-1.2)
  • Migration status for python-pyramid-tm (- to 0.5-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-pyramid-tm python-pyramid (not considered)
    • Depends: python-pyramid-tm python-pyramid (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-tm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1563 days old (needed 5 days)
• python-pyramid-zcml (- to 1.0.0-1.2)
  • Migration status for python-pyramid-zcml (- to 1.0.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-zcml would introduce bugs in testing: #997353
    • Build-Depends(-Arch): python-pyramid-zcml python-pyramid
    • Depends: python-pyramid-zcml python-pyramid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-zcml.html
    • 1563 days old (needed 5 days)
• python-pyramid-multiauth (- to 0.8.0-1.1)
  • Migration status for python-pyramid-multiauth (- to 0.8.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-multiauth would introduce bugs in testing: #997297
    • Build-Depends(-Arch): python-pyramid-multiauth python-pyramid
    • Depends: python-pyramid-multiauth python-pyramid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-multiauth.html
    • 1566 days old (needed 5 days)
• python-ooolib (- to 0.0.22-5)
  • Migration status for python-ooolib (- to 0.0.22-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ooolib would introduce bugs in testing: #965794
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ooolib.html
    • 1574 days old (needed 5 days)
• drmips (- to 2.0.1-2.1)
  • Migration status for drmips (- to 2.0.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drmips would introduce bugs in testing: #971184
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmips.html
    • 1578 days old (needed 5 days)
• gigedit (- to 1.1.1-1)
  • Migration status for gigedit (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gigedit/amd64 has unsatisfiable dependency
    • gigedit/arm64 has unsatisfiable dependency
    • gigedit/armel has unsatisfiable dependency
    • gigedit/armhf has unsatisfiable dependency
    • gigedit/i386 has unsatisfiable dependency
    • gigedit/mips64el has unsatisfiable dependency
    • gigedit/ppc64el has unsatisfiable dependency
    • gigedit/s390x has unsatisfiable dependency
    • Updating gigedit would introduce bugs in testing: #997203
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gigedit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1578 days old (needed 5 days)
• crypto-policies (- to 20190816git-1)
  • Migration status for crypto-policies (- to 20190816git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crypto-policies.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1579 days old (needed 5 days)
• umlet (- to 13.3-1.3)
  • Migration status for umlet (- to 13.3-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umlet would introduce bugs in testing: #965851
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umlet.html
    • 1580 days old (needed 5 days)
• ca-cacert (- to 2019.0411-2)
  • Migration status for ca-cacert (- to 2019.0411-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ca-cacert would introduce bugs in testing: #988512, #990409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ca-cacert.html
    • 1581 days old (needed 5 days)
• xymon (- to 4.3.30-1)
  • Migration status for xymon (- to 4.3.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xymon would introduce bugs in testing: #999921
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xymon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1581 days old (needed 5 days)
• python-arrayfire (- to 3.3.20160624-3)
  • Migration status for python-arrayfire (- to 3.3.20160624-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-arrayfire arrayfire (not considered)
    • Depends: python-arrayfire arrayfire (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-arrayfire.html
    • autopkgtest for python-arrayfire/3.3.20160624-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1584 days old (needed 2 days)
• svn-load (- to 1.6-1)
  • Migration status for svn-load (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating svn-load would introduce bugs in testing: #1033526
    • autopkgtest for svn-load/1.6-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svn-load.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1587 days old (needed 5 days)
• golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1)
  • Migration status for golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-gocui would introduce bugs in testing: #1032109
    • Build-Depends(-Arch): golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go
    • Depends: golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-gocui.html
    • autopkgtest for golang-github-jesseduffield-gocui/0.3.0+git20190803.ad0cd60-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1590 days old (needed 2 days)
• hydroffice.bag (- to 0.2.15-3)
  • Migration status for hydroffice.bag (- to 0.2.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hydroffice.bag would introduce bugs in testing: #993003
    • autopkgtest for hydroffice.bag/0.2.15-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydroffice.bag.html
    • 1594 days old (needed 5 days)
• esniper (- to 2.35.0+git20190805.7930bb4-1)
  • Migration status for esniper (- to 2.35.0+git20190805.7930bb4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating esniper would introduce bugs in testing: #855461
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esniper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1602 days old (needed 5 days)
• simple-obfs (- to 0.0.5-6)
  • Migration status for simple-obfs (- to 0.0.5-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simple-obfs shadowsocks-libev (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simple-obfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1604 days old (needed 5 days)
• gertty (- to 1.6.0-1)
  • Migration status for gertty (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gertty would introduce bugs in testing: #1054007
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gertty.html
    • autopkgtest for gertty/1.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1608 days old (needed 2 days)
• rust-pbr (- to 1.0.1-1)
  • Migration status for rust-pbr (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-pbr would introduce bugs in testing: #1053638
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pbr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1612 days old (needed 5 days)
• squirrel3 (- to 3.1-8)
  • Migration status for squirrel3 (- to 3.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squirrel3 would introduce bugs in testing: #1014539, #997441
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squirrel3.html
    • 1620 days old (needed 5 days)
• profitbricks-sdk-python (- to 4.1.3-3)
  • Migration status for profitbricks-sdk-python (- to 4.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating profitbricks-sdk-python would introduce bugs in testing: #1020092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profitbricks-sdk-python.html
    • 1629 days old (needed 5 days)
• versiontools (- to 1.9.1-4)
  • Migration status for versiontools (- to 1.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating versiontools would introduce bugs in testing: #1054736, #1056537
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/versiontools.html
    • autopkgtest for versiontools/1.9.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1629 days old (needed 2 days)
• nbibtex (- to 0.9.18-13)
  • Migration status for nbibtex (- to 0.9.18-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nbibtex would introduce bugs in testing: #1030454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbibtex.html
    • 1632 days old (needed 5 days)
• hipspy (- to 0.2-3)
  • Migration status for hipspy (- to 0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hipspy would introduce bugs in testing: #1012277
    • autopkgtest for hipspy/0.2-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hipspy.html
    • 1635 days old (needed 5 days)
• opencollada (- to 0.1.0~20180719.619d942+dfsg0-2)
  • Migration status for opencollada (- to 0.1.0~20180719.619d942+dfsg0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opencollada would introduce bugs in testing: #1000009, #1037799
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencollada.html
    • Reproducible on i386 - info ♻
    • 1644 days old (needed 5 days)
• pluginhook (- to 0~20150216.0~a320158-2.1)
  • Migration status for pluginhook (- to 0~20150216.0~a320158-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pluginhook would introduce bugs in testing: #972915
    • pluginhook/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • pluginhook/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluginhook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1654 days old (needed 5 days)
• averell (- to 1.2.5-1.1)
  • Migration status for averell (- to 1.2.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): averell erlang-cowboy (not considered)
    • Depends: averell erlang-cowboy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/averell.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 1690 days old (needed 5 days)
• libapache2-mod-defensible (- to 1.4-3.2)
  • Migration status for libapache2-mod-defensible (- to 1.4-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-defensible would introduce bugs in testing: #965622, #998981
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-defensible.html
    • 1691 days old (needed 5 days)
• megadown (- to 0~20180705+git83c53dd-1.1)
  • Migration status for megadown (- to 0~20180705+git83c53dd-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating megadown would introduce bugs in testing: #1007941, #969885
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/megadown.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1699 days old (needed 5 days)
• golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1)
  • Migration status for golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by micah, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-ops.html
    • autopkgtest for golang-github-getlantern-ops/0.0~git20190325.d70cb0d-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1726 days old (needed 2 days)
• nagzilla (- to 2.0-1.1)
  • Migration status for nagzilla (- to 2.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nagzilla libnet-jabber-perl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nagzilla.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1735 days old (needed 5 days)
• ricochet-im (- to 1.1.4-3)
  • Migration status for ricochet-im (- to 1.1.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ricochet-im would introduce bugs in testing: #992668
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ricochet-im.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1749 days old (needed 5 days)
• x2godesktopsharing (- to 3.2.0.0-2)
  • Migration status for x2godesktopsharing (- to 3.2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2godesktopsharing x2goserver (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2godesktopsharing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1752 days old (needed 5 days)
• pyfr (- to 1.5.0-3)
  • Migration status for pyfr (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfr would introduce bugs in testing: #997427
    • autopkgtest for pyfr/1.5.0-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfr.html
    • 1768 days old (needed 5 days)
• aufs-tools (- to 1:4.14+20190211-1)
  • Migration status for aufs-tools (- to 1:4.14+20190211-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aufs-tools would introduce bugs in testing: #943332
    • Build-Depends(-Arch): aufs-tools aufs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aufs-tools.html
    • 1775 days old (needed 5 days)
• libapache2-mod-auth-cas (- to 1.2-1)
  • Migration status for libapache2-mod-auth-cas (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-auth-cas would introduce bugs in testing: #1000068
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-cas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1786 days old (needed 5 days)
• whitedune (- to 0.30.10-2.2)
  • Migration status for whitedune (- to 0.30.10-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whitedune would introduce bugs in testing: #1036881
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitedune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1789 days old (needed 5 days)
• erlang-ranch (- to 1.3.0-2)
  • Migration status for erlang-ranch (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating erlang-ranch would introduce bugs in testing: #980951
    • Not built on buildd: arch amd64 binaries uploaded by iwamatsu
    • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-ranch.html
    • 1791 days old (needed 5 days)
• diaspora (- to 0.7.9.0+dfsg-4)
  • Migration status for diaspora (- to 0.7.9.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • diaspora/amd64 has unsatisfiable dependency
    • diaspora/arm64 has unsatisfiable dependency
    • Updating diaspora would introduce bugs in testing: #924109, #974014
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/diaspora.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1793 days old (needed 5 days)
• node-trust-webcrypto (- to 0.9.2-1)
  • Migration status for node-trust-webcrypto (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-trust-webcrypto would introduce bugs in testing: #1002262
    • autopkgtest for node-trust-webcrypto/0.9.2-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-trust-webcrypto.html
    • 1795 days old (needed 5 days)
• sqwebmail-de (- to 6.0.0-1)
  • Migration status for sqwebmail-de (- to 6.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sqwebmail-de courier (not considered)
    • Built-Using: sqwebmail-de courier (not considered)
    • Depends: sqwebmail-de courier (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqwebmail-de.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1805 days old (needed 5 days)
• asterisk-espeak (- to 5.0~1-3)
  • Migration status for asterisk-espeak (- to 5.0~1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • asterisk-espeak/amd64 has unsatisfiable dependency
    • asterisk-espeak/arm64 has unsatisfiable dependency
    • asterisk-espeak/armel has unsatisfiable dependency
    • asterisk-espeak/armhf has unsatisfiable dependency
    • asterisk-espeak/i386 has unsatisfiable dependency
    • asterisk-espeak/mips64el has unsatisfiable dependency
    • asterisk-espeak/ppc64el has unsatisfiable dependency
    • asterisk-espeak/s390x has unsatisfiable dependency
    • Updating asterisk-espeak would introduce bugs in testing: #1035547, #947510
    • Build-Depends(-Arch): asterisk-espeak asterisk
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/asterisk-espeak.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1812 days old (needed 5 days)
• fonts-alegreya-sans (- to 2.008-1)
  • Migration status for fonts-alegreya-sans (- to 2.008-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-alegreya-sans would introduce bugs in testing: #944499
    • Not built on buildd: arch all binaries uploaded by jeremy@bicha.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-alegreya-sans.html
    • 1814 days old (needed 5 days)
• yorick-full (- to 2.2.04+dfsg1+full)
  • Migration status for yorick-full (- to 2.2.04+dfsg1+full): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: yorick-full yorick-ynfft (not considered)
    • Invalidated by dependency
    • Depends: yorick-full yorick-mira
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-full.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1815 days old (needed 5 days)
• minify-maven-plugin (- to 1.7.4-1.1)
  • Migration status for minify-maven-plugin (- to 1.7.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating minify-maven-plugin would introduce bugs in testing: #1006451
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minify-maven-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1819 days old (needed 5 days)
• gozer (- to 0.7.nofont.1-7)
  • Migration status for gozer (- to 0.7.nofont.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gozer giblib (not considered)
    • Depends: gozer giblib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gozer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1820 days old (needed 5 days)
• pgcharts (- to 1.0+2017-09-16-1)
  • Migration status for pgcharts (- to 1.0+2017-09-16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgcharts would introduce bugs in testing: #1024642
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1820 days old (needed 5 days)
• vibe.d (- to 0.8.4-2)
  • Migration status for vibe.d (- to 0.8.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libvibe-core0/amd64 has unsatisfiable dependency
    • libvibe-crypto0/amd64 has unsatisfiable dependency
    • libvibe-data0/amd64 has unsatisfiable dependency
    • libvibe-http0/amd64 has unsatisfiable dependency
    • libvibe-inet0/amd64 has unsatisfiable dependency
    • libvibe-mail0/amd64 has unsatisfiable dependency
    • libvibe-mongodb0/amd64 has unsatisfiable dependency
    • libvibe-redis0/amd64 has unsatisfiable dependency
    • libvibe-stream0/amd64 has unsatisfiable dependency
    • libvibe-textfilter0/amd64 has unsatisfiable dependency
    • libvibe-tls0/amd64 has unsatisfiable dependency
    • libvibe-utils0/amd64 has unsatisfiable dependency
    • libvibe-web0/amd64 has unsatisfiable dependency
    • libvibe-core0/arm64 has unsatisfiable dependency
    • libvibe-crypto0/arm64 has unsatisfiable dependency
    • libvibe-data0/arm64 has unsatisfiable dependency
    • libvibe-http0/arm64 has unsatisfiable dependency
    • libvibe-inet0/arm64 has unsatisfiable dependency
    • libvibe-mail0/arm64 has unsatisfiable dependency
    • libvibe-mongodb0/arm64 has unsatisfiable dependency
    • libvibe-redis0/arm64 has unsatisfiable dependency
    • libvibe-stream0/arm64 has unsatisfiable dependency
    • libvibe-textfilter0/arm64 has unsatisfiable dependency
    • libvibe-tls0/arm64 has unsatisfiable dependency
    • libvibe-utils0/arm64 has unsatisfiable dependency
    • libvibe-web0/arm64 has unsatisfiable dependency
    • libvibe-core0/armhf has unsatisfiable dependency
    • libvibe-crypto0/armhf has unsatisfiable dependency
    • libvibe-data0/armhf has unsatisfiable dependency
    • libvibe-http0/armhf has unsatisfiable dependency
    • libvibe-inet0/armhf has unsatisfiable dependency
    • libvibe-mail0/armhf has unsatisfiable dependency
    • libvibe-mongodb0/armhf has unsatisfiable dependency
    • libvibe-redis0/armhf has unsatisfiable dependency
    • libvibe-stream0/armhf has unsatisfiable dependency
    • libvibe-textfilter0/armhf has unsatisfiable dependency
    • libvibe-tls0/armhf has unsatisfiable dependency
    • libvibe-utils0/armhf has unsatisfiable dependency
    • libvibe-web0/armhf has unsatisfiable dependency
    • libvibe-core0/i386 has unsatisfiable dependency
    • libvibe-crypto0/i386 has unsatisfiable dependency
    • libvibe-data0/i386 has unsatisfiable dependency
    • libvibe-http0/i386 has unsatisfiable dependency
    • libvibe-inet0/i386 has unsatisfiable dependency
    • libvibe-mail0/i386 has unsatisfiable dependency
    • libvibe-mongodb0/i386 has unsatisfiable dependency
    • libvibe-redis0/i386 has unsatisfiable dependency
    • libvibe-stream0/i386 has unsatisfiable dependency
    • libvibe-textfilter0/i386 has unsatisfiable dependency
    • libvibe-tls0/i386 has unsatisfiable dependency
    • libvibe-utils0/i386 has unsatisfiable dependency
    • libvibe-web0/i386 has unsatisfiable dependency
    • Updating vibe.d would introduce bugs in testing: #941453
    • vibe.d unsatisfiable Build-Depends(-Arch) on amd64: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on arm64: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on armhf: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on i386: libstdx-allocator-dev (>= 2.77.2)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vibe.d.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1821 days old (needed 5 days)
• kpatch (- to 0.6.0-0.2)
  • Migration status for kpatch (- to 0.6.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kpatch would introduce bugs in testing: #1027889, #983648, #991003
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/k/kpatch.html
  • Additional info:
    • 1825 days old (needed 5 days)
• pdfgrep (- to 2.1.2-1)
  • Migration status for pdfgrep (- to 2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdfgrep would introduce bugs in testing: #1000003
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfgrep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1825 days old (needed 5 days)
• vorbis-java (- to 0.8-3)
  • Migration status for vorbis-java (- to 0.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vorbis-java tika (not considered)
    • Depends: vorbis-java tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vorbis-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1826 days old (needed 5 days)
• xsok (- to 1.02-19)
  • Migration status for xsok (- to 1.02-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xsok would introduce bugs in testing: #1056146
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsok.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1828 days old (needed 5 days)
• ruby-arel (- to 9.0.0-2)
  • Migration status for ruby-arel (- to 9.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-arel would introduce bugs in testing: #1039034
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arel.html
    • autopkgtest for ruby-arel/9.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1829 days old (needed 2 days)
• resteasy (- to 3.6.2-2)
  • Migration status for resteasy (- to 3.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resteasy would introduce bugs in testing: #879469
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resteasy.html
    • 1831 days old (needed 5 days)
• mpqc3 (- to 0.0~git20170114-4.1)
  • Migration status for mpqc3 (- to 0.0~git20170114-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mpqc3/amd64 has unsatisfiable dependency
    • mpqc3/arm64 has unsatisfiable dependency
    • mpqc3/armel has unsatisfiable dependency
    • mpqc3/armhf has unsatisfiable dependency
    • mpqc3/i386 has unsatisfiable dependency
    • mpqc3/mips64el has unsatisfiable dependency
    • mpqc3/ppc64el has unsatisfiable dependency
    • Updating mpqc3 would introduce bugs in testing: #946452
    • Build-Depends(-Arch): mpqc3 tiledarray
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mpqc3.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1847 days old (needed 5 days)
• evqueue-core (- to 2.1-1)
  • Migration status for evqueue-core (- to 2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating evqueue-core would introduce bugs in testing: #1000087, #914801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/evqueue-core.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1881 days old (needed 5 days)
• flightgear-phi (- to 2018.1.1+dfsg1-1.1)
  • Migration status for flightgear-phi (- to 2018.1.1+dfsg1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flightgear-phi would introduce bugs in testing: #979902
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flightgear-phi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1886 days old (needed 5 days)
• spout (- to 1.4-4)
  • Migration status for spout (- to 1.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spout would introduce bugs in testing: #957838
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spout.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1888 days old (needed 5 days)
• mxt-app (- to 1.28-2)
  • Migration status for mxt-app (- to 1.28-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mxt-app would introduce bugs in testing: #952059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mxt-app.html
    • 1889 days old (needed 5 days)
• amp (- to 0.6.1-1)
  • Migration status for amp (- to 0.6.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): amp python-ase (not considered)
    • Depends: amp python-ase (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amp.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1896 days old (needed 5 days)
• gauche-gl (- to 0.6-4)
  • Migration status for gauche-gl (- to 0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche-gl gauche (not considered)
    • Depends: gauche-gl gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche-gl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1903 days old (needed 5 days)
• swfmill (- to 0.3.6-1)
  • Migration status for swfmill (- to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swfmill would introduce bugs in testing: #1019600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swfmill.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1912 days old (needed 5 days)
• aws-shell (- to 0.2.1-1)
  • Migration status for aws-shell (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aws-shell/amd64 has unsatisfiable dependency
    • aws-shell/arm64 has unsatisfiable dependency
    • Updating aws-shell would introduce bugs in testing: #1050402, #944542
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/aws-shell.html
    • aws-shell unsatisfiable Build-Depends(-Arch) on amd64: awscli (<< 2.0.0)
    • Not built on buildd: arch all binaries uploaded by takaki, a new source-only upload is needed to allow migration
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1920 days old (needed 5 days)
• darcs-monitor (- to 0.4.2-14)
  • Migration status for darcs-monitor (- to 0.4.2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs-monitor would introduce bugs in testing: #1057792
    • Depends: darcs-monitor darcs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darcs-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1923 days old (needed 5 days)
• dublin-traceroute (- to 0.4.2-2)
  • Migration status for dublin-traceroute (- to 0.4.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dublin-traceroute libtins (not considered)
    • Depends: dublin-traceroute libtins (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dublin-traceroute.html
    • 1927 days old (needed 5 days)
• mozilla-noscript (- to 10.1.9.6-2)
  • Migration status for mozilla-noscript (- to 10.1.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mozilla-noscript would introduce bugs in testing: #922396
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mozilla-noscript.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1930 days old (needed 5 days)
• libtins (- to 4.0-1)
  • Migration status for libtins (- to 4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtins would introduce bugs in testing: #1037629
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtins.html
    • Reproducible on i386 - info ♻
    • 1931 days old (needed 5 days)
• newmat (- to 1.10.4-8)
  • Migration status for newmat (- to 1.10.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newmat would introduce bugs in testing: #1052790
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newmat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1932 days old (needed 5 days)
• clearlooks-phenix-theme (- to 7.0.1-3)
  • Migration status for clearlooks-phenix-theme (- to 7.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clearlooks-phenix-theme would introduce bugs in testing: #961834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clearlooks-phenix-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1940 days old (needed 5 days)
• bdfproxy (- to 0.3.9-3)
  • Migration status for bdfproxy (- to 0.3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bdfproxy would introduce bugs in testing: #1033923
    • autopkgtest for bdfproxy/0.3.9-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Depends: bdfproxy backdoor-factory
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdfproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1943 days old (needed 5 days)
• ruby-yaml-db (- to 0.7.0-1)
  • Migration status for ruby-yaml-db (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-yaml-db would introduce bugs in testing: #1019679
    • autopkgtest for ruby-yaml-db/0.7.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-yaml-db.html
    • 1969 days old (needed 5 days)
• lief (- to 0.9.0-1)
  • Migration status for lief (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lief would introduce bugs in testing: #1037752
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lief.html
    • Reproducible on i386 - info ♻
    • 1984 days old (needed 5 days)
• openmx (- to 3.8.5+dfsg1-1)
  • Migration status for openmx (- to 3.8.5+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openmx would introduce bugs in testing: #957639
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmx.html
    • 1987 days old (needed 5 days)
• vowpal-wabbit (- to 8.6.1.dfsg1-1)
  • Migration status for vowpal-wabbit (- to 8.6.1.dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vowpal-wabbit would introduce bugs in testing: #836450, #893031
    • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vowpal-wabbit.html
    • 1989 days old (needed 5 days)
• sus (- to 7.20180621)
  • Migration status for sus (- to 7.20180621): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sus would introduce bugs in testing: #968415
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2025 days old (needed 5 days)
• soundmanager2 (- to 2.97a.20150601+dfsg2-2)
  • Migration status for soundmanager2 (- to 2.97a.20150601+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating soundmanager2 would introduce bugs in testing: #1031482
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundmanager2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 2028 days old (needed 5 days)
• xqilla (- to 2.3.4-1)
  • Migration status for xqilla (- to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xqilla would introduce bugs in testing: #1040163, #984418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xqilla.html
    • 2030 days old (needed 5 days)
• erlang-cowboy (- to 2.0.0~pre.1+dfsg1-4)
  • Migration status for erlang-cowboy (- to 2.0.0~pre.1+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by iwamatsu
    • Not built on buildd: arch all binaries uploaded by iwamatsu, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): erlang-cowboy erlang-ranch
    • Depends: erlang-cowboy erlang-ranch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-cowboy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2040 days old (needed 5 days)
• tinyjsd (- to 1.2+git1-1)
  • Migration status for tinyjsd (- to 1.2+git1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinyjsd would introduce bugs in testing: #971774
    • Not built on buildd: arch all binaries uploaded by dkg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinyjsd.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2041 days old (needed 5 days)
• golang-github-coreos-go-tspi (- to 0.1.1-2)
  • Migration status for golang-github-coreos-go-tspi (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-coreos-go-tspi would introduce bugs in testing: #849665
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coreos-go-tspi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2092 days old (needed 5 days)
• mldemos (- to 0.5.1+git.1.ee5d11f-4)
  • Migration status for mldemos (- to 0.5.1+git.1.ee5d11f-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mldemos would introduce bugs in testing: #915711, #922585
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mldemos.html
    • 2093 days old (needed 5 days)
• z88 (- to 13.0.0+dfsg2-6)
  • Migration status for z88 (- to 13.0.0+dfsg2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): z88 gtkglext (not considered)
    • Depends: z88 gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/z88.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2095 days old (needed 5 days)
• debbugs (- to 2.6.0)
  • Migration status for debbugs (- to 2.6.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debbugs would introduce bugs in testing: #903413
    • autopkgtest for debbugs/2.6.0: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by don, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debbugs.html
    • 2112 days old (needed 5 days)
• xymonq (- to 0.8-1)
  • Migration status for xymonq (- to 0.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: xymonq xymon (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xymonq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2147 days old (needed 5 days)
• librsl (- to 1.43-1.2)
  • Migration status for librsl (- to 1.43-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating librsl would introduce bugs in testing: #893023
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librsl.html
    • 2162 days old (needed 5 days)
• ignore-me (- to 0.1.2-1)
  • Migration status for ignore-me (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ignore-me would introduce bugs in testing: #912037, #948875
    • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ignore-me.html
    • 2188 days old (needed 5 days)
• boinc-app-eah-brp (- to 0.20170426+dfsg-10)
  • Migration status for boinc-app-eah-brp (- to 0.20170426+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • boinc-app-eah-brp/amd64 has unsatisfiable dependency
    • boinc-app-eah-brp/arm64 has unsatisfiable dependency
    • boinc-app-eah-brp/armel has unsatisfiable dependency
    • boinc-app-eah-brp/armhf has unsatisfiable dependency
    • boinc-app-eah-brp/i386 has unsatisfiable dependency
    • boinc-app-eah-brp/mips64el has unsatisfiable dependency
    • boinc-app-eah-brp/ppc64el has unsatisfiable dependency
    • boinc-app-eah-brp/s390x has unsatisfiable dependency
    • Updating boinc-app-eah-brp would introduce bugs in testing: #887880, #949603
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on amd64: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on arm64: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armel: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armhf: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on i386: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on mips64el: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on ppc64el: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on s390x: g++-5 | g++ (<< 6)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/boinc-app-eah-brp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2189 days old (needed 5 days)
• debirf (- to 0.38)
  • Migration status for debirf (- to 0.38): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debirf would introduce bugs in testing: #901779, #969938
    • autopkgtest for debirf/0.38: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debirf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2189 days old (needed 5 days)
• pagetools (- to 0.1-3)
  • Migration status for pagetools (- to 0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pagetools/amd64 has unsatisfiable dependency
    • pagetools/arm64 has unsatisfiable dependency
    • pagetools/armel has unsatisfiable dependency
    • pagetools/armhf has unsatisfiable dependency
    • pagetools/i386 has unsatisfiable dependency
    • pagetools/mips64el has unsatisfiable dependency
    • pagetools/ppc64el has unsatisfiable dependency
    • pagetools/s390x has unsatisfiable dependency
    • Updating pagetools would introduce bugs in testing: #1012690
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pagetools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2192 days old (needed 5 days)
• khronos-opengl-man4 (- to 1.0~svn33624-1)
  • Migration status for khronos-opengl-man4 (- to 1.0~svn33624-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): khronos-opengl-man4 w3-dtd-mathml (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opengl-man4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2195 days old (needed 5 days)
• jajuk (- to 1:1.10.9+dfsg2-4)
  • Migration status for jajuk (- to 1:1.10.9+dfsg2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jajuk would introduce bugs in testing: #923330
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jajuk.html
    • 2230 days old (needed 5 days)
• php-enum (- to 2.3.1-1)
  • Migration status for php-enum (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-enum would introduce bugs in testing: #882928
    • autopkgtest for php-enum/2.3.1-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-enum.html
    • 2245 days old (needed 5 days)
• octicons (- to 4.4.0-2)
  • Migration status for octicons (- to 4.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octicons would introduce bugs in testing: #883107
    • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octicons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2264 days old (needed 5 days)
• libcypher-parser (- to 0.6.0-1)
  • Migration status for libcypher-parser (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcypher-parser would introduce bugs in testing: #1012975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcypher-parser.html
    • 2286 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liburweb0/ppc64el has unsatisfiable dependency
    • Updating urweb would introduce bugs in testing: #1060107
    • Build-Depends(-Arch): urweb mlton
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 2302 days old (needed 5 days)
• opengrm-ngram (- to 1.3.2-3)
  • Migration status for opengrm-ngram (- to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libngram-tools/amd64 has unsatisfiable dependency
    • libngram2/amd64 has unsatisfiable dependency
    • libngram-tools/arm64 has unsatisfiable dependency
    • libngram2/arm64 has unsatisfiable dependency
    • libngram-tools/armel has unsatisfiable dependency
    • libngram2/armel has unsatisfiable dependency
    • libngram-tools/armhf has unsatisfiable dependency
    • libngram2/armhf has unsatisfiable dependency
    • libngram-tools/i386 has unsatisfiable dependency
    • libngram2/i386 has unsatisfiable dependency
    • libngram-tools/mips64el has unsatisfiable dependency
    • libngram2/mips64el has unsatisfiable dependency
    • libngram-tools/ppc64el has unsatisfiable dependency
    • libngram2/ppc64el has unsatisfiable dependency
    • libngram-tools/s390x has unsatisfiable dependency
    • libngram2/s390x has unsatisfiable dependency
    • Updating opengrm-ngram would introduce bugs in testing: #1019172
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/opengrm-ngram.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2314 days old (needed 5 days)
• guidedog (- to 1.3.0-1)
  • Migration status for guidedog (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guidedog would introduce bugs in testing: #1025571
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guidedog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2344 days old (needed 5 days)
• golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1)
  • Migration status for golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-minio-cli would introduce bugs in testing: #869190
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-minio-cli.html
    • 2369 days old (needed 5 days)
• golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1)
  • Migration status for golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-gopkg-mcuadros-go-syslog.v2 would introduce bugs in testing: #954514
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-mcuadros-go-syslog.v2.html
    • 2374 days old (needed 5 days)
• ants (- to 2.1.0-5)
  • Migration status for ants (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ants/amd64 has unsatisfiable dependency
    • ants/i386 has unsatisfiable dependency
    • Updating ants would introduce bugs in testing: #872741, #909833
    • ants unsatisfiable Build-Depends(-Arch) on amd64: libinsighttoolkit4-dev (>> 4.7.0~)
    • ants unsatisfiable Build-Depends(-Arch) on i386: libinsighttoolkit4-dev (>> 4.7.0~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/ants.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 2495 days old (needed 5 days)
• yorick-mira (- to 1.1.0+git20170124.3bd1c3~dfsg1-2)
  • Migration status for yorick-mira (- to 1.1.0+git20170124.3bd1c3~dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: yorick-mira yorick-ynfft (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-mira.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2498 days old (needed 5 days)
• irssi-plugin-robustirc (- to 0.6-4)
  • Migration status for irssi-plugin-robustirc (- to 0.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating irssi-plugin-robustirc would introduce bugs in testing: #1015080
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irssi-plugin-robustirc.html
    • 2511 days old (needed 5 days)
• freebsd-libs (- to 10.3~svn296373-10)
  • Migration status for freebsd-libs (- to 10.3~svn296373-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by steven@pyro.eu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): freebsd-libs freebsd-buildutils
    • Build-Depends(-Arch): freebsd-libs freebsd-glue
    • Depends: freebsd-libs freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 2528 days old (needed 5 days)
• lilyterm (- to 0.9.9.4+git20150208.f600c0-5)
  • Migration status for lilyterm (- to 0.9.9.4+git20150208.f600c0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lilyterm would introduce bugs in testing: #970419
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lilyterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2540 days old (needed 5 days)
• bookkeeper (- to 4.4.0-1)
  • Migration status for bookkeeper (- to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bookkeeper would introduce bugs in testing: #906340
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookkeeper.html
    • 2546 days old (needed 5 days)
• gcc-msp430 (- to 4.6.3~mspgcc-20120406-7.1)
  • Migration status for gcc-msp430 (- to 4.6.3~mspgcc-20120406-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-msp430 would introduce bugs in testing: #965541
    • Build-Depends(-Arch): gcc-msp430 binutils-msp430
    • Depends: gcc-msp430 binutils-msp430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-msp430.html
    • 2549 days old (needed 5 days)
• gdb-msp430 (- to 7.2a~mspgcc-20111205-3.1)
  • Migration status for gdb-msp430 (- to 7.2a~mspgcc-20111205-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdb-msp430 would introduce bugs in testing: #965545, #999284
    • Build-Depends(-Arch): gdb-msp430 binutils-msp430
    • Depends: gdb-msp430 binutils-msp430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdb-msp430.html
    • 2549 days old (needed 5 days)
• origami (- to 1.2.7+really0.7.4-1.1)
  • Migration status for origami (- to 1.2.7+really0.7.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating origami would introduce bugs in testing: #953144
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/origami.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2549 days old (needed 5 days)
• gli (- to 0.8.2.0+ds1-2)
  • Migration status for gli (- to 0.8.2.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gli would introduce bugs in testing: #888933
    • autopkgtest for gli/0.8.2.0+ds1-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gli.html
    • 2550 days old (needed 5 days)
• rdup (- to 1.1.15-1)
  • Migration status for rdup (- to 1.1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rdup/amd64 has unsatisfiable dependency
    • rdup/arm64 has unsatisfiable dependency
    • rdup/armel has unsatisfiable dependency
    • rdup/armhf has unsatisfiable dependency
    • rdup/i386 has unsatisfiable dependency
    • rdup/mips64el has unsatisfiable dependency
    • rdup/ppc64el has unsatisfiable dependency
    • rdup/s390x has unsatisfiable dependency
    • Updating rdup would introduce bugs in testing: #941101, #999975
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rdup.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2554 days old (needed 5 days)
• verilog-mode (- to 20161124.fd230e6-2)
  • Migration status for verilog-mode (- to 20161124.fd230e6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verilog-mode would introduce bugs in testing: #934977
    • verilog-mode unsatisfiable Build-Depends(-Arch) on amd64: emacs25
    • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilog-mode.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2559 days old (needed 5 days)
• ruby-celluloid-io (- to 0.16.2-5)
  • Migration status for ruby-celluloid-io (- to 0.16.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-celluloid-io would introduce bugs in testing: #1031476
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-celluloid-io.html
    • autopkgtest for ruby-celluloid-io/0.16.2-5: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on i386 - info ♻
    • 2569 days old (needed 5 days)
• ruby-uglifier (- to 2.7.2+dfsg-2)
  • Migration status for ruby-uglifier (- to 2.7.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-uglifier would introduce bugs in testing: #981224
    • autopkgtest for ruby-uglifier/2.7.2+dfsg-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-uglifier.html
    • 2580 days old (needed 5 days)
• golang-github-tsenart-tb (- to 0.0~git20151208.0.19f4c3d-2)
  • Migration status for golang-github-tsenart-tb (- to 0.0~git20151208.0.19f4c3d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-tsenart-tb would introduce bugs in testing: #964048
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tsenart-tb.html
    • 2593 days old (needed 5 days)
• powermock (- to 1.6.6-1)
  • Migration status for powermock (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating powermock would introduce bugs in testing: #875358
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powermock.html
    • 2612 days old (needed 5 days)
• kryo-serializers (- to 0.22-3)
  • Migration status for kryo-serializers (- to 0.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kryo-serializers would introduce bugs in testing: #875594
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kryo-serializers.html
    • 2657 days old (needed 5 days)
• arrayfire (- to 3.3.2+dfsg1-4)
  • Migration status for arrayfire (- to 3.3.2+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating arrayfire would introduce bugs in testing: #892288, #897707
    • autopkgtest for arrayfire/3.3.2+dfsg1-4: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): arrayfire clblas
    • Depends: arrayfire clblas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arrayfire.html
    • 2699 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libedasqlite0/amd64 has unsatisfiable dependency
    • libedasqlite0/arm64 has unsatisfiable dependency
    • libedasqlite0/armel has unsatisfiable dependency
    • libedasqlite0/armhf has unsatisfiable dependency
    • libecere0/i386 has unsatisfiable dependency
    • libedasqlite0/i386 has unsatisfiable dependency
    • libedasqlite0/mips64el has unsatisfiable dependency
    • libedasqlite0/ppc64el has unsatisfiable dependency
    • libedasqlite0/s390x has unsatisfiable dependency
    • Updating ecere-sdk would introduce bugs in testing: #898832, #995050
    • Build-Depends(-Arch): ecere-sdk mesa
    • Build-Depends(-Arch): ecere-sdk upx-ucl
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/ecere-sdk.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2710 days old (needed 5 days)
• xorp (- to 1.8.6~wip.20160715-2)
  • Migration status for xorp (- to 1.8.6~wip.20160715-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xorp/amd64 has unsatisfiable dependency
    • xorp/i386 has unsatisfiable dependency
    • xorp/ppc64el has unsatisfiable dependency
    • xorp/s390x has unsatisfiable dependency
    • Updating xorp would introduce bugs in testing: #947586, #958600
    • xorp unsatisfiable Build-Depends(-Arch) on amd64: dh-systemd
    • xorp unsatisfiable Build-Depends(-Arch) on i386: dh-systemd
    • xorp unsatisfiable Build-Depends(-Arch) on ppc64el: dh-systemd
    • xorp unsatisfiable Build-Depends(-Arch) on s390x: dh-systemd
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xorp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2723 days old (needed 5 days)
• grip (- to 4.2.0-3)
  • Migration status for grip (- to 4.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grip would introduce bugs in testing: #1025825, #953967
    • autopkgtest for grip/4.2.0-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grip.html
    • 2742 days old (needed 5 days)
• libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1)
  • Migration status for libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-mupen64plus would introduce bugs in testing: #935282, #976078
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-mupen64plus.html
    • 2763 days old (needed 5 days)
• glosstex (- to 0.4.dfsg.1-4)
  • Migration status for glosstex (- to 0.4.dfsg.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glosstex would introduce bugs in testing: #1052914
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glosstex.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2767 days old (needed 5 days)
• elektra (- to 0.8.14-5.1)
  • Migration status for elektra (- to 0.8.14-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elektra-tests/amd64 has unsatisfiable dependency
    • libelektra4-python/amd64 has unsatisfiable dependency
    • python3-elektra/amd64 has unsatisfiable dependency
    • elektra-tests/arm64 has unsatisfiable dependency
    • libelektra4-python/arm64 has unsatisfiable dependency
    • python3-elektra/arm64 has unsatisfiable dependency
    • elektra-tests/armel has unsatisfiable dependency
    • libelektra4-python/armel has unsatisfiable dependency
    • python3-elektra/armel has unsatisfiable dependency
    • elektra-tests/armhf has unsatisfiable dependency
    • libelektra4-python/armhf has unsatisfiable dependency
    • python3-elektra/armhf has unsatisfiable dependency
    • elektra-tests/i386 has unsatisfiable dependency
    • libelektra4-python/i386 has unsatisfiable dependency
    • python3-elektra/i386 has unsatisfiable dependency
    • elektra-tests/mips64el has unsatisfiable dependency
    • libelektra4-python/mips64el has unsatisfiable dependency
    • python3-elektra/mips64el has unsatisfiable dependency
    • elektra-tests/ppc64el has unsatisfiable dependency
    • libelektra4-python/ppc64el has unsatisfiable dependency
    • python3-elektra/ppc64el has unsatisfiable dependency
    • elektra-tests/s390x has unsatisfiable dependency
    • libelektra4-python/s390x has unsatisfiable dependency
    • python3-elektra/s390x has unsatisfiable dependency
    • Updating elektra would introduce bugs in testing: #844145, #846200, #851592, #881676, #956949
    • elektra unsatisfiable Build-Depends(-Arch) on amd64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on arm64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armel: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armhf: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on i386: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on mips64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on ppc64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on s390x: swig3.0
    • Not built on buildd: arch amd64 binaries uploaded by aeb
    • Not built on buildd: arch all binaries uploaded by aeb, a new source-only upload is needed to allow migration
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/elektra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2773 days old (needed 5 days)
• php-sabre-xml (- to 1.4.2-1)
  • Migration status for php-sabre-xml (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-xml would introduce bugs in testing: #882949
    • autopkgtest for php-sabre-xml/1.4.2-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabre-xml php-sabre-uri
    • Depends: php-sabre-xml php-sabre-uri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-xml.html
    • 2787 days old (needed 5 days)
• twofish (- to 0.3-5)
  • Migration status for twofish (- to 0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating twofish would introduce bugs in testing: #997617
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twofish.html
    • 2794 days old (needed 5 days)
• php-sabre-uri (- to 1.1.0-1)
  • Migration status for php-sabre-uri (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-uri would introduce bugs in testing: #882923
    • autopkgtest for php-sabre-uri/1.1.0-1: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-uri.html
    • 2850 days old (needed 5 days)
• php-sabre-http (- to 4.2.1-3)
  • Migration status for php-sabre-http (- to 4.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-http would introduce bugs in testing: #882935
    • autopkgtest for php-sabre-http/4.2.1-3: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabre-http php-sabre-event
    • Build-Depends(-Arch): php-sabre-http php-sabre-uri
    • Depends: php-sabre-http php-sabre-event
    • Depends: php-sabre-http php-sabre-uri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-http.html
    • 2856 days old (needed 5 days)
• php-sabre-event (- to 3.0.0~as2.0.2-2)
  • Migration status for php-sabre-event (- to 3.0.0~as2.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-event would introduce bugs in testing: #882915
    • autopkgtest for php-sabre-event/3.0.0~as2.0.2-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-event.html
    • 2864 days old (needed 5 days)
• yorick-ynfft (- to 1.0.3-1)
  • Migration status for yorick-ynfft (- to 1.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): yorick-ynfft nfft (not considered)
    • Depends: yorick-ynfft nfft (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-ynfft.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 2882 days old (needed 5 days)
• libr3 (- to 1.3.4-1)
  • Migration status for libr3 (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libr3 would introduce bugs in testing: #1000058
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libr3.html
    • autopkgtest for libr3/1.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2890 days old (needed 2 days)
• literki (- to 0.0.0+20100113.git1da40724-1.2)
  • Migration status for literki (- to 0.0.0+20100113.git1da40724-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating literki would introduce bugs in testing: #892344, #899846, #999283
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/literki.html
    • 2897 days old (needed 5 days)
• fsharp (- to 4.0.0.4+dfsg2-2)
  • Migration status for fsharp (- to 4.0.0.4+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fsharp/4.0.0.4+dfsg2-2: amd64: Regression or new test ♻ , arm64: Regression or new test ♻ , armel: Regression or new test ♻ , armhf: Regression or new test ♻ , i386: Regression or new test ♻ , ppc64el: Regression or new test ♻ , s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsharp.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 2949 days old (needed 5 days)
• sipgrep (- to 2.1.0-2)
  • Migration status for sipgrep (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sipgrep would introduce bugs in testing: #999961
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sipgrep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2990 days old (needed 5 days)
• curlftpfs (- to 0.9.2-9)
  • Migration status for curlftpfs (- to 0.9.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating curlftpfs would introduce bugs in testing: #965476
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curlftpfs.html
    • 3064 days old (needed 5 days)
• bwctl (- to 1.5.4+dfsg1-1)
  • Migration status for bwctl (- to 1.5.4+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bwctl would introduce bugs in testing: #997326
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bwctl.html
    • 3075 days old (needed 5 days)
• yap (- to 6.2.2-6)
  • Migration status for yap (- to 6.2.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yap/i386 has unsatisfiable dependency
    • Updating yap would introduce bugs in testing: #877034, #965915
    • autopkgtest for yap/6.2.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yap.html
    • uninstallable on arch i386, not running autopkgtest there
    • 3098 days old (needed 5 days)
• vncterm (- to 0.9.10-2)
  • Migration status for vncterm (- to 0.9.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vncterm would introduce bugs in testing: #898453
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vncterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3132 days old (needed 5 days)
• qmenu (- to 5.0.2-2)
  • Migration status for qmenu (- to 5.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qmenu would introduce bugs in testing: #997191
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qmenu.html
    • 3173 days old (needed 5 days)
• libapache2-mod-auth-pgsql (- to 2.0.3-6.1)
  • Migration status for libapache2-mod-auth-pgsql (- to 2.0.3-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-auth-pgsql would introduce bugs in testing: #947039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3276 days old (needed 5 days)
• libmonitoring-availability-perl (- to 0.46-1)
  • Migration status for libmonitoring-availability-perl (- to 0.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libmonitoring-availability-perl would introduce bugs in testing: #839432
    • Not built on buildd: arch all binaries uploaded by formorer, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmonitoring-availability-perl.html
    • Reproducible on i386 - info ♻
    • 3360 days old (needed 5 days)
• pam-pgsql (- to 0.7.3.2-1)
  • Migration status for pam-pgsql (- to 0.7.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pam-pgsql would introduce bugs in testing: #863650
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3379 days old (needed 5 days)
• tart (- to 3.10-1)
  • Migration status for tart (- to 3.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tart would introduce bugs in testing: #965837
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tart.html
    • 3407 days old (needed 5 days)
• ptex-jtex (- to 1.7+1-15)
  • Migration status for ptex-jtex (- to 1.7+1-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ptex-jtex would introduce bugs in testing: #1003654
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3509 days old (needed 5 days)
• gogglesmm (- to 0.12.7-3)
  • Migration status for gogglesmm (- to 0.12.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gogglesmm would introduce bugs in testing: #1008384
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gogglesmm.html
    • 3533 days old (needed 5 days)
• scheme2c (- to 2012.10.14-1)
  • Migration status for scheme2c (- to 2012.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scheme2c would introduce bugs in testing: #778111
    • Not built on buildd: arch amd64 binaries uploaded by bap
    • Not built on buildd: arch all binaries uploaded by bap, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scheme2c.html
    • 3539 days old (needed 5 days)
• libpthread-workqueue (- to 0.9.1-1)
  • Migration status for libpthread-workqueue (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpthread-workqueue would introduce bugs in testing: #835107
    • Not built on buildd: arch amd64 binaries uploaded by rbalint
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpthread-workqueue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3591 days old (needed 5 days)
• pdfcube (- to 0.0.5-2)
  • Migration status for pdfcube (- to 0.0.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pdfcube gtkglext (not considered)
    • Depends: pdfcube gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfcube.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3617 days old (needed 5 days)
• couriergrey (- to 0.3.2-5)
  • Migration status for couriergrey (- to 0.3.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: couriergrey courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/couriergrey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3641 days old (needed 5 days)
• reminiscence (- to 0.2.1-2)
  • Migration status for reminiscence (- to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating reminiscence would introduce bugs in testing: #985184
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3729 days old (needed 5 days)
• zeroc-ice-manual (- to 3.5.0-1)
  • Migration status for zeroc-ice-manual (- to 3.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zeroc-ice-manual would introduce bugs in testing: #864472
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3794 days old (needed 5 days)
• mutextrace (- to 0.1.4-1)
  • Migration status for mutextrace (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mutextrace would introduce bugs in testing: #743062
    • Not built on buildd: arch amd64 binaries uploaded by sjr
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mutextrace.html
    • 3897 days old (needed 5 days)
• xmms2-scrobbler (- to 0.4.0-4)
  • Migration status for xmms2-scrobbler (- to 0.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmms2-scrobbler would introduce bugs in testing: #798099, #919037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2-scrobbler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3960 days old (needed 5 days)
• msp430-libc (- to 20120224-1)
  • Migration status for msp430-libc (- to 20120224-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating msp430-libc would introduce bugs in testing: #965732, #999077
    • Build-Depends(-Arch): msp430-libc binutils-msp430
    • Build-Depends(-Arch): msp430-libc gcc-msp430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msp430-libc.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • 4249 days old (needed 5 days)
• pxe-kexec (- to 0.2.4-3)
  • Migration status for pxe-kexec (- to 0.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pxe-kexec would introduce bugs in testing: #984300
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pxe-kexec.html
    • 4252 days old (needed 5 days)
• mppenc (- to 1.16-1.1)
  • Migration status for mppenc (- to 1.16-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mppenc would introduce bugs in testing: #965730, #999076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mppenc.html
    • 4280 days old (needed 5 days)
• navi2ch (- to 2.0.0~git20120331-1)
  • Migration status for navi2ch (- to 2.0.0~git20120331-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating navi2ch would introduce bugs in testing: #780480, #952259
    • Not built on buildd: arch all binaries uploaded by knok, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/navi2ch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4281 days old (needed 5 days)
• privbind (- to 1.2-1.1)
  • Migration status for privbind (- to 1.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating privbind would introduce bugs in testing: #965787, #998987
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/privbind.html
    • 4288 days old (needed 5 days)
• nttcp (- to 1.47-13)
  • Migration status for nttcp (- to 1.47-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nttcp would introduce bugs in testing: #1002847
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4298 days old (needed 5 days)
• mixer.app (- to 1.8.0-5)
  • Migration status for mixer.app (- to 1.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mixer.app would introduce bugs in testing: #896580
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixer.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4318 days old (needed 5 days)
• pstack (- to 1.3.1-1)
  • Migration status for pstack (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pstack would introduce bugs in testing: #950168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pstack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 4475 days old (needed 5 days)
• gems (- to 1.1.1-2)
  • Migration status for gems (- to 1.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gems would introduce bugs in testing: #965548
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gems.html
    • 4480 days old (needed 5 days)
• libinnodb (- to 1.0.6.6750-1)
  • Migration status for libinnodb (- to 1.0.6.6750-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libinnodb would introduce bugs in testing: #952290, #999029
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libinnodb.html
    • 5039 days old (needed 5 days)