Generated: 2022.06.10 20:10:55 +0000

• -crystal (1.2.2+dfsg-1 to -)
  • Migration status for -crystal (1.2.2+dfsg-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by elbrus
    • Package is broken, will try to remove
• -llvm-toolchain-12 (1:12.0.1-20 to -)
  • Migration status for -llvm-toolchain-12 (1:12.0.1-20 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by elbrus
    • Package is broken, will try to remove
• ace/amd64 (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/amd64 (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/amd64 openssl
• ace/arm64 (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/arm64 (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/arm64 openssl
• ace/armel (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/armel (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/armel openssl
• ace/armhf (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/armhf (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/armhf openssl
• ace/i386 (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/i386 (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/i386 openssl
• ace/mips64el (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/mips64el (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/mips64el openssl
• ace/mipsel (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/mipsel (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/mipsel openssl
• ace/ppc64el (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/ppc64el (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/ppc64el openssl
• ace/s390x (7.0.6+dfsg-2 to 7.0.6+dfsg-2)
  • Migration status for ace/s390x (7.0.6+dfsg-2 to 7.0.6+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: ace/s390x openssl
• actor-framework/amd64 (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/amd64 (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/amd64 openssl
• actor-framework/arm64 (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/arm64 (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/arm64 openssl
• actor-framework/armel (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/armel (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/armel openssl
• actor-framework/armhf (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/armhf (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/armhf openssl
• actor-framework/i386 (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/i386 (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/i386 openssl
• actor-framework/mips64el (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/mips64el (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/mips64el openssl
• actor-framework/mipsel (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/mipsel (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/mipsel openssl
• actor-framework/ppc64el (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/ppc64el (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/ppc64el openssl
• actor-framework/s390x (0.17.6-2.1 to 0.17.6-2.1)
  • Migration status for actor-framework/s390x (0.17.6-2.1 to 0.17.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: actor-framework/s390x openssl
• afflib/amd64 (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/amd64 (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/amd64 openssl
• afflib/arm64 (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/arm64 (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/arm64 openssl
• afflib/armel (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/armel (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/armel openssl
• afflib/armhf (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/armhf (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/armhf openssl
• afflib/i386 (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/i386 (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/i386 openssl
• afflib/mips64el (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/mips64el (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/mips64el openssl
• afflib/mipsel (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/mipsel (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/mipsel openssl
• afflib/ppc64el (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/ppc64el (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/ppc64el openssl
• afflib/s390x (3.7.19-2 to 3.7.19-2)
  • Migration status for afflib/s390x (3.7.19-2 to 3.7.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: afflib/s390x openssl
• apr-util/amd64 (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/amd64 (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/amd64 openssl
• apr-util/arm64 (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/arm64 (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/arm64 openssl
• apr-util/armel (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/armel (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/armel openssl
• apr-util/armhf (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/armhf (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/armhf openssl
• apr-util/i386 (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/i386 (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/i386 openssl
• apr-util/mips64el (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/mips64el (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/mips64el openssl
• apr-util/mipsel (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/mipsel (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/mipsel openssl
• apr-util/ppc64el (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/ppc64el (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/ppc64el openssl
• apr-util/s390x (1.6.1-5 to 1.6.1-5)
  • Migration status for apr-util/s390x (1.6.1-5 to 1.6.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: apr-util/s390x openssl
• apt-cacher-ng/amd64 (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/amd64 (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/amd64 openssl
• apt-cacher-ng/arm64 (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/arm64 (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/arm64 openssl
• apt-cacher-ng/armel (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/armel (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/armel openssl
• apt-cacher-ng/armhf (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/armhf (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/armhf openssl
• apt-cacher-ng/i386 (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/i386 (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/i386 openssl
• apt-cacher-ng/mips64el (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/mips64el (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/mips64el openssl
• apt-cacher-ng/mipsel (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/mipsel (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/mipsel openssl
• apt-cacher-ng/ppc64el (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/ppc64el (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/ppc64el openssl
• apt-cacher-ng/s390x (3.7.4-1 to 3.7.4-1)
  • Migration status for apt-cacher-ng/s390x (3.7.4-1 to 3.7.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: apt-cacher-ng/s390x openssl
• arc-gui-clients/amd64 (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/amd64 (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/amd64 openssl
• arc-gui-clients/arm64 (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/arm64 (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/arm64 openssl
• arc-gui-clients/armel (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/armel (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/armel openssl
• arc-gui-clients/armhf (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/armhf (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/armhf openssl
• arc-gui-clients/i386 (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/i386 (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/i386 openssl
• arc-gui-clients/mips64el (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/mips64el (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/mips64el openssl
• arc-gui-clients/mipsel (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/mipsel (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/mipsel openssl
• arc-gui-clients/ppc64el (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/ppc64el (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/ppc64el openssl
• arc-gui-clients/s390x (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/s390x (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
    • Depends: arc-gui-clients/s390x openssl
• argyll/amd64 (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/amd64 (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/amd64 openssl
• argyll/arm64 (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/arm64 (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/arm64 openssl
• argyll/armel (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/armel (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/armel openssl
• argyll/armhf (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/armhf (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/armhf openssl
• argyll/i386 (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/i386 (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/i386 openssl
• argyll/mips64el (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/mips64el (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/mips64el openssl
• argyll/mipsel (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/mipsel (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/mipsel openssl
• argyll/ppc64el (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/ppc64el (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/ppc64el openssl
• argyll/s390x (2.3.0+repack-1 to 2.3.0+repack-1)
  • Migration status for argyll/s390x (2.3.0+repack-1 to 2.3.0+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: argyll/s390x openssl
• arm-trusted-firmware/amd64 (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/amd64 (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/amd64 openssl
• arm-trusted-firmware/arm64 (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/arm64 (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/arm64 openssl
• arm-trusted-firmware/armel (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/armel (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/armel openssl
• arm-trusted-firmware/armhf (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/armhf (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/armhf openssl
• arm-trusted-firmware/i386 (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/i386 (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/i386 openssl
• arm-trusted-firmware/mips64el (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/mips64el (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/mips64el openssl
• arm-trusted-firmware/mipsel (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/mipsel (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/mipsel openssl
• arm-trusted-firmware/ppc64el (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/ppc64el (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/ppc64el openssl
• arm-trusted-firmware/s390x (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for arm-trusted-firmware/s390x (2.6+dfsg-1 to 2.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: arm-trusted-firmware/s390x openssl
• asterisk/amd64 (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/amd64 (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/amd64 openssl
• asterisk/arm64 (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/arm64 (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/arm64 openssl
• asterisk/armel (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/armel (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/armel openssl
• asterisk/armhf (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/armhf (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/armhf openssl
• asterisk/i386 (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/i386 (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/i386 openssl
• asterisk/mips64el (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/mips64el (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/mips64el openssl
• asterisk/mipsel (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/mipsel (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/mipsel openssl
• asterisk/ppc64el (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/ppc64el (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/ppc64el openssl
• asterisk/s390x (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1)
  • Migration status for asterisk/s390x (1:18.12.0~dfsg+~cs6.12.40431413-1 to 1:18.12.0~dfsg+~cs6.12.40431413-1): Will attempt migration (Any information below is purely informational)
    • Depends: asterisk/s390x openssl
• atheme-services/amd64 (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/amd64 (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/amd64 openssl
• atheme-services/arm64 (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/arm64 (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/arm64 openssl
• atheme-services/armel (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/armel (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/armel openssl
• atheme-services/armhf (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/armhf (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/armhf openssl
• atheme-services/i386 (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/i386 (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/i386 openssl
• atheme-services/mips64el (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/mips64el (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/mips64el openssl
• atheme-services/mipsel (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/mipsel (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/mipsel openssl
• atheme-services/ppc64el (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/ppc64el (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/ppc64el openssl
• atheme-services/s390x (7.2.12-1 to 7.2.12-1)
  • Migration status for atheme-services/s390x (7.2.12-1 to 7.2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: atheme-services/s390x openssl
• autofdo/amd64 (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/amd64 (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/amd64 openssl
• autofdo/arm64 (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/arm64 (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/arm64 openssl
• autofdo/armel (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/armel (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/armel openssl
• autofdo/armhf (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/armhf (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/armhf openssl
• autofdo/i386 (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/i386 (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/i386 openssl
• autofdo/mips64el (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/mips64el (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/mips64el openssl
• autofdo/mipsel (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/mipsel (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/mipsel openssl
• autofdo/ppc64el (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/ppc64el (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/ppc64el openssl
• autofdo/s390x (0.19-2.1 to 0.19-2.1)
  • Migration status for autofdo/s390x (0.19-2.1 to 0.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: autofdo/s390x openssl
• axel/amd64 (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/amd64 (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/amd64 openssl
• axel/arm64 (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/arm64 (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/arm64 openssl
• axel/armel (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/armel (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/armel openssl
• axel/armhf (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/armhf (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/armhf openssl
• axel/i386 (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/i386 (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/i386 openssl
• axel/mips64el (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/mips64el (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/mips64el openssl
• axel/mipsel (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/mipsel (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/mipsel openssl
• axel/ppc64el (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/ppc64el (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/ppc64el openssl
• axel/s390x (2.17.11-1 to 2.17.11-1)
  • Migration status for axel/s390x (2.17.11-1 to 2.17.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: axel/s390x openssl
• azure-uamqp-python/amd64 (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/amd64 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/amd64 openssl
• azure-uamqp-python/arm64 (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/arm64 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/arm64 openssl
• azure-uamqp-python/armel (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/armel (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/armel openssl
• azure-uamqp-python/armhf (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/armhf (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/armhf openssl
• azure-uamqp-python/i386 (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/i386 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/i386 openssl
• azure-uamqp-python/mips64el (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/mips64el (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/mips64el openssl
• azure-uamqp-python/mipsel (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/mipsel (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/mipsel openssl
• azure-uamqp-python/ppc64el (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/ppc64el (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/ppc64el openssl
• azure-uamqp-python/s390x (1.5.3-1 to 1.5.3-1)
  • Migration status for azure-uamqp-python/s390x (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: azure-uamqp-python/s390x openssl
• balboa/amd64 (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/amd64 (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/amd64 rocksdb (not considered)
    • Invalidated by dependency
• balboa/arm64 (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/arm64 (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/arm64 rocksdb (not considered)
    • Invalidated by dependency
• balboa/armel (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/armel (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/armel rocksdb (not considered)
    • Invalidated by dependency
• balboa/armhf (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/armhf (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/armhf rocksdb (not considered)
    • Invalidated by dependency
• balboa/i386 (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/i386 (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/i386 rocksdb (not considered)
    • Invalidated by dependency
• balboa/mips64el (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/mips64el (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/mips64el rocksdb (not considered)
    • Invalidated by dependency
• balboa/mipsel (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/mipsel (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/mipsel rocksdb (not considered)
    • Invalidated by dependency
• balboa/s390x (2.0.0+ds-4 to 2.0.0+ds-4)
  • Migration status for balboa/s390x (2.0.0+ds-4 to 2.0.0+ds-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/s390x rocksdb (not considered)
    • Invalidated by dependency
• barada-pam/amd64 (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/amd64 (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/amd64 openssl
• barada-pam/arm64 (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/arm64 (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/arm64 openssl
• barada-pam/armel (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/armel (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/armel openssl
• barada-pam/armhf (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/armhf (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/armhf openssl
• barada-pam/i386 (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/i386 (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/i386 openssl
• barada-pam/mips64el (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/mips64el (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/mips64el openssl
• barada-pam/mipsel (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/mipsel (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/mipsel openssl
• barada-pam/ppc64el (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/ppc64el (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/ppc64el openssl
• barada-pam/s390x (0.5-3.2 to 0.5-3.2)
  • Migration status for barada-pam/s390x (0.5-3.2 to 0.5-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: barada-pam/s390x openssl
• barnowl/amd64 (1.10-2 to 1.10-2)
  • Migration status for barnowl/amd64 (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/amd64 openssl
• barnowl/arm64 (1.10-2 to 1.10-2)
  • Migration status for barnowl/arm64 (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/arm64 openssl
• barnowl/armel (1.10-2 to 1.10-2)
  • Migration status for barnowl/armel (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/armel openssl
• barnowl/armhf (1.10-2 to 1.10-2)
  • Migration status for barnowl/armhf (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/armhf openssl
• barnowl/i386 (1.10-2 to 1.10-2)
  • Migration status for barnowl/i386 (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/i386 openssl
• barnowl/mips64el (1.10-2 to 1.10-2)
  • Migration status for barnowl/mips64el (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/mips64el openssl
• barnowl/mipsel (1.10-2 to 1.10-2)
  • Migration status for barnowl/mipsel (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/mipsel openssl
• barnowl/ppc64el (1.10-2 to 1.10-2)
  • Migration status for barnowl/ppc64el (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/ppc64el openssl
• barnowl/s390x (1.10-2 to 1.10-2)
  • Migration status for barnowl/s390x (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: barnowl/s390x openssl
• barrier/amd64 (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/amd64 (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/amd64 openssl
• barrier/arm64 (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/arm64 (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/arm64 openssl
• barrier/armel (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/armel (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/armel openssl
• barrier/armhf (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/armhf (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/armhf openssl
• barrier/i386 (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/i386 (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/i386 openssl
• barrier/mips64el (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/mips64el (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/mips64el openssl
• barrier/mipsel (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/mipsel (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/mipsel openssl
• barrier/ppc64el (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/ppc64el (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/ppc64el openssl
• barrier/s390x (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for barrier/s390x (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: barrier/s390x openssl
• bash_pu (5.1-6.1 to 5.1-2+deb11u1)
  • Migration status for bash_pu (5.1-6.1 to 5.1-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: bash is newer in the target suite (5.1-6.1 5.1-2+deb11u1)
• bibtexconv/amd64 (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/amd64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/amd64 openssl
• bibtexconv/arm64 (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/arm64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/arm64 openssl
• bibtexconv/armel (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/armel (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/armel openssl
• bibtexconv/armhf (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/armhf (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/armhf openssl
• bibtexconv/i386 (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/i386 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/i386 openssl
• bibtexconv/mips64el (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/mips64el (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/mips64el openssl
• bibtexconv/mipsel (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/mipsel (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/mipsel openssl
• bibtexconv/ppc64el (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/ppc64el (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/ppc64el openssl
• bibtexconv/s390x (1.3.2-1 to 1.3.2-1)
  • Migration status for bibtexconv/s390x (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: bibtexconv/s390x openssl
• bind-dyndb-ldap/amd64 (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/amd64 (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/amd64 bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/arm64 (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/arm64 (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/arm64 bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/armel (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/armel (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/armel bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/armhf (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/armhf (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/armhf bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/i386 (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/i386 (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/i386 bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/mips64el (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/mips64el (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/mips64el bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/mipsel (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/mipsel (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/mipsel bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/ppc64el (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/ppc64el (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/ppc64el bind9 (not considered)
    • Invalidated by dependency
• bind-dyndb-ldap/s390x (11.9-5 to 11.9-5)
  • Migration status for bind-dyndb-ldap/s390x (11.9-5 to 11.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bind-dyndb-ldap/s390x bind9 (not considered)
    • Invalidated by dependency
• bind9-libs/amd64 (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/amd64 (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/amd64 openssl
• bind9-libs/arm64 (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/arm64 (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/arm64 openssl
• bind9-libs/armel (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/armel (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/armel openssl
• bind9-libs/armhf (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/armhf (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/armhf openssl
• bind9-libs/i386 (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/i386 (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/i386 openssl
• bind9-libs/mips64el (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/mips64el (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/mips64el openssl
• bind9-libs/mipsel (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/mipsel (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/mipsel openssl
• bind9-libs/ppc64el (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/ppc64el (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/ppc64el openssl
• bind9-libs/s390x (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1)
  • Migration status for bind9-libs/s390x (1:9.11.19+dfsg-2.1 to 1:9.11.19+dfsg-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: bind9-libs/s390x openssl
• bip/amd64 (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/amd64 (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/amd64 openssl
• bip/arm64 (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/arm64 (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/arm64 openssl
• bip/armel (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/armel (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/armel openssl
• bip/armhf (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/armhf (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/armhf openssl
• bip/i386 (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/i386 (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/i386 openssl
• bip/mips64el (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/mips64el (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/mips64el openssl
• bip/mipsel (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/mipsel (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/mipsel openssl
• bip/ppc64el (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/ppc64el (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/ppc64el openssl
• bip/s390x (0.9.3-1 to 0.9.3-1)
  • Migration status for bip/s390x (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: bip/s390x openssl
• boinc/amd64 (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/amd64 (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Depends: boinc/amd64 openssl
• boinc/arm64 (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/arm64 (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Depends: boinc/arm64 openssl
• boinc/armel (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/armel (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch armel binaries not found
    • Depends: boinc/armel openssl
• boinc/armhf (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/armhf (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch armhf binaries not found
    • Depends: boinc/armhf openssl
• boinc/i386 (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/i386 (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch i386 binaries not found
    • Depends: boinc/i386 openssl
• boinc/mips64el (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/mips64el (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Depends: boinc/mips64el openssl
• boinc/mipsel (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/mipsel (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch mipsel binaries not found
    • Depends: boinc/mipsel openssl
• boinc/ppc64el (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/ppc64el (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Depends: boinc/ppc64el openssl
• boinc/s390x (7.18.1+dfsg-4 to 7.18.1+dfsg-4)
  • Migration status for boinc/s390x (7.18.1+dfsg-4 to 7.18.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch s390x binaries not found
    • Depends: boinc/s390x openssl
• bruteforce-salted-openssl/amd64 (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/amd64 (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/amd64 openssl
• bruteforce-salted-openssl/arm64 (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/arm64 (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/arm64 openssl
• bruteforce-salted-openssl/armel (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/armel (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/armel openssl
• bruteforce-salted-openssl/armhf (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/armhf (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/armhf openssl
• bruteforce-salted-openssl/i386 (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/i386 (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/i386 openssl
• bruteforce-salted-openssl/mips64el (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/mips64el (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/mips64el openssl
• bruteforce-salted-openssl/mipsel (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/mipsel (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/mipsel openssl
• bruteforce-salted-openssl/ppc64el (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/ppc64el (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/ppc64el openssl
• bruteforce-salted-openssl/s390x (1.4.2-3 to 1.4.2-3)
  • Migration status for bruteforce-salted-openssl/s390x (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-salted-openssl/s390x openssl
• bruteforce-wallet/amd64 (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/amd64 (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/amd64 openssl
• bruteforce-wallet/arm64 (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/arm64 (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/arm64 openssl
• bruteforce-wallet/armel (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/armel (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/armel openssl
• bruteforce-wallet/armhf (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/armhf (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/armhf openssl
• bruteforce-wallet/i386 (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/i386 (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/i386 openssl
• bruteforce-wallet/mips64el (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/mips64el (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/mips64el openssl
• bruteforce-wallet/mipsel (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/mipsel (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/mipsel openssl
• bruteforce-wallet/ppc64el (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/ppc64el (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/ppc64el openssl
• bruteforce-wallet/s390x (1.5.3-5 to 1.5.3-5)
  • Migration status for bruteforce-wallet/s390x (1.5.3-5 to 1.5.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: bruteforce-wallet/s390x openssl
• btfs/amd64 (2.24-1 to 2.24-1)
  • Migration status for btfs/amd64 (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/amd64 openssl
• btfs/arm64 (2.24-1 to 2.24-1)
  • Migration status for btfs/arm64 (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/arm64 openssl
• btfs/armel (2.24-1 to 2.24-1)
  • Migration status for btfs/armel (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/armel openssl
• btfs/armhf (2.24-1 to 2.24-1)
  • Migration status for btfs/armhf (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/armhf openssl
• btfs/i386 (2.24-1 to 2.24-1)
  • Migration status for btfs/i386 (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/i386 openssl
• btfs/mips64el (2.24-1 to 2.24-1)
  • Migration status for btfs/mips64el (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/mips64el openssl
• btfs/mipsel (2.24-1 to 2.24-1)
  • Migration status for btfs/mipsel (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/mipsel openssl
• btfs/ppc64el (2.24-1 to 2.24-1)
  • Migration status for btfs/ppc64el (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/ppc64el openssl
• btfs/s390x (2.24-1 to 2.24-1)
  • Migration status for btfs/s390x (2.24-1 to 2.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: btfs/s390x openssl
• burp/amd64 (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/amd64 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/amd64 openssl
• burp/arm64 (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/arm64 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/arm64 openssl
• burp/armel (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/armel (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/armel openssl
• burp/armhf (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/armhf (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/armhf openssl
• burp/i386 (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/i386 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/i386 openssl
• burp/mips64el (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/mips64el (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/mips64el openssl
• burp/mipsel (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/mipsel (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/mipsel openssl
• burp/ppc64el (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/ppc64el (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/ppc64el openssl
• burp/s390x (2.4.0-3 to 2.4.0-3)
  • Migration status for burp/s390x (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: burp/s390x openssl
• butt/amd64 (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/amd64 (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/amd64 openssl
• butt/arm64 (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/arm64 (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/arm64 openssl
• butt/armel (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/armel (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/armel openssl
• butt/armhf (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/armhf (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/armhf openssl
• butt/i386 (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/i386 (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/i386 openssl
• butt/mips64el (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/mips64el (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/mips64el openssl
• butt/mipsel (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/mipsel (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/mipsel openssl
• butt/ppc64el (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/ppc64el (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/ppc64el openssl
• butt/s390x (0.1.26-1 to 0.1.26-1)
  • Migration status for butt/s390x (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: butt/s390x openssl
• c-icap/amd64 (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/amd64 (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/amd64 openssl
• c-icap/arm64 (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/arm64 (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/arm64 openssl
• c-icap/armel (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/armel (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/armel openssl
• c-icap/armhf (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/armhf (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/armhf openssl
• c-icap/i386 (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/i386 (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/i386 openssl
• c-icap/mips64el (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/mips64el (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/mips64el openssl
• c-icap/mipsel (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/mipsel (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/mipsel openssl
• c-icap/ppc64el (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/ppc64el (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/ppc64el openssl
• c-icap/s390x (1:0.5.10-1 to 1:0.5.10-1)
  • Migration status for c-icap/s390x (1:0.5.10-1 to 1:0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: c-icap/s390x openssl
• cairo-dock-plug-ins/amd64 (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/amd64 (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/amd64 openssl
• cairo-dock-plug-ins/arm64 (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/arm64 (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/arm64 openssl
• cairo-dock-plug-ins/armel (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/armel (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/armel openssl
• cairo-dock-plug-ins/armhf (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/armhf (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/armhf openssl
• cairo-dock-plug-ins/i386 (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/i386 (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/i386 openssl
• cairo-dock-plug-ins/mips64el (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/mips64el (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/mips64el openssl
• cairo-dock-plug-ins/mipsel (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/mipsel (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/mipsel openssl
• cairo-dock-plug-ins/ppc64el (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/ppc64el (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/ppc64el openssl
• cairo-dock-plug-ins/s390x (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1)
  • Migration status for cairo-dock-plug-ins/s390x (3.4.1+git20201022.a0d3415c-1 to 3.4.1+git20201022.a0d3415c-1): Will attempt migration (Any information below is purely informational)
    • Depends: cairo-dock-plug-ins/s390x openssl
• canl-c/amd64 (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/amd64 (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/amd64 openssl
• canl-c/arm64 (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/arm64 (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/arm64 openssl
• canl-c/armel (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/armel (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/armel openssl
• canl-c/armhf (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/armhf (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/armhf openssl
• canl-c/i386 (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/i386 (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/i386 openssl
• canl-c/mips64el (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/mips64el (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/mips64el openssl
• canl-c/mipsel (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/mipsel (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/mipsel openssl
• canl-c/ppc64el (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/ppc64el (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/ppc64el openssl
• canl-c/s390x (3.0.0-3.1 to 3.0.0-3.1)
  • Migration status for canl-c/s390x (3.0.0-3.1 to 3.0.0-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: canl-c/s390x openssl
• capnproto/amd64 (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/amd64 (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/amd64 openssl
• capnproto/arm64 (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/arm64 (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/arm64 openssl
• capnproto/armel (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/armel (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/armel openssl
• capnproto/armhf (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/armhf (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/armhf openssl
• capnproto/i386 (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/i386 (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/i386 openssl
• capnproto/mips64el (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/mips64el (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/mips64el openssl
• capnproto/mipsel (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/mipsel (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/mipsel openssl
• capnproto/ppc64el (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/ppc64el (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/ppc64el openssl
• capnproto/s390x (0.9.1-4 to 0.9.1-4)
  • Migration status for capnproto/s390x (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: capnproto/s390x openssl
• carbon-c-relay/amd64 (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/amd64 (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/amd64 openssl
• carbon-c-relay/arm64 (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/arm64 (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/arm64 openssl
• carbon-c-relay/armel (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/armel (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/armel openssl
• carbon-c-relay/armhf (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/armhf (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/armhf openssl
• carbon-c-relay/i386 (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/i386 (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/i386 openssl
• carbon-c-relay/mips64el (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/mips64el (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/mips64el openssl
• carbon-c-relay/mipsel (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/mipsel (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/mipsel openssl
• carbon-c-relay/ppc64el (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/ppc64el (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/ppc64el openssl
• carbon-c-relay/s390x (3.7.3-2 to 3.7.3-2)
  • Migration status for carbon-c-relay/s390x (3.7.3-2 to 3.7.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: carbon-c-relay/s390x openssl
• cardpeek/amd64 (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/amd64 (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/amd64 openssl
• cardpeek/arm64 (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/arm64 (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/arm64 openssl
• cardpeek/armel (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/armel (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/armel openssl
• cardpeek/armhf (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/armhf (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/armhf openssl
• cardpeek/i386 (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/i386 (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/i386 openssl
• cardpeek/mips64el (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/mips64el (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/mips64el openssl
• cardpeek/mipsel (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/mipsel (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/mipsel openssl
• cardpeek/ppc64el (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/ppc64el (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/ppc64el openssl
• cardpeek/s390x (0.8.4-1.1 to 0.8.4-1.1)
  • Migration status for cardpeek/s390x (0.8.4-1.1 to 0.8.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: cardpeek/s390x openssl
• cargo/amd64 (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/amd64 (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/amd64 openssl
• cargo/arm64 (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/arm64 (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/arm64 openssl
• cargo/armhf (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/armhf (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/armhf openssl
• cargo/i386 (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/i386 (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/i386 openssl
• cargo/mipsel (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/mipsel (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/mipsel openssl
• cargo/ppc64el (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/ppc64el (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/ppc64el openssl
• cargo/s390x (0.57.0-7 to 0.57.0-7)
  • Migration status for cargo/s390x (0.57.0-7 to 0.57.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: cargo/s390x openssl
• casync/amd64 (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/amd64 (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/amd64 openssl
• casync/arm64 (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/arm64 (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/arm64 openssl
• casync/armel (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/armel (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/armel openssl
• casync/armhf (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/armhf (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/armhf openssl
• casync/i386 (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/i386 (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/i386 openssl
• casync/mips64el (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/mips64el (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/mips64el openssl
• casync/mipsel (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/mipsel (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/mipsel openssl
• casync/ppc64el (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/ppc64el (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/ppc64el openssl
• casync/s390x (2+20201210-1 to 2+20201210-1)
  • Migration status for casync/s390x (2+20201210-1 to 2+20201210-1): Will attempt migration (Any information below is purely informational)
    • Depends: casync/s390x openssl
• catgirl/amd64 (2.1-1 to 2.1-1)
  • Migration status for catgirl/amd64 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/amd64 libretls
• catgirl/arm64 (2.1-1 to 2.1-1)
  • Migration status for catgirl/arm64 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/arm64 libretls
• catgirl/armel (2.1-1 to 2.1-1)
  • Migration status for catgirl/armel (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/armel libretls
• catgirl/armhf (2.1-1 to 2.1-1)
  • Migration status for catgirl/armhf (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/armhf libretls
• catgirl/i386 (2.1-1 to 2.1-1)
  • Migration status for catgirl/i386 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/i386 libretls
• catgirl/mips64el (2.1-1 to 2.1-1)
  • Migration status for catgirl/mips64el (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/mips64el libretls
• catgirl/mipsel (2.1-1 to 2.1-1)
  • Migration status for catgirl/mipsel (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/mipsel libretls
• catgirl/ppc64el (2.1-1 to 2.1-1)
  • Migration status for catgirl/ppc64el (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/ppc64el libretls
• catgirl/s390x (2.1-1 to 2.1-1)
  • Migration status for catgirl/s390x (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: catgirl/s390x libretls
• ceph/amd64 (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/amd64 (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/amd64 openssl
• ceph/arm64 (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/arm64 (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/arm64 openssl
• ceph/armel (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/armel (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/armel openssl
• ceph/armhf (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/armhf (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/armhf openssl
• ceph/i386 (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/i386 (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/i386 openssl
• ceph/mips64el (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/mips64el (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/mips64el openssl
• ceph/mipsel (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/mipsel (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/mipsel openssl
• ceph/ppc64el (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/ppc64el (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/ppc64el openssl
• ceph/s390x (16.2.7+ds-4 to 16.2.7+ds-4)
  • Migration status for ceph/s390x (16.2.7+ds-4 to 16.2.7+ds-4): Will attempt migration (Any information below is purely informational)
    • Depends: ceph/s390x openssl
• certmonger/amd64 (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/amd64 (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/amd64 openssl
• certmonger/arm64 (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/arm64 (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/arm64 openssl
• certmonger/armel (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/armel (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/armel openssl
• certmonger/armhf (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/armhf (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/armhf openssl
• certmonger/i386 (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/i386 (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/i386 openssl
• certmonger/mips64el (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/mips64el (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/mips64el openssl
• certmonger/mipsel (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/mipsel (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/mipsel openssl
• certmonger/ppc64el (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/ppc64el (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/ppc64el openssl
• certmonger/s390x (0.79.15-1 to 0.79.15-1)
  • Migration status for certmonger/s390x (0.79.15-1 to 0.79.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: certmonger/s390x openssl
• cgsi-gsoap/amd64 (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/amd64 (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
    • Depends: cgsi-gsoap/amd64 openssl
• cgsi-gsoap/arm64 (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/arm64 (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
    • Depends: cgsi-gsoap/arm64 openssl
• 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)
    • Depends: cgsi-gsoap/armel openssl
• 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)
    • Depends: cgsi-gsoap/armhf openssl
• 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)
    • Depends: cgsi-gsoap/i386 openssl
• 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)
    • Depends: cgsi-gsoap/mips64el openssl
• cgsi-gsoap/mipsel (1.3.11-2 to 1.3.11-2)
  • Migration status for cgsi-gsoap/mipsel (1.3.11-2 to 1.3.11-2): Will attempt migration (Any information below is purely informational)
    • Depends: cgsi-gsoap/mipsel openssl
• 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)
    • Depends: cgsi-gsoap/ppc64el openssl
• 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)
    • Depends: cgsi-gsoap/s390x openssl
• chiaki/amd64 (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/amd64 (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/amd64 openssl
• chiaki/arm64 (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/arm64 (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/arm64 openssl
• chiaki/armel (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/armel (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/armel openssl
• chiaki/armhf (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/armhf (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/armhf openssl
• chiaki/i386 (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/i386 (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/i386 openssl
• chiaki/mips64el (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/mips64el (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/mips64el openssl
• chiaki/mipsel (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/mipsel (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/mipsel openssl
• chiaki/ppc64el (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/ppc64el (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/ppc64el openssl
• chiaki/s390x (2.1.0-1.1 to 2.1.0-1.1)
  • Migration status for chiaki/s390x (2.1.0-1.1 to 2.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: chiaki/s390x openssl
• cjose/amd64 (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/amd64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/amd64 openssl
• cjose/arm64 (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/arm64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/arm64 openssl
• cjose/armel (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/armel (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/armel openssl
• cjose/armhf (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/armhf (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/armhf openssl
• cjose/i386 (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/i386 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/i386 openssl
• cjose/mips64el (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/mips64el (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/mips64el openssl
• cjose/mipsel (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/mipsel (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/mipsel openssl
• cjose/ppc64el (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/ppc64el (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/ppc64el openssl
• cjose/s390x (0.6.2-1 to 0.6.2-1)
  • Migration status for cjose/s390x (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: cjose/s390x openssl
• ckermit/amd64 (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/amd64 (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/amd64 openssl
• ckermit/arm64 (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/arm64 (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/arm64 openssl
• ckermit/armel (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/armel (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/armel openssl
• ckermit/armhf (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/armhf (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/armhf openssl
• ckermit/i386 (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/i386 (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/i386 openssl
• ckermit/mips64el (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/mips64el (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/mips64el openssl
• ckermit/mipsel (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/mipsel (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/mipsel openssl
• ckermit/ppc64el (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/ppc64el (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/ppc64el openssl
• ckermit/s390x (305~alpha07-1 to 305~alpha07-1)
  • Migration status for ckermit/s390x (305~alpha07-1 to 305~alpha07-1): Will attempt migration (Any information below is purely informational)
    • Depends: ckermit/s390x openssl
• clamav/amd64 (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/amd64 (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/amd64 openssl
• clamav/arm64 (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/arm64 (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/arm64 openssl
• clamav/armel (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/armel (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/armel openssl
• clamav/armhf (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/armhf (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/armhf openssl
• clamav/i386 (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/i386 (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/i386 openssl
• clamav/mips64el (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/mips64el (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/mips64el openssl
• clamav/mipsel (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/mipsel (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/mipsel openssl
• clamav/ppc64el (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/ppc64el (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/ppc64el openssl
• clamav/s390x (0.103.6+dfsg-1 to 0.103.6+dfsg-1)
  • Migration status for clamav/s390x (0.103.6+dfsg-1 to 0.103.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: clamav/s390x openssl
• clamav_pu (0.103.6+dfsg-1 to 0.103.6+dfsg-0+deb11u1)
  • Migration status for clamav_pu (0.103.6+dfsg-1 to 0.103.6+dfsg-0+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: clamav is newer in the target suite (0.103.6+dfsg-1 0.103.6+dfsg-0+deb11u1)
• classified-ads/amd64 (0.14-1 to 0.14-1)
  • Migration status for classified-ads/amd64 (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/amd64 openssl
• classified-ads/arm64 (0.14-1 to 0.14-1)
  • Migration status for classified-ads/arm64 (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/arm64 openssl
• classified-ads/armel (0.14-1 to 0.14-1)
  • Migration status for classified-ads/armel (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/armel openssl
• classified-ads/armhf (0.14-1 to 0.14-1)
  • Migration status for classified-ads/armhf (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/armhf openssl
• classified-ads/i386 (0.14-1 to 0.14-1)
  • Migration status for classified-ads/i386 (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/i386 openssl
• classified-ads/mips64el (0.14-1 to 0.14-1)
  • Migration status for classified-ads/mips64el (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/mips64el openssl
• classified-ads/mipsel (0.14-1 to 0.14-1)
  • Migration status for classified-ads/mipsel (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/mipsel openssl
• classified-ads/ppc64el (0.14-1 to 0.14-1)
  • Migration status for classified-ads/ppc64el (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/ppc64el openssl
• classified-ads/s390x (0.14-1 to 0.14-1)
  • Migration status for classified-ads/s390x (0.14-1 to 0.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: classified-ads/s390x openssl
• clevis/amd64 (18-2 to 18-2)
  • Migration status for clevis/amd64 (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/amd64 openssl
• clevis/arm64 (18-2 to 18-2)
  • Migration status for clevis/arm64 (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/arm64 openssl
• clevis/armel (18-2 to 18-2)
  • Migration status for clevis/armel (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/armel openssl
• clevis/armhf (18-2 to 18-2)
  • Migration status for clevis/armhf (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/armhf openssl
• clevis/i386 (18-2 to 18-2)
  • Migration status for clevis/i386 (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/i386 openssl
• clevis/mips64el (18-2 to 18-2)
  • Migration status for clevis/mips64el (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/mips64el openssl
• clevis/mipsel (18-2 to 18-2)
  • Migration status for clevis/mipsel (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/mipsel openssl
• clevis/ppc64el (18-2 to 18-2)
  • Migration status for clevis/ppc64el (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/ppc64el openssl
• clevis/s390x (18-2 to 18-2)
  • Migration status for clevis/s390x (18-2 to 18-2): Will attempt migration (Any information below is purely informational)
    • Depends: clevis/s390x openssl
• conserver/amd64 (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/amd64 (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/amd64 openssl
• conserver/arm64 (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/arm64 (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/arm64 openssl
• conserver/armel (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/armel (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/armel openssl
• conserver/armhf (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/armhf (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/armhf openssl
• conserver/i386 (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/i386 (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/i386 openssl
• conserver/mips64el (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/mips64el (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/mips64el openssl
• conserver/mipsel (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/mipsel (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/mipsel openssl
• conserver/ppc64el (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/ppc64el (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/ppc64el openssl
• conserver/s390x (8.2.6-3 to 8.2.6-3)
  • Migration status for conserver/s390x (8.2.6-3 to 8.2.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: conserver/s390x openssl
• cowpatty/amd64 (4.8-3 to 4.8-3)
  • Migration status for cowpatty/amd64 (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/amd64 openssl
• cowpatty/arm64 (4.8-3 to 4.8-3)
  • Migration status for cowpatty/arm64 (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/arm64 openssl
• cowpatty/armel (4.8-3 to 4.8-3)
  • Migration status for cowpatty/armel (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/armel openssl
• cowpatty/armhf (4.8-3 to 4.8-3)
  • Migration status for cowpatty/armhf (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/armhf openssl
• cowpatty/i386 (4.8-3 to 4.8-3)
  • Migration status for cowpatty/i386 (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/i386 openssl
• cowpatty/mips64el (4.8-3 to 4.8-3)
  • Migration status for cowpatty/mips64el (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/mips64el openssl
• cowpatty/mipsel (4.8-3 to 4.8-3)
  • Migration status for cowpatty/mipsel (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/mipsel openssl
• cowpatty/ppc64el (4.8-3 to 4.8-3)
  • Migration status for cowpatty/ppc64el (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/ppc64el openssl
• cowpatty/s390x (4.8-3 to 4.8-3)
  • Migration status for cowpatty/s390x (4.8-3 to 4.8-3): Will attempt migration (Any information below is purely informational)
    • Depends: cowpatty/s390x openssl
• cpprest/amd64 (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/amd64 (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/amd64 openssl
• cpprest/arm64 (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/arm64 (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/arm64 openssl
• cpprest/armel (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/armel (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/armel openssl
• cpprest/armhf (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/armhf (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/armhf openssl
• cpprest/i386 (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/i386 (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/i386 openssl
• cpprest/mips64el (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/mips64el (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/mips64el openssl
• cpprest/mipsel (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/mipsel (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/mipsel openssl
• cpprest/ppc64el (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/ppc64el (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/ppc64el openssl
• cpprest/s390x (2.10.18-1 to 2.10.18-1)
  • Migration status for cpprest/s390x (2.10.18-1 to 2.10.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpprest/s390x openssl
• createrepo-c/amd64 (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/amd64 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/amd64 openssl
• createrepo-c/arm64 (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/arm64 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/arm64 openssl
• createrepo-c/armel (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/armel (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/armel openssl
• createrepo-c/armhf (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/armhf (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/armhf openssl
• createrepo-c/i386 (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/i386 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/i386 openssl
• createrepo-c/mips64el (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/mips64el (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/mips64el openssl
• createrepo-c/mipsel (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/mipsel (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/mipsel openssl
• createrepo-c/ppc64el (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/ppc64el (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/ppc64el openssl
• createrepo-c/s390x (0.17.0-1 to 0.17.0-1)
  • Migration status for createrepo-c/s390x (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: createrepo-c/s390x openssl
• cryptsetup/amd64 (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/amd64 (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/amd64 openssl
• cryptsetup/arm64 (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/arm64 (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/arm64 openssl
• cryptsetup/armel (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/armel (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/armel openssl
• cryptsetup/armhf (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/armhf (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/armhf openssl
• cryptsetup/i386 (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/i386 (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/i386 openssl
• cryptsetup/mips64el (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/mips64el (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/mips64el openssl
• cryptsetup/mipsel (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/mipsel (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/mipsel openssl
• cryptsetup/ppc64el (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/ppc64el (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/ppc64el openssl
• cryptsetup/s390x (2:2.4.3-1 to 2:2.4.3-1)
  • Migration status for cryptsetup/s390x (2:2.4.3-1 to 2:2.4.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: cryptsetup/s390x openssl
• crystal/amd64 (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/amd64 (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/arm64 (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/arm64 (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/armel (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/armel (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/armhf (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/armhf (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/i386 (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/i386 (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/mips64el (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/mips64el (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/mipsel (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/mipsel (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/ppc64el (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/ppc64el (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• crystal/s390x (1.2.2+dfsg-1 to 1.2.2+dfsg-1)
  • Migration status for crystal/s390x (1.2.2+dfsg-1 to 1.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
• cups_pu (2.4.2-1 to 2.3.3op2-3+deb11u2)
  • Migration status for cups_pu (2.4.2-1 to 2.3.3op2-3+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: cups is newer in the target suite (2.4.2-1 2.3.3op2-3+deb11u2)
• cyrus-imapd/amd64 (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/amd64 (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/amd64 openssl
• cyrus-imapd/arm64 (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/arm64 (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/arm64 openssl
• cyrus-imapd/armel (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/armel (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/armel openssl
• cyrus-imapd/armhf (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/armhf (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/armhf openssl
• cyrus-imapd/i386 (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/i386 (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/i386 openssl
• cyrus-imapd/mips64el (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/mips64el (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/mips64el openssl
• cyrus-imapd/mipsel (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/mipsel (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/mipsel openssl
• cyrus-imapd/ppc64el (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/ppc64el (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/ppc64el openssl
• cyrus-imapd/s390x (3.6.0~beta2-3 to 3.6.0~beta2-3)
  • Migration status for cyrus-imapd/s390x (3.6.0~beta2-3 to 3.6.0~beta2-3): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-imapd/s390x openssl
• davix/amd64 (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/amd64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/amd64 openssl
• davix/arm64 (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/arm64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/arm64 openssl
• davix/armel (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/armel (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/armel openssl
• davix/armhf (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/armhf (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/armhf openssl
• davix/i386 (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/i386 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/i386 openssl
• davix/mips64el (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/mips64el (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/mips64el openssl
• davix/mipsel (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/mipsel (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/mipsel openssl
• davix/ppc64el (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/ppc64el (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/ppc64el openssl
• davix/s390x (0.8.1-1 to 0.8.1-1)
  • Migration status for davix/s390x (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: davix/s390x openssl
• dcap/amd64 (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/amd64 (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/amd64 openssl
• dcap/arm64 (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/arm64 (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/arm64 openssl
• dcap/armel (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/armel (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/armel openssl
• dcap/armhf (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/armhf (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/armhf openssl
• dcap/i386 (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/i386 (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/i386 openssl
• dcap/mips64el (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/mips64el (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/mips64el openssl
• dcap/mipsel (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/mipsel (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/mipsel openssl
• dcap/ppc64el (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/ppc64el (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/ppc64el openssl
• dcap/s390x (2.47.12-4 to 2.47.12-4)
  • Migration status for dcap/s390x (2.47.12-4 to 2.47.12-4): Will attempt migration (Any information below is purely informational)
    • Depends: dcap/s390x openssl
• ddnet/amd64 (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/amd64 (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/amd64 openssl
• ddnet/arm64 (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/arm64 (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/arm64 openssl
• ddnet/armel (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/armel (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/armel openssl
• ddnet/armhf (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/armhf (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/armhf openssl
• ddnet/i386 (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/i386 (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/i386 openssl
• ddnet/mips64el (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/mips64el (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/mips64el openssl
• ddnet/mipsel (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/mipsel (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/mipsel openssl
• ddnet/ppc64el (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/ppc64el (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/ppc64el openssl
• ddnet/s390x (16.0.2-1 to 16.0.2-1)
  • Migration status for ddnet/s390x (16.0.2-1 to 16.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: ddnet/s390x openssl
• dillo/amd64 (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/amd64 (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/amd64 openssl
• dillo/arm64 (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/arm64 (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/arm64 openssl
• dillo/armel (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/armel (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/armel openssl
• dillo/armhf (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/armhf (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/armhf openssl
• dillo/i386 (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/i386 (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/i386 openssl
• dillo/mips64el (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/mips64el (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/mips64el openssl
• dillo/mipsel (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/mipsel (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/mipsel openssl
• dillo/ppc64el (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/ppc64el (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/ppc64el openssl
• dillo/s390x (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/s390x (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
    • Depends: dillo/s390x openssl
• distro-info-data_pu (0.53 to 0.51+deb11u2)
  • Migration status for distro-info-data_pu (0.53 to 0.51+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: distro-info-data is newer in the target suite (0.53 0.51+deb11u2)
• dma/amd64 (0.13-1 to 0.13-1)
  • Migration status for dma/amd64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/amd64 openssl
• dma/arm64 (0.13-1 to 0.13-1)
  • Migration status for dma/arm64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/arm64 openssl
• dma/armel (0.13-1 to 0.13-1)
  • Migration status for dma/armel (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/armel openssl
• dma/armhf (0.13-1 to 0.13-1)
  • Migration status for dma/armhf (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/armhf openssl
• dma/i386 (0.13-1 to 0.13-1)
  • Migration status for dma/i386 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/i386 openssl
• dma/mips64el (0.13-1 to 0.13-1)
  • Migration status for dma/mips64el (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/mips64el openssl
• dma/mipsel (0.13-1 to 0.13-1)
  • Migration status for dma/mipsel (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/mipsel openssl
• dma/ppc64el (0.13-1 to 0.13-1)
  • Migration status for dma/ppc64el (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/ppc64el openssl
• dma/s390x (0.13-1 to 0.13-1)
  • Migration status for dma/s390x (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: dma/s390x openssl
• dmg2img/amd64 (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/amd64 (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/amd64 openssl
• dmg2img/arm64 (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/arm64 (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/arm64 openssl
• dmg2img/armel (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/armel (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/armel openssl
• dmg2img/armhf (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/armhf (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/armhf openssl
• dmg2img/i386 (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/i386 (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/i386 openssl
• dmg2img/mips64el (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/mips64el (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/mips64el openssl
• dmg2img/mipsel (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/mipsel (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/mipsel openssl
• dmg2img/ppc64el (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/ppc64el (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/ppc64el openssl
• dmg2img/s390x (1.6.7-1 to 1.6.7-1)
  • Migration status for dmg2img/s390x (1.6.7-1 to 1.6.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: dmg2img/s390x openssl
• dnscap/amd64 (2.0.2-1 to 2.0.2-1)
  • Migration status for dnscap/amd64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnscap/amd64 openssl
• dnscap/arm64 (2.0.2-1 to 2.0.2-1)
  • Migration status for dnscap/arm64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnscap/arm64 openssl
• dnscap/armel (2.0.2-1 to 2.0.2-1)
  • Migration status for dnscap/armel (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnscap/armel openssl
• dnscap/armhf (2.0.2-1 to 2.0.2-1)
  • Migration status for dnscap/armhf (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnscap/armhf openssl
• dnscap/i386 (2.0.2-1 to 2.0.2-1)
  • Migration status for dnscap/i386 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnscap/i386 openssl
• dnscap/ppc64el (2.0.2-1 to 2.0.2-1)
  • Migration status for dnscap/ppc64el (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnscap/ppc64el openssl
• dnsdist/amd64 (1.7.1-1 to 1.7.1-1)
  • Migration status for dnsdist/amd64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsdist/amd64 openssl
• dnsdist/arm64 (1.7.1-1 to 1.7.1-1)
  • Migration status for dnsdist/arm64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsdist/arm64 openssl
• dnsdist/mips64el (1.7.1-1 to 1.7.1-1)
  • Migration status for dnsdist/mips64el (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsdist/mips64el openssl
• dnsdist/ppc64el (1.7.1-1 to 1.7.1-1)
  • Migration status for dnsdist/ppc64el (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsdist/ppc64el openssl
• dnsdist/s390x (1.7.1-1 to 1.7.1-1)
  • Migration status for dnsdist/s390x (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsdist/s390x openssl
• dnsperf/amd64 (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/amd64 (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/amd64 openssl
• dnsperf/arm64 (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/arm64 (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/arm64 openssl
• dnsperf/armel (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/armel (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/armel openssl
• dnsperf/armhf (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/armhf (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/armhf openssl
• dnsperf/i386 (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/i386 (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/i386 openssl
• dnsperf/mips64el (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/mips64el (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/mips64el openssl
• dnsperf/mipsel (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/mipsel (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/mipsel openssl
• dnsperf/ppc64el (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/ppc64el (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/ppc64el openssl
• dnsperf/s390x (2.9.0-1 to 2.9.0-1)
  • Migration status for dnsperf/s390x (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: dnsperf/s390x openssl
• dnssec-trigger/amd64 (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/amd64 (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/amd64 openssl
• dnssec-trigger/arm64 (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/arm64 (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/arm64 openssl
• dnssec-trigger/armel (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/armel (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/armel openssl
• dnssec-trigger/armhf (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/armhf (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/armhf openssl
• dnssec-trigger/i386 (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/i386 (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/i386 openssl
• dnssec-trigger/mips64el (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/mips64el (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/mips64el openssl
• dnssec-trigger/mipsel (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/mipsel (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/mipsel openssl
• dnssec-trigger/ppc64el (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/ppc64el (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/ppc64el openssl
• dnssec-trigger/s390x (0.17+repack-5 to 0.17+repack-5)
  • Migration status for dnssec-trigger/s390x (0.17+repack-5 to 0.17+repack-5): Will attempt migration (Any information below is purely informational)
    • Depends: dnssec-trigger/s390x openssl
• dpdk/amd64 (20.11.5-1 to 20.11.5-1)
  • Migration status for dpdk/amd64 (20.11.5-1 to 20.11.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: dpdk/amd64 openssl
• dpdk/arm64 (20.11.5-1 to 20.11.5-1)
  • Migration status for dpdk/arm64 (20.11.5-1 to 20.11.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: dpdk/arm64 openssl
• dpdk/armhf (20.11.5-1 to 20.11.5-1)
  • Migration status for dpdk/armhf (20.11.5-1 to 20.11.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: dpdk/armhf openssl
• dpdk/i386 (20.11.5-1 to 20.11.5-1)
  • Migration status for dpdk/i386 (20.11.5-1 to 20.11.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: dpdk/i386 openssl
• dpdk/ppc64el (20.11.5-1 to 20.11.5-1)
  • Migration status for dpdk/ppc64el (20.11.5-1 to 20.11.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: dpdk/ppc64el openssl
• dpdk_pu (20.11.5-1 to 20.11.5-1~deb11u1)
  • Migration status for dpdk_pu (20.11.5-1 to 20.11.5-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: dpdk is newer in the target suite (20.11.5-1 20.11.5-1~deb11u1)
• dpkg_pu (1.21.8 to 1.20.10)
  • Migration status for dpkg_pu (1.21.8 to 1.20.10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: dpkg is newer in the target suite (1.21.8 1.20.10)
• dsniff/amd64 (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/amd64 (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/amd64 openssl
• dsniff/arm64 (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/arm64 (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/arm64 openssl
• dsniff/armel (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/armel (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/armel openssl
• dsniff/armhf (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/armhf (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/armhf openssl
• dsniff/i386 (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/i386 (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/i386 openssl
• dsniff/mips64el (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/mips64el (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/mips64el openssl
• dsniff/mipsel (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/mipsel (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/mipsel openssl
• dsniff/ppc64el (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/ppc64el (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/ppc64el openssl
• dsniff/s390x (2.4b1+debian-30 to 2.4b1+debian-30)
  • Migration status for dsniff/s390x (2.4b1+debian-30 to 2.4b1+debian-30): Will attempt migration (Any information below is purely informational)
    • Depends: dsniff/s390x openssl
• duo-unix/amd64 (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/amd64 (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/amd64 openssl
• duo-unix/arm64 (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/arm64 (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/arm64 openssl
• duo-unix/armel (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/armel (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/armel openssl
• duo-unix/armhf (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/armhf (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/armhf openssl
• duo-unix/i386 (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/i386 (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/i386 openssl
• duo-unix/mips64el (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/mips64el (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/mips64el openssl
• duo-unix/mipsel (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/mipsel (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/mipsel openssl
• duo-unix/ppc64el (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/ppc64el (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/ppc64el openssl
• duo-unix/s390x (1.11.3-1 to 1.11.3-1)
  • Migration status for duo-unix/s390x (1.11.3-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: duo-unix/s390x openssl
• e2guardian/amd64 (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/amd64 (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/amd64 openssl
• e2guardian/arm64 (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/arm64 (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/arm64 openssl
• e2guardian/armel (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/armel (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/armel openssl
• e2guardian/armhf (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/armhf (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/armhf openssl
• e2guardian/i386 (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/i386 (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/i386 openssl
• e2guardian/mips64el (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/mips64el (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/mips64el openssl
• e2guardian/mipsel (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/mipsel (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/mipsel openssl
• e2guardian/ppc64el (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/ppc64el (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/ppc64el openssl
• e2guardian/s390x (5.3.5-3 to 5.3.5-3)
  • Migration status for e2guardian/s390x (5.3.5-3 to 5.3.5-3): Will attempt migration (Any information below is purely informational)
    • Depends: e2guardian/s390x openssl
• ecdsautils_pu (0.4.1-1 to 0.3.2+git20151018-2+deb11u1)
  • Migration status for ecdsautils_pu (0.4.1-1 to 0.3.2+git20151018-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ecdsautils is newer in the target suite (0.4.1-1 0.3.2+git20151018-2+deb11u1)
• eclipse-titan/amd64 (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/amd64 (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/amd64 openssl
• eclipse-titan/arm64 (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/arm64 (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/arm64 openssl
• eclipse-titan/armel (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/armel (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/armel openssl
• eclipse-titan/armhf (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/armhf (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/armhf openssl
• eclipse-titan/i386 (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/i386 (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/i386 openssl
• eclipse-titan/mips64el (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/mips64el (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/mips64el openssl
• eclipse-titan/mipsel (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/mipsel (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/mipsel openssl
• eclipse-titan/ppc64el (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/ppc64el (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/ppc64el openssl
• eclipse-titan/s390x (8.1.1-1 to 8.1.1-1)
  • Migration status for eclipse-titan/s390x (8.1.1-1 to 8.1.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: eclipse-titan/s390x openssl
• eiskaltdcpp/amd64 (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/amd64 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/amd64 openssl
• eiskaltdcpp/arm64 (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/arm64 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/arm64 openssl
• eiskaltdcpp/armel (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/armel (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/armel openssl
• eiskaltdcpp/armhf (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/armhf (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/armhf openssl
• eiskaltdcpp/i386 (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/i386 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/i386 openssl
• eiskaltdcpp/mips64el (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/mips64el (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/mips64el openssl
• eiskaltdcpp/mipsel (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/mipsel (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/mipsel openssl
• eiskaltdcpp/ppc64el (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/ppc64el (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/ppc64el openssl
• eiskaltdcpp/s390x (2.4.2-1 to 2.4.2-1)
  • Migration status for eiskaltdcpp/s390x (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: eiskaltdcpp/s390x openssl
• eliom/amd64 (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/amd64 (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/amd64 js-of-ocaml/amd64 (not considered)
    • Invalidated by dependency
• eliom/arm64 (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/arm64 (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/arm64 js-of-ocaml/arm64 (not considered)
    • Invalidated by dependency
• eliom/armel (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/armel (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/armel js-of-ocaml/armel (not considered)
    • Invalidated by dependency
• eliom/armhf (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/armhf (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/armhf js-of-ocaml/armhf (not considered)
    • Invalidated by dependency
• eliom/i386 (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/i386 (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/i386 js-of-ocaml/i386 (not considered)
    • Invalidated by dependency
• eliom/mips64el (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/mips64el (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/mips64el js-of-ocaml/mips64el (not considered)
    • Invalidated by dependency
• eliom/mipsel (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/mipsel (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/mipsel js-of-ocaml/mipsel (not considered)
    • Invalidated by dependency
• eliom/ppc64el (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/ppc64el (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/ppc64el js-of-ocaml/ppc64el (not considered)
    • Invalidated by dependency
• eliom/s390x (9.4.0-2 to 9.4.0-2)
  • Migration status for eliom/s390x (9.4.0-2 to 9.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/s390x js-of-ocaml/s390x (not considered)
    • Invalidated by dependency
• encfs/amd64 (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/amd64 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/amd64 openssl
• encfs/arm64 (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/arm64 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/arm64 openssl
• encfs/armel (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/armel (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/armel openssl
• encfs/armhf (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/armhf (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/armhf openssl
• encfs/i386 (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/i386 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/i386 openssl
• encfs/mips64el (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/mips64el (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/mips64el openssl
• encfs/mipsel (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/mipsel (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/mipsel openssl
• encfs/ppc64el (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/ppc64el (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/ppc64el openssl
• encfs/s390x (1.9.5-1 to 1.9.5-1)
  • Migration status for encfs/s390x (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: encfs/s390x openssl
• epic4/amd64 (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/amd64 (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/amd64 openssl
• epic4/arm64 (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/arm64 (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/arm64 openssl
• epic4/armel (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/armel (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/armel openssl
• epic4/armhf (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/armhf (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/armhf openssl
• epic4/i386 (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/i386 (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/i386 openssl
• epic4/mips64el (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/mips64el (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/mips64el openssl
• epic4/mipsel (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/mipsel (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/mipsel openssl
• epic4/ppc64el (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/ppc64el (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/ppc64el openssl
• epic4/s390x (1:2.10.10-1 to 1:2.10.10-1)
  • Migration status for epic4/s390x (1:2.10.10-1 to 1:2.10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic4/s390x openssl
• epic5/amd64 (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/amd64 (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/amd64 openssl
• epic5/arm64 (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/arm64 (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/arm64 openssl
• epic5/armel (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/armel (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/armel openssl
• epic5/armhf (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/armhf (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/armhf openssl
• epic5/i386 (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/i386 (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/i386 openssl
• epic5/mips64el (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/mips64el (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/mips64el openssl
• epic5/mipsel (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/mipsel (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/mipsel openssl
• epic5/ppc64el (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/ppc64el (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/ppc64el openssl
• epic5/s390x (2.1.6-1 to 2.1.6-1)
  • Migration status for epic5/s390x (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: epic5/s390x openssl
• eurephia/amd64 (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/amd64 (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/amd64 openssl
• eurephia/arm64 (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/arm64 (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/arm64 openssl
• eurephia/armel (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/armel (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/armel openssl
• eurephia/armhf (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/armhf (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/armhf openssl
• eurephia/i386 (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/i386 (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/i386 openssl
• eurephia/mips64el (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/mips64el (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/mips64el openssl
• eurephia/mipsel (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/mipsel (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/mipsel openssl
• eurephia/ppc64el (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/ppc64el (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/ppc64el openssl
• eurephia/s390x (1.1.0-6.1 to 1.1.0-6.1)
  • Migration status for eurephia/s390x (1.1.0-6.1 to 1.1.0-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: eurephia/s390x openssl
• facter/amd64 (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/amd64 (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/amd64 openssl
• facter/arm64 (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/arm64 (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/arm64 openssl
• facter/armel (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/armel (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/armel openssl
• facter/armhf (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/armhf (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/armhf openssl
• facter/i386 (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/i386 (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/i386 openssl
• facter/mips64el (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/mips64el (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/mips64el openssl
• facter/mipsel (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/mipsel (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/mipsel openssl
• facter/ppc64el (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/ppc64el (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/ppc64el openssl
• facter/s390x (3.14.12-1.1 to 3.14.12-1.1)
  • Migration status for facter/s390x (3.14.12-1.1 to 3.14.12-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: facter/s390x openssl
• faifa/amd64 (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/amd64 (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/amd64 openssl
• faifa/arm64 (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/arm64 (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/arm64 openssl
• faifa/armel (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/armel (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/armel openssl
• faifa/armhf (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/armhf (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/armhf openssl
• faifa/i386 (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/i386 (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/i386 openssl
• faifa/mips64el (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/mips64el (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/mips64el openssl
• faifa/mipsel (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/mipsel (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/mipsel openssl
• faifa/ppc64el (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/ppc64el (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/ppc64el openssl
• faifa/s390x (0.2~svn82-2 to 0.2~svn82-2)
  • Migration status for faifa/s390x (0.2~svn82-2 to 0.2~svn82-2): Will attempt migration (Any information below is purely informational)
    • Depends: faifa/s390x openssl
• fastd/amd64 (22-2 to 22-2)
  • Migration status for fastd/amd64 (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/amd64 openssl
• fastd/arm64 (22-2 to 22-2)
  • Migration status for fastd/arm64 (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/arm64 openssl
• fastd/armel (22-2 to 22-2)
  • Migration status for fastd/armel (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/armel openssl
• fastd/armhf (22-2 to 22-2)
  • Migration status for fastd/armhf (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/armhf openssl
• fastd/i386 (22-2 to 22-2)
  • Migration status for fastd/i386 (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/i386 openssl
• fastd/mips64el (22-2 to 22-2)
  • Migration status for fastd/mips64el (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/mips64el openssl
• fastd/mipsel (22-2 to 22-2)
  • Migration status for fastd/mipsel (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/mipsel openssl
• fastd/ppc64el (22-2 to 22-2)
  • Migration status for fastd/ppc64el (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/ppc64el openssl
• fastd/s390x (22-2 to 22-2)
  • Migration status for fastd/s390x (22-2 to 22-2): Will attempt migration (Any information below is purely informational)
    • Depends: fastd/s390x openssl
• fastdds/amd64 (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/amd64 (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/amd64 openssl
• fastdds/arm64 (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/arm64 (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/arm64 openssl
• fastdds/armel (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/armel (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/armel openssl
• fastdds/armhf (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/armhf (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/armhf openssl
• fastdds/i386 (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/i386 (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/i386 openssl
• fastdds/mips64el (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/mips64el (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/mips64el openssl
• fastdds/mipsel (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/mipsel (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/mipsel openssl
• fastdds/ppc64el (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/ppc64el (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/ppc64el openssl
• fastdds/s390x (2.6.0+ds-3 to 2.6.0+ds-3)
  • Migration status for fastdds/s390x (2.6.0+ds-3 to 2.6.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Depends: fastdds/s390x openssl
• fdm/amd64 (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/amd64 (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/amd64 openssl
• fdm/arm64 (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/arm64 (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/arm64 openssl
• fdm/armel (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/armel (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/armel openssl
• fdm/armhf (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/armhf (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/armhf openssl
• fdm/i386 (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/i386 (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/i386 openssl
• fdm/mips64el (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/mips64el (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/mips64el openssl
• fdm/mipsel (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/mipsel (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/mipsel openssl
• fdm/ppc64el (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/ppc64el (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/ppc64el openssl
• fdm/s390x (1.9+git20181219-1 to 1.9+git20181219-1)
  • Migration status for fdm/s390x (1.9+git20181219-1 to 1.9+git20181219-1): Will attempt migration (Any information below is purely informational)
    • Depends: fdm/s390x openssl
• fetchmail/amd64 (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/amd64 (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/amd64 openssl
• fetchmail/arm64 (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/arm64 (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/arm64 openssl
• fetchmail/armel (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/armel (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/armel openssl
• fetchmail/armhf (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/armhf (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/armhf openssl
• fetchmail/i386 (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/i386 (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/i386 openssl
• fetchmail/mips64el (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/mips64el (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/mips64el openssl
• fetchmail/mipsel (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/mipsel (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/mipsel openssl
• fetchmail/ppc64el (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/ppc64el (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/ppc64el openssl
• fetchmail/s390x (6.4.30-1 to 6.4.30-1)
  • Migration status for fetchmail/s390x (6.4.30-1 to 6.4.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: fetchmail/s390x openssl
• ffmpeg_pu (7:4.4.2-1 to 7:4.3.4-0+deb11u1)
  • Migration status for ffmpeg_pu (7:4.4.2-1 to 7:4.3.4-0+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ffmpeg is newer in the target suite (7:4.4.2-1 7:4.3.4-0+deb11u1)
• firefox-esr_pu (91.10.0esr-1 to 91.9.1esr-1~deb11u1)
  • Migration status for firefox-esr_pu (91.10.0esr-1 to 91.9.1esr-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: firefox-esr is newer in the target suite (91.10.0esr-1 91.9.1esr-1~deb11u1)
• fort-validator/amd64 (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/amd64 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/amd64 openssl
• fort-validator/arm64 (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/arm64 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/arm64 openssl
• fort-validator/armel (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/armel (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/armel openssl
• fort-validator/armhf (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/armhf (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/armhf openssl
• fort-validator/i386 (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/i386 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/i386 openssl
• fort-validator/mips64el (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/mips64el (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/mips64el openssl
• fort-validator/mipsel (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/mipsel (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/mipsel openssl
• fort-validator/ppc64el (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/ppc64el (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/ppc64el openssl
• fort-validator/s390x (1.5.3-1 to 1.5.3-1)
  • Migration status for fort-validator/s390x (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: fort-validator/s390x openssl
• fossil/amd64 (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/amd64 (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/amd64 openssl
• fossil/arm64 (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/arm64 (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/arm64 openssl
• fossil/armel (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/armel (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/armel openssl
• fossil/armhf (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/armhf (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/armhf openssl
• fossil/i386 (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/i386 (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/i386 openssl
• fossil/mips64el (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/mips64el (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/mips64el openssl
• fossil/mipsel (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/mipsel (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/mipsel openssl
• fossil/ppc64el (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/ppc64el (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/ppc64el openssl
• fossil/s390x (1:2.18-2 to 1:2.18-2)
  • Migration status for fossil/s390x (1:2.18-2 to 1:2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: fossil/s390x openssl
• fqterm/amd64 (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/amd64 (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/amd64 openssl
• fqterm/arm64 (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/arm64 (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/arm64 openssl
• fqterm/armel (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/armel (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/armel openssl
• fqterm/armhf (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/armhf (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/armhf openssl
• fqterm/i386 (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/i386 (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/i386 openssl
• fqterm/mips64el (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/mips64el (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/mips64el openssl
• fqterm/mipsel (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/mipsel (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/mipsel openssl
• fqterm/ppc64el (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/ppc64el (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/ppc64el openssl
• fqterm/s390x (0.9.10.1-1 to 0.9.10.1-1)
  • Migration status for fqterm/s390x (0.9.10.1-1 to 0.9.10.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fqterm/s390x openssl
• freeipa/amd64 (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/amd64 (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/amd64 openssl
• freeipa/arm64 (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/arm64 (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/arm64 openssl
• freeipa/armel (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/armel (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/armel openssl
• freeipa/armhf (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/armhf (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/armhf openssl
• freeipa/i386 (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/i386 (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/i386 openssl
• freeipa/mips64el (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/mips64el (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/mips64el openssl
• freeipa/mipsel (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/mipsel (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/mipsel openssl
• freeipa/ppc64el (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/ppc64el (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/ppc64el openssl
• freeipa/s390x (4.9.8-1 to 4.9.8-1)
  • Migration status for freeipa/s390x (4.9.8-1 to 4.9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeipa/s390x openssl
• freerdp2/amd64 (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/amd64 (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/amd64 openssl
• freerdp2/arm64 (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/arm64 (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/arm64 openssl
• freerdp2/armel (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/armel (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/armel openssl
• freerdp2/armhf (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/armhf (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/armhf openssl
• freerdp2/i386 (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/i386 (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/i386 openssl
• freerdp2/mips64el (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/mips64el (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/mips64el openssl
• freerdp2/mipsel (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/mipsel (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/mipsel openssl
• freerdp2/ppc64el (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/ppc64el (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/ppc64el openssl
• freerdp2/s390x (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1)
  • Migration status for freerdp2/s390x (2.7.0+dfsg1-1 to 2.7.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: freerdp2/s390x openssl
• fsverity-utils/amd64 (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/amd64 (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/amd64 openssl
• fsverity-utils/arm64 (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/arm64 (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/arm64 openssl
• fsverity-utils/armel (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/armel (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/armel openssl
• fsverity-utils/armhf (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/armhf (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/armhf openssl
• fsverity-utils/i386 (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/i386 (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/i386 openssl
• fsverity-utils/mips64el (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/mips64el (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/mips64el openssl
• fsverity-utils/mipsel (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/mipsel (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/mipsel openssl
• fsverity-utils/ppc64el (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/ppc64el (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/ppc64el openssl
• fsverity-utils/s390x (1.4-1~exp1 to 1.4-1~exp1)
  • Migration status for fsverity-utils/s390x (1.4-1~exp1 to 1.4-1~exp1): Will attempt migration (Any information below is purely informational)
    • Depends: fsverity-utils/s390x openssl
• galera-3/amd64 (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/amd64 (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/amd64 openssl
• galera-3/arm64 (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/arm64 (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/arm64 openssl
• galera-3/armel (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/armel (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/armel openssl
• galera-3/armhf (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/armhf (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/armhf openssl
• galera-3/i386 (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/i386 (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/i386 openssl
• galera-3/mips64el (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/mips64el (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/mips64el openssl
• galera-3/mipsel (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/mipsel (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/mipsel openssl
• galera-3/ppc64el (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/ppc64el (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/ppc64el openssl
• galera-3/s390x (25.3.36-1 to 25.3.36-1)
  • Migration status for galera-3/s390x (25.3.36-1 to 25.3.36-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-3/s390x openssl
• galera-4/amd64 (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/amd64 (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/amd64 openssl
• galera-4/arm64 (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/arm64 (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/arm64 openssl
• galera-4/armel (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/armel (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/armel openssl
• galera-4/armhf (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/armhf (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/armhf openssl
• galera-4/i386 (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/i386 (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/i386 openssl
• galera-4/mips64el (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/mips64el (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/mips64el openssl
• galera-4/mipsel (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/mipsel (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/mipsel openssl
• galera-4/ppc64el (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/ppc64el (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/ppc64el openssl
• galera-4/s390x (26.4.11-1 to 26.4.11-1)
  • Migration status for galera-4/s390x (26.4.11-1 to 26.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: galera-4/s390x openssl
• gambas3/amd64 (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/amd64 (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/amd64 openssl
• gambas3/arm64 (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/arm64 (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/arm64 openssl
• gambas3/armel (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/armel (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/armel openssl
• gambas3/armhf (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/armhf (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/armhf openssl
• gambas3/i386 (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/i386 (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/i386 openssl
• gambas3/mips64el (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/mips64el (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/mips64el openssl
• gambas3/mipsel (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/mipsel (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/mipsel openssl
• gambas3/ppc64el (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/ppc64el (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/ppc64el openssl
• gambas3/s390x (3.17.2-1 to 3.17.2-1)
  • Migration status for gambas3/s390x (3.17.2-1 to 3.17.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gambas3/s390x openssl
• gambc/amd64 (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/amd64 (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/amd64 openssl
• gambc/arm64 (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/arm64 (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/arm64 openssl
• gambc/armel (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/armel (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/armel openssl
• gambc/armhf (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/armhf (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/armhf openssl
• gambc/i386 (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/i386 (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/i386 openssl
• gambc/mips64el (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/mips64el (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/mips64el openssl
• gambc/mipsel (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/mipsel (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/mipsel openssl
• gambc/ppc64el (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/ppc64el (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/ppc64el openssl
• gambc/s390x (4.9.3-1.2 to 4.9.3-1.2)
  • Migration status for gambc/s390x (4.9.3-1.2 to 4.9.3-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: gambc/s390x openssl
• gatling/amd64 (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/amd64 (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/amd64 openssl
• gatling/arm64 (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/arm64 (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/arm64 openssl
• gatling/armel (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/armel (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/armel openssl
• gatling/armhf (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/armhf (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/armhf openssl
• gatling/i386 (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/i386 (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/i386 openssl
• gatling/mips64el (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/mips64el (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/mips64el openssl
• gatling/mipsel (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/mipsel (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/mipsel openssl
• gatling/ppc64el (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/ppc64el (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/ppc64el openssl
• gatling/s390x (0.13-6.1 to 0.13-6.1)
  • Migration status for gatling/s390x (0.13-6.1 to 0.13-6.1): Will attempt migration (Any information below is purely informational)
    • Depends: gatling/s390x openssl
• gdal/amd64 (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/amd64 (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/amd64 openssl
• gdal/arm64 (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/arm64 (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/arm64 openssl
• gdal/armel (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/armel (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/armel openssl
• gdal/armhf (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/armhf (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/armhf openssl
• gdal/i386 (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/i386 (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/i386 openssl
• gdal/mips64el (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/mips64el (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/mips64el openssl
• gdal/mipsel (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/mipsel (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/mipsel openssl
• gdal/ppc64el (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/ppc64el (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/ppc64el openssl
• gdal/s390x (3.4.3+dfsg-1 to 3.4.3+dfsg-1)
  • Migration status for gdal/s390x (3.4.3+dfsg-1 to 3.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdal/s390x openssl
• gdb-bpf/amd64 (4 to 4)
  • Migration status for gdb-bpf/amd64 (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/amd64 gdb (not considered)
    • Depends: gdb-bpf/amd64 gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/arm64 (4 to 4)
  • Migration status for gdb-bpf/arm64 (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/arm64 gdb (not considered)
    • Depends: gdb-bpf/arm64 gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/armel (4 to 4)
  • Migration status for gdb-bpf/armel (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/armel gdb (not considered)
    • Depends: gdb-bpf/armel gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/armhf (4 to 4)
  • Migration status for gdb-bpf/armhf (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/armhf gdb (not considered)
    • Depends: gdb-bpf/armhf gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/i386 (4 to 4)
  • Migration status for gdb-bpf/i386 (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/i386 gdb (not considered)
    • Depends: gdb-bpf/i386 gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/mips64el (4 to 4)
  • Migration status for gdb-bpf/mips64el (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/mips64el gdb (not considered)
    • Depends: gdb-bpf/mips64el gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/mipsel (4 to 4)
  • Migration status for gdb-bpf/mipsel (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/mipsel gdb (not considered)
    • Depends: gdb-bpf/mipsel gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-bpf/s390x (4 to 4)
  • Migration status for gdb-bpf/s390x (4 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-bpf/s390x gdb (not considered)
    • Depends: gdb-bpf/s390x gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/amd64 (12 to 12)
  • Migration status for gdb-mingw-w64/amd64 (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/amd64 gdb (not considered)
    • Depends: gdb-mingw-w64/amd64 gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/arm64 (12 to 12)
  • Migration status for gdb-mingw-w64/arm64 (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/arm64 gdb (not considered)
    • Depends: gdb-mingw-w64/arm64 gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/armel (12 to 12)
  • Migration status for gdb-mingw-w64/armel (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/armel gdb (not considered)
    • Depends: gdb-mingw-w64/armel gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/armhf (12 to 12)
  • Migration status for gdb-mingw-w64/armhf (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/armhf gdb (not considered)
    • Depends: gdb-mingw-w64/armhf gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/i386 (12 to 12)
  • Migration status for gdb-mingw-w64/i386 (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/i386 gdb (not considered)
    • Depends: gdb-mingw-w64/i386 gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/mips64el (12 to 12)
  • Migration status for gdb-mingw-w64/mips64el (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/mips64el gdb (not considered)
    • Depends: gdb-mingw-w64/mips64el gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/mipsel (12 to 12)
  • Migration status for gdb-mingw-w64/mipsel (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/mipsel gdb (not considered)
    • Depends: gdb-mingw-w64/mipsel gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdb-mingw-w64/s390x (12 to 12)
  • Migration status for gdb-mingw-w64/s390x (12 to 12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gdb-mingw-w64/s390x gdb (not considered)
    • Depends: gdb-mingw-w64/s390x gdb (not considered)
    • Invalidated by built-using
    • Invalidated by dependency
• gdcm/amd64 (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/amd64 (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/amd64 openssl
• gdcm/arm64 (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/arm64 (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/arm64 openssl
• gdcm/armel (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/armel (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/armel openssl
• gdcm/armhf (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/armhf (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/armhf openssl
• gdcm/i386 (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/i386 (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/i386 openssl
• gdcm/mips64el (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/mips64el (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/mips64el openssl
• gdcm/mipsel (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/mipsel (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/mipsel openssl
• gdcm/ppc64el (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/ppc64el (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/ppc64el openssl
• gdcm/s390x (3.0.12-1 to 3.0.12-1)
  • Migration status for gdcm/s390x (3.0.12-1 to 3.0.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: gdcm/s390x openssl
• geeqie_pu (1:1.7.3-1 to 1:1.6-9+deb11u1)
  • Migration status for geeqie_pu (1:1.7.3-1 to 1:1.6-9+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: geeqie is newer in the target suite (1:1.7.3-1 1:1.6-9+deb11u1)
• gensio/amd64 (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/amd64 (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/amd64 openssl
• gensio/arm64 (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/arm64 (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/arm64 openssl
• gensio/armel (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/armel (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/armel openssl
• gensio/armhf (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/armhf (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/armhf openssl
• gensio/i386 (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/i386 (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/i386 openssl
• gensio/mips64el (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/mips64el (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/mips64el openssl
• gensio/mipsel (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/mipsel (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/mipsel openssl
• gensio/ppc64el (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/ppc64el (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/ppc64el openssl
• gensio/s390x (2.3.5-1 to 2.3.5-1)
  • Migration status for gensio/s390x (2.3.5-1 to 2.3.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: gensio/s390x openssl
• getdns/amd64 (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/amd64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/amd64 openssl
• getdns/arm64 (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/arm64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/arm64 openssl
• getdns/armel (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/armel (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/armel openssl
• getdns/armhf (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/armhf (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/armhf openssl
• getdns/i386 (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/i386 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/i386 openssl
• getdns/mips64el (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/mips64el (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/mips64el openssl
• getdns/mipsel (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/mipsel (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/mipsel openssl
• getdns/ppc64el (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/ppc64el (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/ppc64el openssl
• getdns/s390x (1.6.0-2 to 1.6.0-2)
  • Migration status for getdns/s390x (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: getdns/s390x openssl
• gfarm/amd64 (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/amd64 (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/amd64 openssl
• gfarm/arm64 (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/arm64 (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/arm64 openssl
• gfarm/armel (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/armel (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/armel openssl
• gfarm/armhf (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/armhf (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/armhf openssl
• gfarm/i386 (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/i386 (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/i386 openssl
• gfarm/mips64el (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/mips64el (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/mips64el openssl
• gfarm/mipsel (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/mipsel (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/mipsel openssl
• gfarm/ppc64el (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/ppc64el (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/ppc64el openssl
• gfarm/s390x (2.7.20+dfsg-1 to 2.7.20+dfsg-1)
  • Migration status for gfarm/s390x (2.7.20+dfsg-1 to 2.7.20+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gfarm/s390x openssl
• gftp/amd64 (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/amd64 (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/amd64 openssl
• gftp/arm64 (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/arm64 (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/arm64 openssl
• gftp/armel (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/armel (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/armel openssl
• gftp/armhf (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/armhf (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/armhf openssl
• gftp/i386 (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/i386 (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/i386 openssl
• gftp/mips64el (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/mips64el (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/mips64el openssl
• gftp/mipsel (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/mipsel (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/mipsel openssl
• gftp/ppc64el (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/ppc64el (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/ppc64el openssl
• gftp/s390x (2.9.1~beta-1 to 2.9.1~beta-1)
  • Migration status for gftp/s390x (2.9.1~beta-1 to 2.9.1~beta-1): Will attempt migration (Any information below is purely informational)
    • Depends: gftp/s390x openssl
• glasscoder/amd64 (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/amd64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/amd64 openssl
• glasscoder/arm64 (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/arm64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/arm64 openssl
• glasscoder/armel (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/armel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/armel openssl
• glasscoder/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/armhf openssl
• glasscoder/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/i386 openssl
• glasscoder/mips64el (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/mips64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/mips64el openssl
• glasscoder/mipsel (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/mipsel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/mipsel openssl
• glasscoder/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/ppc64el openssl
• glasscoder/s390x (1.0.4-1 to 1.0.4-1)
  • Migration status for glasscoder/s390x (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: glasscoder/s390x openssl
• glirc/amd64 (2.36-3 to 2.36-3)
  • Migration status for glirc/amd64 (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/amd64 openssl
• glirc/arm64 (2.36-3 to 2.36-3)
  • Migration status for glirc/arm64 (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/arm64 openssl
• glirc/armel (2.36-3 to 2.36-3)
  • Migration status for glirc/armel (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/armel openssl
• glirc/armhf (2.36-3 to 2.36-3)
  • Migration status for glirc/armhf (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/armhf openssl
• glirc/i386 (2.36-3 to 2.36-3)
  • Migration status for glirc/i386 (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/i386 openssl
• glirc/mips64el (2.36-3 to 2.36-3)
  • Migration status for glirc/mips64el (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/mips64el openssl
• glirc/mipsel (2.36-3 to 2.36-3)
  • Migration status for glirc/mipsel (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/mipsel openssl
• glirc/ppc64el (2.36-3 to 2.36-3)
  • Migration status for glirc/ppc64el (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/ppc64el openssl
• glirc/s390x (2.36-3 to 2.36-3)
  • Migration status for glirc/s390x (2.36-3 to 2.36-3): Will attempt migration (Any information below is purely informational)
    • Depends: glirc/s390x openssl
• globus-gass-cache/amd64 (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/amd64 (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/amd64 openssl
• globus-gass-cache/arm64 (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/arm64 (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/arm64 openssl
• globus-gass-cache/armel (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/armel (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/armel openssl
• globus-gass-cache/armhf (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/armhf (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/armhf openssl
• globus-gass-cache/i386 (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/i386 (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/i386 openssl
• globus-gass-cache/mips64el (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/mips64el (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/mips64el openssl
• globus-gass-cache/mipsel (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/mipsel (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/mipsel openssl
• globus-gass-cache/ppc64el (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/ppc64el (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/ppc64el openssl
• globus-gass-cache/s390x (10.3-1 to 10.3-1)
  • Migration status for globus-gass-cache/s390x (10.3-1 to 10.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-cache/s390x openssl
• globus-gridmap-eppn-callout/amd64 (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/amd64 (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/amd64 openssl
• globus-gridmap-eppn-callout/arm64 (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/arm64 (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/arm64 openssl
• globus-gridmap-eppn-callout/armel (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/armel (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/armel openssl
• globus-gridmap-eppn-callout/armhf (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/armhf (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/armhf openssl
• globus-gridmap-eppn-callout/i386 (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/i386 (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/i386 openssl
• globus-gridmap-eppn-callout/mips64el (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/mips64el (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/mips64el openssl
• globus-gridmap-eppn-callout/mipsel (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/mipsel (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/mipsel openssl
• globus-gridmap-eppn-callout/ppc64el (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/ppc64el (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/ppc64el openssl
• globus-gridmap-eppn-callout/s390x (2.2-2 to 2.2-2)
  • Migration status for globus-gridmap-eppn-callout/s390x (2.2-2 to 2.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-eppn-callout/s390x openssl
• globus-gridmap-verify-myproxy-callout/amd64 (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/amd64 (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/amd64 openssl
• globus-gridmap-verify-myproxy-callout/arm64 (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/arm64 (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/arm64 openssl
• globus-gridmap-verify-myproxy-callout/armel (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/armel (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/armel openssl
• globus-gridmap-verify-myproxy-callout/armhf (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/armhf (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/armhf openssl
• globus-gridmap-verify-myproxy-callout/i386 (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/i386 (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/i386 openssl
• globus-gridmap-verify-myproxy-callout/mips64el (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/mips64el (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/mips64el openssl
• globus-gridmap-verify-myproxy-callout/mipsel (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/mipsel (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/mipsel openssl
• globus-gridmap-verify-myproxy-callout/ppc64el (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/ppc64el (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/ppc64el openssl
• globus-gridmap-verify-myproxy-callout/s390x (3.2-2 to 3.2-2)
  • Migration status for globus-gridmap-verify-myproxy-callout/s390x (3.2-2 to 3.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridmap-verify-myproxy-callout/s390x openssl
• globus-gsi-callback/amd64 (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/amd64 (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/amd64 openssl
• globus-gsi-callback/arm64 (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/arm64 (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/arm64 openssl
• globus-gsi-callback/armel (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/armel (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/armel openssl
• globus-gsi-callback/armhf (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/armhf (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/armhf openssl
• globus-gsi-callback/i386 (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/i386 (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/i386 openssl
• globus-gsi-callback/mips64el (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/mips64el (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/mips64el openssl
• globus-gsi-callback/mipsel (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/mipsel (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/mipsel openssl
• globus-gsi-callback/ppc64el (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/ppc64el (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/ppc64el openssl
• globus-gsi-callback/s390x (6.2-1 to 6.2-1)
  • Migration status for globus-gsi-callback/s390x (6.2-1 to 6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-callback/s390x openssl
• globus-gsi-credential/amd64 (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/amd64 (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/amd64 openssl
• globus-gsi-credential/arm64 (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/arm64 (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/arm64 openssl
• globus-gsi-credential/armel (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/armel (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/armel openssl
• globus-gsi-credential/armhf (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/armhf (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/armhf openssl
• globus-gsi-credential/i386 (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/i386 (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/i386 openssl
• globus-gsi-credential/mips64el (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/mips64el (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/mips64el openssl
• globus-gsi-credential/mipsel (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/mipsel (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/mipsel openssl
• globus-gsi-credential/ppc64el (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/ppc64el (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/ppc64el openssl
• globus-gsi-credential/s390x (8.3-1 to 8.3-1)
  • Migration status for globus-gsi-credential/s390x (8.3-1 to 8.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-credential/s390x openssl
• globus-gsi-proxy-ssl/amd64 (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/amd64 (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/amd64 openssl
• globus-gsi-proxy-ssl/arm64 (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/arm64 (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/arm64 openssl
• globus-gsi-proxy-ssl/armel (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/armel (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/armel openssl
• globus-gsi-proxy-ssl/armhf (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/armhf (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/armhf openssl
• globus-gsi-proxy-ssl/i386 (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/i386 (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/i386 openssl
• globus-gsi-proxy-ssl/mips64el (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/mips64el (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/mips64el openssl
• globus-gsi-proxy-ssl/mipsel (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/mipsel (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/mipsel openssl
• globus-gsi-proxy-ssl/ppc64el (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/ppc64el (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/ppc64el openssl
• globus-gsi-proxy-ssl/s390x (6.5-1 to 6.5-1)
  • Migration status for globus-gsi-proxy-ssl/s390x (6.5-1 to 6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-ssl/s390x openssl
• globus-openssl-module/amd64 (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/amd64 (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/amd64 openssl
• globus-openssl-module/arm64 (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/arm64 (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/arm64 openssl
• globus-openssl-module/armel (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/armel (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/armel openssl
• globus-openssl-module/armhf (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/armhf (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/armhf openssl
• globus-openssl-module/i386 (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/i386 (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/i386 openssl
• globus-openssl-module/mips64el (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/mips64el (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/mips64el openssl
• globus-openssl-module/mipsel (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/mipsel (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/mipsel openssl
• globus-openssl-module/ppc64el (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/ppc64el (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/ppc64el openssl
• globus-openssl-module/s390x (5.2-1 to 5.2-1)
  • Migration status for globus-openssl-module/s390x (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-openssl-module/s390x openssl
• gnubiff/amd64 (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/amd64 (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/amd64 openssl
• gnubiff/arm64 (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/arm64 (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/arm64 openssl
• gnubiff/armel (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/armel (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/armel openssl
• gnubiff/armhf (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/armhf (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/armhf openssl
• gnubiff/i386 (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/i386 (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/i386 openssl
• gnubiff/mips64el (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/mips64el (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/mips64el openssl
• gnubiff/mipsel (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/mipsel (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/mipsel openssl
• gnubiff/ppc64el (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/ppc64el (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/ppc64el openssl
• gnubiff/s390x (2.2.17-4 to 2.2.17-4)
  • Migration status for gnubiff/s390x (2.2.17-4 to 2.2.17-4): Will attempt migration (Any information below is purely informational)
    • Depends: gnubiff/s390x openssl
• gnupg-pkcs11-scd/amd64 (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/amd64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/amd64 openssl
• gnupg-pkcs11-scd/arm64 (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/arm64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/arm64 openssl
• gnupg-pkcs11-scd/armel (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/armel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/armel openssl
• gnupg-pkcs11-scd/armhf (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/armhf (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/armhf openssl
• gnupg-pkcs11-scd/i386 (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/i386 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/i386 openssl
• gnupg-pkcs11-scd/mips64el (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/mips64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/mips64el openssl
• gnupg-pkcs11-scd/mipsel (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/mipsel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/mipsel openssl
• gnupg-pkcs11-scd/ppc64el (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/ppc64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/ppc64el openssl
• gnupg-pkcs11-scd/s390x (0.9.2-1 to 0.9.2-1)
  • Migration status for gnupg-pkcs11-scd/s390x (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnupg-pkcs11-scd/s390x openssl
• goaccess/amd64 (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/amd64 (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/amd64 openssl
• goaccess/arm64 (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/arm64 (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/arm64 openssl
• goaccess/armel (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/armel (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/armel openssl
• goaccess/armhf (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/armhf (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/armhf openssl
• goaccess/i386 (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/i386 (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/i386 openssl
• goaccess/mips64el (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/mips64el (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/mips64el openssl
• goaccess/mipsel (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/mipsel (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/mipsel openssl
• goaccess/ppc64el (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/ppc64el (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/ppc64el openssl
• goaccess/s390x (1:1.5.5-1 to 1:1.5.5-1)
  • Migration status for goaccess/s390x (1:1.5.5-1 to 1:1.5.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: goaccess/s390x openssl
• gocryptfs/amd64 (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/amd64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/amd64 openssl
• gocryptfs/arm64 (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/arm64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/arm64 openssl
• gocryptfs/armel (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/armel (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/armel openssl
• gocryptfs/armhf (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/armhf (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/armhf openssl
• gocryptfs/i386 (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/i386 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/i386 openssl
• gocryptfs/mips64el (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/mips64el (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/mips64el openssl
• gocryptfs/mipsel (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/mipsel (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/mipsel openssl
• gocryptfs/ppc64el (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/ppc64el (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/ppc64el openssl
• gocryptfs/s390x (2.2.1-1 to 2.2.1-1)
  • Migration status for gocryptfs/s390x (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gocryptfs/s390x openssl
• gridengine/amd64 (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/amd64 (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/amd64 openssl
• gridengine/arm64 (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/arm64 (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/arm64 openssl
• gridengine/armel (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/armel (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/armel openssl
• gridengine/armhf (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/armhf (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/armhf openssl
• gridengine/i386 (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/i386 (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/i386 openssl
• gridengine/mips64el (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/mips64el (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/mips64el openssl
• gridengine/mipsel (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/mipsel (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/mipsel openssl
• gridengine/ppc64el (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/ppc64el (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/ppc64el openssl
• gridengine/s390x (8.1.9+dfsg-10 to 8.1.9+dfsg-10)
  • Migration status for gridengine/s390x (8.1.9+dfsg-10 to 8.1.9+dfsg-10): Will attempt migration (Any information below is purely informational)
    • Depends: gridengine/s390x openssl
• gridsite/amd64 (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/amd64 (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/amd64 openssl
• gridsite/arm64 (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/arm64 (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/arm64 openssl
• gridsite/armel (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/armel (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/armel openssl
• gridsite/armhf (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/armhf (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/armhf openssl
• gridsite/i386 (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/i386 (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/i386 openssl
• gridsite/mips64el (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/mips64el (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/mips64el openssl
• gridsite/mipsel (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/mipsel (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/mipsel openssl
• gridsite/ppc64el (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/ppc64el (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/ppc64el openssl
• gridsite/s390x (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3)
  • Migration status for gridsite/s390x (3.0.0~20180202git2fdbc6f-3 to 3.0.0~20180202git2fdbc6f-3): Will attempt migration (Any information below is purely informational)
    • Depends: gridsite/s390x openssl
• grisbi/amd64 (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/amd64 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/amd64 openssl
• grisbi/arm64 (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/arm64 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/arm64 openssl
• grisbi/armel (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/armel (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/armel openssl
• grisbi/armhf (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/armhf (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/armhf openssl
• grisbi/i386 (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/i386 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/i386 openssl
• grisbi/mips64el (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/mips64el (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/mips64el openssl
• grisbi/mipsel (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/mipsel (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/mipsel openssl
• grisbi/ppc64el (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/ppc64el (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/ppc64el openssl
• grisbi/s390x (2.0.5-1 to 2.0.5-1)
  • Migration status for grisbi/s390x (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: grisbi/s390x openssl
• growl-for-linux/amd64 (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/amd64 (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/amd64 openssl
• growl-for-linux/arm64 (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/arm64 (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/arm64 openssl
• growl-for-linux/armel (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/armel (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/armel openssl
• growl-for-linux/armhf (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/armhf (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/armhf openssl
• growl-for-linux/i386 (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/i386 (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/i386 openssl
• growl-for-linux/mips64el (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/mips64el (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/mips64el openssl
• growl-for-linux/mipsel (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/mipsel (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/mipsel openssl
• growl-for-linux/ppc64el (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/ppc64el (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/ppc64el openssl
• growl-for-linux/s390x (0.8.5-8 to 0.8.5-8)
  • Migration status for growl-for-linux/s390x (0.8.5-8 to 0.8.5-8): Will attempt migration (Any information below is purely informational)
    • Depends: growl-for-linux/s390x openssl
• grpc/amd64 (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/amd64 (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/amd64 openssl
• grpc/arm64 (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/arm64 (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/arm64 openssl
• grpc/armel (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/armel (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/armel openssl
• grpc/armhf (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/armhf (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/armhf openssl
• grpc/i386 (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/i386 (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/i386 openssl
• grpc/mips64el (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/mips64el (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/mips64el openssl
• grpc/mipsel (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/mipsel (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/mipsel openssl
• grpc/ppc64el (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/ppc64el (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/ppc64el openssl
• grpc/s390x (1.30.2-3 to 1.30.2-3)
  • Migration status for grpc/s390x (1.30.2-3 to 1.30.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: grpc/s390x openssl
• grub-customizer/amd64 (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/amd64 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/amd64 openssl
• grub-customizer/arm64 (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/arm64 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/arm64 openssl
• grub-customizer/armel (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/armel (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/armel openssl
• grub-customizer/armhf (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/armhf (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/armhf openssl
• grub-customizer/i386 (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/i386 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/i386 openssl
• grub-customizer/mips64el (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/mips64el (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/mips64el openssl
• grub-customizer/mipsel (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/mipsel (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/mipsel openssl
• grub-customizer/ppc64el (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/ppc64el (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/ppc64el openssl
• grub-customizer/s390x (5.1.0-3 to 5.1.0-3)
  • Migration status for grub-customizer/s390x (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: grub-customizer/s390x openssl
• grunt_pu (1.5.3-1 to 1.3.0-1+deb11u1)
  • Migration status for grunt_pu (1.5.3-1 to 1.3.0-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: grunt is newer in the target suite (1.5.3-1 1.3.0-1+deb11u1)
• gsoap/amd64 (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/amd64 (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/amd64 openssl
• gsoap/arm64 (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/arm64 (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/arm64 openssl
• gsoap/armel (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/armel (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/armel openssl
• gsoap/armhf (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/armhf (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/armhf openssl
• gsoap/i386 (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/i386 (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/i386 openssl
• gsoap/mips64el (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/mips64el (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/mips64el openssl
• gsoap/mipsel (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/mipsel (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/mipsel openssl
• gsoap/ppc64el (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/ppc64el (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/ppc64el openssl
• gsoap/s390x (2.8.117-2 to 2.8.117-2)
  • Migration status for gsoap/s390x (2.8.117-2 to 2.8.117-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsoap/s390x openssl
• gsocket/amd64 (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/amd64 (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/amd64 openssl
• gsocket/arm64 (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/arm64 (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/arm64 openssl
• gsocket/armel (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/armel (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/armel openssl
• gsocket/armhf (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/armhf (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/armhf openssl
• gsocket/i386 (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/i386 (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/i386 openssl
• gsocket/mips64el (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/mips64el (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/mips64el openssl
• gsocket/mipsel (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/mipsel (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/mipsel openssl
• gsocket/ppc64el (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/ppc64el (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/ppc64el openssl
• gsocket/s390x (1.4.33-2 to 1.4.33-2)
  • Migration status for gsocket/s390x (1.4.33-2 to 1.4.33-2): Will attempt migration (Any information below is purely informational)
    • Depends: gsocket/s390x openssl
• gss-ntlmssp/amd64 (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/amd64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/amd64 openssl
• gss-ntlmssp/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/arm64 openssl
• gss-ntlmssp/armel (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/armel (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/armel openssl
• gss-ntlmssp/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/armhf openssl
• gss-ntlmssp/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/i386 openssl
• gss-ntlmssp/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/mips64el openssl
• gss-ntlmssp/mipsel (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/mipsel (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/mipsel openssl
• gss-ntlmssp/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/ppc64el openssl
• gss-ntlmssp/s390x (1.0.0-1 to 1.0.0-1)
  • Migration status for gss-ntlmssp/s390x (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: gss-ntlmssp/s390x openssl
• gst-plugins-bad1.0/amd64 (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/amd64 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/amd64 openssl
• gst-plugins-bad1.0/arm64 (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/arm64 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/arm64 openssl
• gst-plugins-bad1.0/armel (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/armel (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/armel openssl
• gst-plugins-bad1.0/armhf (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/armhf (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/armhf openssl
• gst-plugins-bad1.0/i386 (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/i386 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/i386 openssl
• gst-plugins-bad1.0/mips64el (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/mips64el (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/mips64el openssl
• gst-plugins-bad1.0/mipsel (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/mipsel (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/mipsel openssl
• gst-plugins-bad1.0/ppc64el (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/ppc64el (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/ppc64el openssl
• gst-plugins-bad1.0/s390x (1.20.2-1 to 1.20.2-1)
  • Migration status for gst-plugins-bad1.0/s390x (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: gst-plugins-bad1.0/s390x openssl
• gvpe/amd64 (3.1-2 to 3.1-2)
  • Migration status for gvpe/amd64 (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/amd64 openssl
• gvpe/arm64 (3.1-2 to 3.1-2)
  • Migration status for gvpe/arm64 (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/arm64 openssl
• gvpe/armel (3.1-2 to 3.1-2)
  • Migration status for gvpe/armel (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/armel openssl
• gvpe/armhf (3.1-2 to 3.1-2)
  • Migration status for gvpe/armhf (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/armhf openssl
• gvpe/i386 (3.1-2 to 3.1-2)
  • Migration status for gvpe/i386 (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/i386 openssl
• gvpe/mips64el (3.1-2 to 3.1-2)
  • Migration status for gvpe/mips64el (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/mips64el openssl
• gvpe/mipsel (3.1-2 to 3.1-2)
  • Migration status for gvpe/mipsel (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/mipsel openssl
• gvpe/ppc64el (3.1-2 to 3.1-2)
  • Migration status for gvpe/ppc64el (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/ppc64el openssl
• gvpe/s390x (3.1-2 to 3.1-2)
  • Migration status for gvpe/s390x (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: gvpe/s390x openssl
• gzip_pu (1.12-1 to 1.10-4+deb11u1)
  • Migration status for gzip_pu (1.12-1 to 1.10-4+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: gzip is newer in the target suite (1.12-1 1.10-4+deb11u1)
• h2o/amd64 (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/amd64 (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/amd64 openssl
• h2o/arm64 (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/arm64 (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/arm64 openssl
• h2o/armel (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/armel (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/armel openssl
• h2o/armhf (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/armhf (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/armhf openssl
• h2o/i386 (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/i386 (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/i386 openssl
• h2o/mips64el (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/mips64el (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/mips64el openssl
• h2o/mipsel (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/mipsel (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/mipsel openssl
• h2o/ppc64el (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/ppc64el (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/ppc64el openssl
• h2o/s390x (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2)
  • Migration status for h2o/s390x (2.2.5+dfsg2-6.2 to 2.2.5+dfsg2-6.2): Will attempt migration (Any information below is purely informational)
    • Depends: h2o/s390x openssl
• haskell-doctemplates/amd64 (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/amd64 (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/amd64 to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/amd64 uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/amd64 to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/amd64 uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/amd64 to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/amd64 uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/amd64 to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/amd64 uninstallable
    • Depends: haskell-doctemplates/amd64 haskell-hsyaml
• haskell-doctemplates/arm64 (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/arm64 (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/arm64 to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/arm64 uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/arm64 to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/arm64 uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/arm64 to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/arm64 uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/arm64 to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/arm64 uninstallable
    • Depends: haskell-doctemplates/arm64 haskell-hsyaml
• haskell-doctemplates/armel (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/armel (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/armel to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/armel uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/armel to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/armel uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/armel to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/armel uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/armel to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/armel uninstallable
    • Depends: haskell-doctemplates/armel haskell-hsyaml
• haskell-doctemplates/armhf (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/armhf (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/armhf to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/armhf uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/armhf to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/armhf uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/armhf to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/armhf uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/armhf to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/armhf uninstallable
    • Depends: haskell-doctemplates/armhf haskell-hsyaml
• haskell-doctemplates/i386 (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/i386 (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/i386 to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/i386 uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/i386 to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/i386 uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/i386 to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/i386 uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/i386 to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/i386 uninstallable
    • Depends: haskell-doctemplates/i386 haskell-hsyaml
• haskell-doctemplates/mips64el (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/mips64el (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/mips64el to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/mips64el uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/mips64el to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/mips64el uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/mips64el to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/mips64el uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/mips64el to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/mips64el uninstallable
    • Depends: haskell-doctemplates/mips64el haskell-hsyaml
• haskell-doctemplates/mipsel (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/mipsel (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/mipsel to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/mipsel uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/mipsel to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/mipsel uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/mipsel to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/mipsel uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/mipsel to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/mipsel uninstallable
    • Depends: haskell-doctemplates/mipsel haskell-hsyaml
• haskell-doctemplates/ppc64el (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/ppc64el (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/ppc64el to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/ppc64el uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/ppc64el to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/ppc64el uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/ppc64el to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/ppc64el uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/ppc64el to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/ppc64el uninstallable
    • Depends: haskell-doctemplates/ppc64el haskell-hsyaml
• haskell-doctemplates/s390x (0.8.2-1 to 0.8.2-1)
  • Migration status for haskell-doctemplates/s390x (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/s390x to testing makes libghc-gitit-dev/0.15.1.0+dfsg-1/s390x uninstallable
    • migrating libghc-doctemplates-dev/0.8.2-1+b1/s390x to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/s390x uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/s390x to testing makes libghc-gitit-prof/0.15.1.0+dfsg-1/s390x uninstallable
    • migrating libghc-doctemplates-prof/0.8.2-1+b1/s390x to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/s390x uninstallable
    • Depends: haskell-doctemplates/s390x haskell-hsyaml
• haskell-haxr/amd64 (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/amd64 (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/amd64 haskell-hsopenssl
    • Depends: haskell-haxr/amd64 haskell-http-streams/amd64
    • Depends: haskell-haxr/amd64 openssl
• haskell-haxr/arm64 (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/arm64 (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/arm64 haskell-hsopenssl
    • Depends: haskell-haxr/arm64 haskell-http-streams/arm64
    • Depends: haskell-haxr/arm64 openssl
• haskell-haxr/armel (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/armel (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/armel haskell-hsopenssl
    • Depends: haskell-haxr/armel haskell-http-streams/armel
    • Depends: haskell-haxr/armel openssl
• haskell-haxr/armhf (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/armhf (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/armhf haskell-hsopenssl
    • Depends: haskell-haxr/armhf haskell-http-streams/armhf
    • Depends: haskell-haxr/armhf openssl
• haskell-haxr/i386 (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/i386 (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/i386 haskell-hsopenssl
    • Depends: haskell-haxr/i386 haskell-http-streams/i386
    • Depends: haskell-haxr/i386 openssl
• haskell-haxr/mips64el (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/mips64el (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/mips64el haskell-hsopenssl
    • Depends: haskell-haxr/mips64el haskell-http-streams/mips64el
    • Depends: haskell-haxr/mips64el openssl
• haskell-haxr/mipsel (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/mipsel (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/mipsel haskell-hsopenssl
    • Depends: haskell-haxr/mipsel haskell-http-streams/mipsel
    • Depends: haskell-haxr/mipsel openssl
• haskell-haxr/ppc64el (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/ppc64el (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/ppc64el haskell-hsopenssl
    • Depends: haskell-haxr/ppc64el haskell-http-streams/ppc64el
    • Depends: haskell-haxr/ppc64el openssl
• haskell-haxr/s390x (3000.11.4.1-1 to 3000.11.4.1-1)
  • Migration status for haskell-haxr/s390x (3000.11.4.1-1 to 3000.11.4.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-haxr/s390x haskell-hsopenssl
    • Depends: haskell-haxr/s390x haskell-http-streams/s390x
    • Depends: haskell-haxr/s390x openssl
• haskell-hookup/amd64 (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/amd64 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/amd64 haskell-hsopenssl
    • Depends: haskell-hookup/amd64 haskell-hsopenssl-x509-system/amd64
    • Depends: haskell-hookup/amd64 openssl
• haskell-hookup/arm64 (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/arm64 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/arm64 haskell-hsopenssl
    • Depends: haskell-hookup/arm64 haskell-hsopenssl-x509-system/arm64
    • Depends: haskell-hookup/arm64 openssl
• haskell-hookup/armel (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/armel (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/armel haskell-hsopenssl
    • Depends: haskell-hookup/armel haskell-hsopenssl-x509-system/armel
    • Depends: haskell-hookup/armel openssl
• haskell-hookup/armhf (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/armhf (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/armhf haskell-hsopenssl
    • Depends: haskell-hookup/armhf haskell-hsopenssl-x509-system/armhf
    • Depends: haskell-hookup/armhf openssl
• haskell-hookup/i386 (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/i386 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/i386 haskell-hsopenssl
    • Depends: haskell-hookup/i386 haskell-hsopenssl-x509-system/i386
    • Depends: haskell-hookup/i386 openssl
• haskell-hookup/mips64el (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/mips64el (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/mips64el haskell-hsopenssl
    • Depends: haskell-hookup/mips64el haskell-hsopenssl-x509-system/mips64el
    • Depends: haskell-hookup/mips64el openssl
• haskell-hookup/mipsel (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/mipsel (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/mipsel haskell-hsopenssl
    • Depends: haskell-hookup/mipsel haskell-hsopenssl-x509-system/mipsel
    • Depends: haskell-hookup/mipsel openssl
• haskell-hookup/ppc64el (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/ppc64el (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/ppc64el haskell-hsopenssl
    • Depends: haskell-hookup/ppc64el haskell-hsopenssl-x509-system/ppc64el
    • Depends: haskell-hookup/ppc64el openssl
• haskell-hookup/s390x (0.4-2 to 0.4-2)
  • Migration status for haskell-hookup/s390x (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hookup/s390x haskell-hsopenssl
    • Depends: haskell-hookup/s390x haskell-hsopenssl-x509-system/s390x
    • Depends: haskell-hookup/s390x openssl
• haskell-hsopenssl-x509-system/amd64 (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/amd64 (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/amd64 haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/amd64 openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/amd64 haskell-hookup/amd64
• haskell-hsopenssl-x509-system/arm64 (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/arm64 (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/arm64 haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/arm64 openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/arm64 haskell-hookup/arm64
• haskell-hsopenssl-x509-system/armel (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/armel (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/armel haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/armel openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/armel haskell-hookup/armel
• haskell-hsopenssl-x509-system/armhf (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/armhf (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/armhf haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/armhf openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/armhf haskell-hookup/armhf
• haskell-hsopenssl-x509-system/i386 (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/i386 (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/i386 haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/i386 openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/i386 haskell-hookup/i386
• haskell-hsopenssl-x509-system/mips64el (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/mips64el (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/mips64el haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/mips64el openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/mips64el haskell-hookup/mips64el
• haskell-hsopenssl-x509-system/mipsel (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/mipsel (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/mipsel haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/mipsel openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/mipsel haskell-hookup/mipsel
• haskell-hsopenssl-x509-system/ppc64el (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/ppc64el (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/ppc64el haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/ppc64el openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/ppc64el haskell-hookup/ppc64el
• haskell-hsopenssl-x509-system/s390x (0.1.0.3-5 to 0.1.0.3-5)
  • Migration status for haskell-hsopenssl-x509-system/s390x (0.1.0.3-5 to 0.1.0.3-5): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl-x509-system/s390x haskell-hsopenssl
    • Depends: haskell-hsopenssl-x509-system/s390x openssl
    • Implicit dependency: haskell-hsopenssl-x509-system/s390x haskell-hookup/s390x
• haskell-hsyaml-aeson/amd64 (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/amd64 (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b3/amd64 to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/amd64 uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b3/amd64 to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/amd64 uninstallable
    • Depends: haskell-hsyaml-aeson/amd64 haskell-hsyaml
• haskell-hsyaml-aeson/arm64 (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/arm64 (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b3/arm64 to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/arm64 uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b3/arm64 to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/arm64 uninstallable
    • Depends: haskell-hsyaml-aeson/arm64 haskell-hsyaml
• haskell-hsyaml-aeson/armel (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/armel (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b2/armel to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/armel uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b2/armel to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/armel uninstallable
    • Depends: haskell-hsyaml-aeson/armel haskell-hsyaml
• haskell-hsyaml-aeson/armhf (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/armhf (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b2/armhf to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/armhf uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b2/armhf to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/armhf uninstallable
    • Depends: haskell-hsyaml-aeson/armhf haskell-hsyaml
• haskell-hsyaml-aeson/i386 (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/i386 (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b2/i386 to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/i386 uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b2/i386 to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/i386 uninstallable
    • Depends: haskell-hsyaml-aeson/i386 haskell-hsyaml
• haskell-hsyaml-aeson/mips64el (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/mips64el (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b3/mips64el to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/mips64el uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b3/mips64el to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/mips64el uninstallable
    • Depends: haskell-hsyaml-aeson/mips64el haskell-hsyaml
• haskell-hsyaml-aeson/mipsel (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/mipsel (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b3/mipsel to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/mipsel uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b3/mipsel to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/mipsel uninstallable
    • Depends: haskell-hsyaml-aeson/mipsel haskell-hsyaml
• haskell-hsyaml-aeson/ppc64el (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/ppc64el (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b3/ppc64el to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/ppc64el uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b3/ppc64el to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/ppc64el uninstallable
    • Depends: haskell-hsyaml-aeson/ppc64el haskell-hsyaml
• haskell-hsyaml-aeson/s390x (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-hsyaml-aeson/s390x (0.2.0.0-2 to 0.2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-aeson-dev/0.2.0.0-2+b3/s390x to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/s390x uninstallable
    • migrating libghc-hsyaml-aeson-prof/0.2.0.0-2+b3/s390x to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/s390x uninstallable
    • Depends: haskell-hsyaml-aeson/s390x haskell-hsyaml
• haskell-http-streams/amd64 (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/amd64 (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/amd64 haskell-hsopenssl
    • Depends: haskell-http-streams/amd64 haskell-openssl-streams/amd64
    • Depends: haskell-http-streams/amd64 openssl
    • Implicit dependency: haskell-http-streams/amd64 haskell-haxr/amd64
• haskell-http-streams/arm64 (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/arm64 (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/arm64 haskell-hsopenssl
    • Depends: haskell-http-streams/arm64 haskell-openssl-streams/arm64
    • Depends: haskell-http-streams/arm64 openssl
    • Implicit dependency: haskell-http-streams/arm64 haskell-haxr/arm64
• haskell-http-streams/armel (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/armel (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/armel haskell-hsopenssl
    • Depends: haskell-http-streams/armel haskell-openssl-streams/armel
    • Depends: haskell-http-streams/armel openssl
    • Implicit dependency: haskell-http-streams/armel haskell-haxr/armel
• haskell-http-streams/armhf (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/armhf (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/armhf haskell-hsopenssl
    • Depends: haskell-http-streams/armhf haskell-openssl-streams/armhf
    • Depends: haskell-http-streams/armhf openssl
    • Implicit dependency: haskell-http-streams/armhf haskell-haxr/armhf
• haskell-http-streams/i386 (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/i386 (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/i386 haskell-hsopenssl
    • Depends: haskell-http-streams/i386 haskell-openssl-streams/i386
    • Depends: haskell-http-streams/i386 openssl
    • Implicit dependency: haskell-http-streams/i386 haskell-haxr/i386
• haskell-http-streams/mips64el (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/mips64el (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/mips64el haskell-hsopenssl
    • Depends: haskell-http-streams/mips64el haskell-openssl-streams/mips64el
    • Depends: haskell-http-streams/mips64el openssl
    • Implicit dependency: haskell-http-streams/mips64el haskell-haxr/mips64el
• haskell-http-streams/mipsel (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/mipsel (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/mipsel haskell-hsopenssl
    • Depends: haskell-http-streams/mipsel haskell-openssl-streams/mipsel
    • Depends: haskell-http-streams/mipsel openssl
    • Implicit dependency: haskell-http-streams/mipsel haskell-haxr/mipsel
• haskell-http-streams/ppc64el (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/ppc64el (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/ppc64el haskell-hsopenssl
    • Depends: haskell-http-streams/ppc64el haskell-openssl-streams/ppc64el
    • Depends: haskell-http-streams/ppc64el openssl
    • Implicit dependency: haskell-http-streams/ppc64el haskell-haxr/ppc64el
• haskell-http-streams/s390x (0.8.7.2-1 to 0.8.7.2-1)
  • Migration status for haskell-http-streams/s390x (0.8.7.2-1 to 0.8.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-http-streams/s390x haskell-hsopenssl
    • Depends: haskell-http-streams/s390x haskell-openssl-streams/s390x
    • Depends: haskell-http-streams/s390x openssl
    • Implicit dependency: haskell-http-streams/s390x haskell-haxr/s390x
• haskell-openssl-streams/amd64 (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/amd64 (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/amd64 haskell-hsopenssl
    • Depends: haskell-openssl-streams/amd64 openssl
    • Implicit dependency: haskell-openssl-streams/amd64 haskell-http-streams/amd64
• haskell-openssl-streams/arm64 (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/arm64 (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/arm64 haskell-hsopenssl
    • Depends: haskell-openssl-streams/arm64 openssl
    • Implicit dependency: haskell-openssl-streams/arm64 haskell-http-streams/arm64
• haskell-openssl-streams/armel (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/armel (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/armel haskell-hsopenssl
    • Depends: haskell-openssl-streams/armel openssl
    • Implicit dependency: haskell-openssl-streams/armel haskell-http-streams/armel
• haskell-openssl-streams/armhf (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/armhf (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/armhf haskell-hsopenssl
    • Depends: haskell-openssl-streams/armhf openssl
    • Implicit dependency: haskell-openssl-streams/armhf haskell-http-streams/armhf
• haskell-openssl-streams/i386 (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/i386 (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/i386 haskell-hsopenssl
    • Depends: haskell-openssl-streams/i386 openssl
    • Implicit dependency: haskell-openssl-streams/i386 haskell-http-streams/i386
• haskell-openssl-streams/mips64el (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/mips64el (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/mips64el haskell-hsopenssl
    • Depends: haskell-openssl-streams/mips64el openssl
    • Implicit dependency: haskell-openssl-streams/mips64el haskell-http-streams/mips64el
• haskell-openssl-streams/mipsel (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/mipsel (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/mipsel haskell-hsopenssl
    • Depends: haskell-openssl-streams/mipsel openssl
    • Implicit dependency: haskell-openssl-streams/mipsel haskell-http-streams/mipsel
• haskell-openssl-streams/ppc64el (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/ppc64el (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/ppc64el haskell-hsopenssl
    • Depends: haskell-openssl-streams/ppc64el openssl
    • Implicit dependency: haskell-openssl-streams/ppc64el haskell-http-streams/ppc64el
• haskell-openssl-streams/s390x (1.2.2.0-3 to 1.2.2.0-3)
  • Migration status for haskell-openssl-streams/s390x (1.2.2.0-3 to 1.2.2.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-openssl-streams/s390x haskell-hsopenssl
    • Depends: haskell-openssl-streams/s390x openssl
    • Implicit dependency: haskell-openssl-streams/s390x haskell-http-streams/s390x
• hcxdumptool/amd64 (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/amd64 (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/amd64 openssl
• hcxdumptool/arm64 (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/arm64 (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/arm64 openssl
• hcxdumptool/armel (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/armel (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/armel openssl
• hcxdumptool/armhf (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/armhf (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/armhf openssl
• hcxdumptool/i386 (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/i386 (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/i386 openssl
• hcxdumptool/mips64el (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/mips64el (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/mips64el openssl
• hcxdumptool/mipsel (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/mipsel (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/mipsel openssl
• hcxdumptool/ppc64el (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/ppc64el (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/ppc64el openssl
• hcxdumptool/s390x (6.2.6-1 to 6.2.6-1)
  • Migration status for hcxdumptool/s390x (6.2.6-1 to 6.2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxdumptool/s390x openssl
• hcxkeys/amd64 (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/amd64 (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/amd64 openssl
• hcxkeys/arm64 (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/arm64 (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/arm64 openssl
• hcxkeys/armel (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/armel (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/armel openssl
• hcxkeys/armhf (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/armhf (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/armhf openssl
• hcxkeys/i386 (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/i386 (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/i386 openssl
• hcxkeys/mips64el (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/mips64el (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/mips64el openssl
• hcxkeys/mipsel (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/mipsel (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/mipsel openssl
• hcxkeys/ppc64el (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/ppc64el (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/ppc64el openssl
• hcxkeys/s390x (6.2.1-1 to 6.2.1-1)
  • Migration status for hcxkeys/s390x (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxkeys/s390x openssl
• hcxtools/amd64 (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/amd64 (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/amd64 openssl
• hcxtools/arm64 (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/arm64 (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/arm64 openssl
• hcxtools/armel (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/armel (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/armel openssl
• hcxtools/armhf (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/armhf (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/armhf openssl
• hcxtools/i386 (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/i386 (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/i386 openssl
• hcxtools/mips64el (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/mips64el (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/mips64el openssl
• hcxtools/mipsel (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/mipsel (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/mipsel openssl
• hcxtools/ppc64el (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/ppc64el (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/ppc64el openssl
• hcxtools/s390x (6.2.7-1 to 6.2.7-1)
  • Migration status for hcxtools/s390x (6.2.7-1 to 6.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: hcxtools/s390x openssl
• hdf5/amd64 (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/amd64 (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/amd64 openssl
• hdf5/arm64 (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/arm64 (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/arm64 openssl
• hdf5/armel (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/armel (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/armel openssl
• hdf5/armhf (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/armhf (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/armhf openssl
• hdf5/i386 (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/i386 (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/i386 openssl
• hdf5/mips64el (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/mips64el (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/mips64el openssl
• hdf5/mipsel (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/mipsel (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/mipsel openssl
• hdf5/ppc64el (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/ppc64el (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/ppc64el openssl
• hdf5/s390x (1.10.7+repack-4 to 1.10.7+repack-4)
  • Migration status for hdf5/s390x (1.10.7+repack-4 to 1.10.7+repack-4): Will attempt migration (Any information below is purely informational)
    • Depends: hdf5/s390x openssl
• hdmi2usb-mode-switch_pu (0.0.1-3 to 0.0.1-2+deb11u1)
  • Migration status for hdmi2usb-mode-switch_pu (0.0.1-3 to 0.0.1-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: hdmi2usb-mode-switch is newer in the target suite (0.0.1-3 0.0.1-2+deb11u1)
• hexchat/amd64 (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/amd64 (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/amd64 openssl
• hexchat/arm64 (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/arm64 (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/arm64 openssl
• hexchat/armel (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/armel (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/armel openssl
• hexchat/armhf (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/armhf (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/armhf openssl
• hexchat/i386 (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/i386 (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/i386 openssl
• hexchat/mips64el (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/mips64el (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/mips64el openssl
• hexchat/mipsel (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/mipsel (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/mipsel openssl
• hexchat/ppc64el (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/ppc64el (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/ppc64el openssl
• hexchat/s390x (2.16.1-1 to 2.16.1-1)
  • Migration status for hexchat/s390x (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: hexchat/s390x openssl
• hexchat_pu (2.16.1-1 to 2.14.3-6+deb11u1)
  • Migration status for hexchat_pu (2.16.1-1 to 2.14.3-6+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: hexchat is newer in the target suite (2.16.1-1 2.14.3-6+deb11u1)
• hfsprogs/amd64 (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/amd64 (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/amd64 openssl
• hfsprogs/arm64 (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/arm64 (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/arm64 openssl
• hfsprogs/armel (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/armel (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/armel openssl
• hfsprogs/armhf (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/armhf (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/armhf openssl
• hfsprogs/i386 (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/i386 (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/i386 openssl
• hfsprogs/mips64el (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/mips64el (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/mips64el openssl
• hfsprogs/mipsel (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/mipsel (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/mipsel openssl
• hfsprogs/ppc64el (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/ppc64el (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/ppc64el openssl
• hfsprogs/s390x (540.1.linux3-5 to 540.1.linux3-5)
  • Migration status for hfsprogs/s390x (540.1.linux3-5 to 540.1.linux3-5): Will attempt migration (Any information below is purely informational)
    • Depends: hfsprogs/s390x openssl
• hopm/amd64 (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/amd64 (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/amd64 openssl
• hopm/arm64 (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/arm64 (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/arm64 openssl
• hopm/armel (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/armel (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/armel openssl
• hopm/armhf (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/armhf (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/armhf openssl
• hopm/i386 (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/i386 (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/i386 openssl
• hopm/mips64el (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/mips64el (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/mips64el openssl
• hopm/mipsel (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/mipsel (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/mipsel openssl
• hopm/ppc64el (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/ppc64el (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/ppc64el openssl
• hopm/s390x (1.1.10-1 to 1.1.10-1)
  • Migration status for hopm/s390x (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: hopm/s390x openssl
• htmldoc_pu (1.9.15-2 to 1.9.11-4+deb11u3)
  • Migration status for htmldoc_pu (1.9.15-2 to 1.9.11-4+deb11u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: htmldoc is newer in the target suite (1.9.15-2 1.9.11-4+deb11u3)
• htslib/amd64 (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/amd64 (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/amd64 openssl
• htslib/arm64 (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/arm64 (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/arm64 openssl
• htslib/armel (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/armel (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/armel openssl
• htslib/armhf (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/armhf (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/armhf openssl
• htslib/i386 (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/i386 (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/i386 openssl
• htslib/mips64el (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/mips64el (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/mips64el openssl
• htslib/mipsel (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/mipsel (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/mipsel openssl
• htslib/ppc64el (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/ppc64el (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/ppc64el openssl
• htslib/s390x (1.13+ds-2 to 1.13+ds-2)
  • Migration status for htslib/s390x (1.13+ds-2 to 1.13+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: htslib/s390x openssl
• httest/amd64 (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/amd64 (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/amd64 openssl
• httest/arm64 (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/arm64 (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/arm64 openssl
• httest/armel (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/armel (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/armel openssl
• httest/armhf (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/armhf (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/armhf openssl
• httest/i386 (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/i386 (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/i386 openssl
• httest/mips64el (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/mips64el (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/mips64el openssl
• httest/mipsel (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/mipsel (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/mipsel openssl
• httest/ppc64el (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/ppc64el (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/ppc64el openssl
• httest/s390x (2.4.23-1.2 to 2.4.23-1.2)
  • Migration status for httest/s390x (2.4.23-1.2 to 2.4.23-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: httest/s390x openssl
• httpdirfs-fuse/amd64 (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/amd64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/amd64 openssl
• httpdirfs-fuse/arm64 (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/arm64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/arm64 openssl
• httpdirfs-fuse/armel (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/armel (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/armel openssl
• httpdirfs-fuse/armhf (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/armhf (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/armhf openssl
• httpdirfs-fuse/i386 (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/i386 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/i386 openssl
• httpdirfs-fuse/mips64el (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/mips64el (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/mips64el openssl
• httpdirfs-fuse/mipsel (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/mipsel (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/mipsel openssl
• httpdirfs-fuse/ppc64el (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/ppc64el (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/ppc64el openssl
• httpdirfs-fuse/s390x (1.2.3-1 to 1.2.3-1)
  • Migration status for httpdirfs-fuse/s390x (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: httpdirfs-fuse/s390x openssl
• httperf/amd64 (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/amd64 (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/amd64 openssl
• httperf/arm64 (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/arm64 (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/arm64 openssl
• httperf/armel (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/armel (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/armel openssl
• httperf/armhf (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/armhf (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/armhf openssl
• httperf/i386 (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/i386 (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/i386 openssl
• httperf/mips64el (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/mips64el (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/mips64el openssl
• httperf/mipsel (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/mipsel (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/mipsel openssl
• httperf/ppc64el (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/ppc64el (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/ppc64el openssl
• httperf/s390x (0.9.0-9 to 0.9.0-9)
  • Migration status for httperf/s390x (0.9.0-9 to 0.9.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: httperf/s390x openssl
• httping/amd64 (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/amd64 (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/amd64 openssl
• httping/arm64 (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/arm64 (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/arm64 openssl
• httping/armel (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/armel (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/armel openssl
• httping/armhf (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/armhf (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/armhf openssl
• httping/i386 (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/i386 (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/i386 openssl
• httping/mips64el (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/mips64el (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/mips64el openssl
• httping/mipsel (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/mipsel (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/mipsel openssl
• httping/ppc64el (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/ppc64el (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/ppc64el openssl
• httping/s390x (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/s390x (2.5-5.2 to 2.5-5.2): Will attempt migration (Any information below is purely informational)
    • Depends: httping/s390x openssl
• httrack/amd64 (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/amd64 (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/amd64 openssl
• httrack/arm64 (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/arm64 (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/arm64 openssl
• httrack/armel (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/armel (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/armel openssl
• httrack/armhf (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/armhf (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/armhf openssl
• httrack/i386 (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/i386 (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/i386 openssl
• httrack/mips64el (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/mips64el (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/mips64el openssl
• httrack/mipsel (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/mipsel (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/mipsel openssl
• httrack/ppc64el (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/ppc64el (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/ppc64el openssl
• httrack/s390x (3.49.2-1.1 to 3.49.2-1.1)
  • Migration status for httrack/s390x (3.49.2-1.1 to 3.49.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: httrack/s390x openssl
• hydra/amd64 (9.3-3 to 9.3-3)
  • Migration status for hydra/amd64 (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/amd64 openssl
• hydra/arm64 (9.3-3 to 9.3-3)
  • Migration status for hydra/arm64 (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/arm64 openssl
• hydra/armel (9.3-3 to 9.3-3)
  • Migration status for hydra/armel (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/armel openssl
• hydra/armhf (9.3-3 to 9.3-3)
  • Migration status for hydra/armhf (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/armhf openssl
• hydra/i386 (9.3-3 to 9.3-3)
  • Migration status for hydra/i386 (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/i386 openssl
• hydra/mips64el (9.3-3 to 9.3-3)
  • Migration status for hydra/mips64el (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/mips64el openssl
• hydra/mipsel (9.3-3 to 9.3-3)
  • Migration status for hydra/mipsel (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/mipsel openssl
• hydra/ppc64el (9.3-3 to 9.3-3)
  • Migration status for hydra/ppc64el (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/ppc64el openssl
• hydra/s390x (9.3-3 to 9.3-3)
  • Migration status for hydra/s390x (9.3-3 to 9.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: hydra/s390x openssl
• i2pd/amd64 (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/amd64 (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/amd64 openssl
• i2pd/arm64 (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/arm64 (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/arm64 openssl
• i2pd/armel (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/armel (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/armel openssl
• i2pd/armhf (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/armhf (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/armhf openssl
• i2pd/i386 (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/i386 (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/i386 openssl
• i2pd/mips64el (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/mips64el (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/mips64el openssl
• i2pd/mipsel (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/mipsel (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/mipsel openssl
• i2pd/ppc64el (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/ppc64el (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/ppc64el openssl
• i2pd/s390x (2.41.0-1 to 2.41.0-1)
  • Migration status for i2pd/s390x (2.41.0-1 to 2.41.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: i2pd/s390x openssl
• ibm-3270/amd64 (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/amd64 (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/amd64 openssl
• ibm-3270/arm64 (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/arm64 (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/arm64 openssl
• ibm-3270/armel (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/armel (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/armel openssl
• ibm-3270/armhf (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/armhf (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/armhf openssl
• ibm-3270/i386 (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/i386 (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/i386 openssl
• ibm-3270/mips64el (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/mips64el (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/mips64el openssl
• ibm-3270/mipsel (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/mipsel (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/mipsel openssl
• ibm-3270/ppc64el (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/ppc64el (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/ppc64el openssl
• ibm-3270/s390x (4.1ga10-1.1 to 4.1ga10-1.1)
  • Migration status for ibm-3270/s390x (4.1ga10-1.1 to 4.1ga10-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ibm-3270/s390x openssl
• icecast2/amd64 (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/amd64 (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/amd64 openssl
• icecast2/arm64 (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/arm64 (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/arm64 openssl
• icecast2/armel (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/armel (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/armel openssl
• icecast2/armhf (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/armhf (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/armhf openssl
• icecast2/i386 (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/i386 (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/i386 openssl
• icecast2/mips64el (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/mips64el (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/mips64el openssl
• icecast2/mipsel (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/mipsel (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/mipsel openssl
• icecast2/ppc64el (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/ppc64el (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/ppc64el openssl
• icecast2/s390x (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/s390x (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: icecast2/s390x openssl
• icinga2/amd64 (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/amd64 (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/amd64 openssl
• icinga2/arm64 (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/arm64 (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/arm64 openssl
• icinga2/armel (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/armel (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/armel openssl
• icinga2/armhf (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/armhf (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/armhf openssl
• icinga2/i386 (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/i386 (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/i386 openssl
• icinga2/mips64el (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/mips64el (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/mips64el openssl
• icinga2/ppc64el (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/ppc64el (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/ppc64el openssl
• icinga2/s390x (2.13.3-1 to 2.13.3-1)
  • Migration status for icinga2/s390x (2.13.3-1 to 2.13.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: icinga2/s390x openssl
• identity4c/amd64 (1.0-1 to 1.0-1)
  • Migration status for identity4c/amd64 (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/amd64 openssl
• identity4c/arm64 (1.0-1 to 1.0-1)
  • Migration status for identity4c/arm64 (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/arm64 openssl
• identity4c/armel (1.0-1 to 1.0-1)
  • Migration status for identity4c/armel (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/armel openssl
• identity4c/armhf (1.0-1 to 1.0-1)
  • Migration status for identity4c/armhf (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/armhf openssl
• identity4c/i386 (1.0-1 to 1.0-1)
  • Migration status for identity4c/i386 (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/i386 openssl
• identity4c/mips64el (1.0-1 to 1.0-1)
  • Migration status for identity4c/mips64el (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/mips64el openssl
• identity4c/mipsel (1.0-1 to 1.0-1)
  • Migration status for identity4c/mipsel (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/mipsel openssl
• identity4c/ppc64el (1.0-1 to 1.0-1)
  • Migration status for identity4c/ppc64el (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/ppc64el openssl
• identity4c/s390x (1.0-1 to 1.0-1)
  • Migration status for identity4c/s390x (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: identity4c/s390x openssl
• idevicerestore/amd64 (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/amd64 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/amd64 openssl
• idevicerestore/arm64 (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/arm64 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/arm64 openssl
• idevicerestore/armel (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/armel (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/armel openssl
• idevicerestore/armhf (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/armhf (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/armhf openssl
• idevicerestore/i386 (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/i386 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/i386 openssl
• idevicerestore/mips64el (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/mips64el (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/mips64el openssl
• idevicerestore/mipsel (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/mipsel (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/mipsel openssl
• idevicerestore/ppc64el (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/ppc64el (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/ppc64el openssl
• idevicerestore/s390x (1.0.0-3 to 1.0.0-3)
  • Migration status for idevicerestore/s390x (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: idevicerestore/s390x openssl
• ike-scan/amd64 (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/amd64 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/amd64 openssl
• ike-scan/arm64 (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/arm64 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/arm64 openssl
• ike-scan/armel (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/armel (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/armel openssl
• ike-scan/armhf (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/armhf (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/armhf openssl
• ike-scan/i386 (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/i386 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/i386 openssl
• ike-scan/mips64el (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/mips64el (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/mips64el openssl
• ike-scan/mipsel (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/mipsel (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/mipsel openssl
• ike-scan/ppc64el (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/ppc64el (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/ppc64el openssl
• ike-scan/s390x (1.9.5-1 to 1.9.5-1)
  • Migration status for ike-scan/s390x (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: ike-scan/s390x openssl
• ima-evm-utils/amd64 (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/amd64 (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/amd64 openssl
• ima-evm-utils/arm64 (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/arm64 (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/arm64 openssl
• ima-evm-utils/armel (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/armel (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/armel openssl
• ima-evm-utils/armhf (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/armhf (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/armhf openssl
• ima-evm-utils/i386 (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/i386 (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/i386 openssl
• ima-evm-utils/mips64el (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/mips64el (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/mips64el openssl
• ima-evm-utils/mipsel (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/mipsel (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/mipsel openssl
• ima-evm-utils/ppc64el (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/ppc64el (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/ppc64el openssl
• ima-evm-utils/s390x (1.4-1.2 to 1.4-1.2)
  • Migration status for ima-evm-utils/s390x (1.4-1.2 to 1.4-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: ima-evm-utils/s390x openssl
• imapfilter/amd64 (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/amd64 (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/amd64 openssl
• imapfilter/arm64 (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/arm64 (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/arm64 openssl
• imapfilter/armel (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/armel (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/armel openssl
• imapfilter/armhf (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/armhf (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/armhf openssl
• imapfilter/i386 (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/i386 (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/i386 openssl
• imapfilter/mips64el (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/mips64el (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/mips64el openssl
• imapfilter/mipsel (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/mipsel (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/mipsel openssl
• imapfilter/ppc64el (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/ppc64el (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/ppc64el openssl
• imapfilter/s390x (1:2.7.5-1 to 1:2.7.5-1)
  • Migration status for imapfilter/s390x (1:2.7.5-1 to 1:2.7.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: imapfilter/s390x openssl
• imx-code-signing-tool/amd64 (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/amd64 (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/amd64 openssl
• imx-code-signing-tool/arm64 (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/arm64 (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/arm64 openssl
• imx-code-signing-tool/armel (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/armel (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/armel openssl
• imx-code-signing-tool/armhf (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/armhf (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/armhf openssl
• imx-code-signing-tool/i386 (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/i386 (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/i386 openssl
• imx-code-signing-tool/mips64el (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/mips64el (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/mips64el openssl
• imx-code-signing-tool/mipsel (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/mipsel (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/mipsel openssl
• imx-code-signing-tool/ppc64el (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/ppc64el (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/ppc64el openssl
• imx-code-signing-tool/s390x (3.3.1+dfsg-2 to 3.3.1+dfsg-2)
  • Migration status for imx-code-signing-tool/s390x (3.3.1+dfsg-2 to 3.3.1+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: imx-code-signing-tool/s390x openssl
• inn2/amd64 (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/amd64 (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/amd64 openssl
• inn2/arm64 (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/arm64 (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/arm64 openssl
• inn2/armel (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/armel (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/armel openssl
• inn2/armhf (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/armhf (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/armhf openssl
• inn2/i386 (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/i386 (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/i386 openssl
• inn2/mips64el (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/mips64el (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/mips64el openssl
• inn2/mipsel (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/mipsel (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/mipsel openssl
• inn2/ppc64el (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/ppc64el (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/ppc64el openssl
• inn2/s390x (2.6.5-1 to 2.6.5-1)
  • Migration status for inn2/s390x (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: inn2/s390x openssl
• intel-hdcp/amd64 (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/amd64 (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/amd64 openssl
• intel-hdcp/arm64 (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/arm64 (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/arm64 openssl
• intel-hdcp/armel (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/armel (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/armel openssl
• intel-hdcp/armhf (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/armhf (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/armhf openssl
• intel-hdcp/i386 (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/i386 (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/i386 openssl
• intel-hdcp/mips64el (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/mips64el (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/mips64el openssl
• intel-hdcp/mipsel (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/mipsel (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/mipsel openssl
• intel-hdcp/ppc64el (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/ppc64el (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/ppc64el openssl
• intel-hdcp/s390x (20.3.0-1 to 20.3.0-1)
  • Migration status for intel-hdcp/s390x (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: intel-hdcp/s390x openssl
• ipmitool/amd64 (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/amd64 (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/amd64 openssl
• ipmitool/arm64 (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/arm64 (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/arm64 openssl
• ipmitool/armel (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/armel (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/armel openssl
• ipmitool/armhf (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/armhf (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/armhf openssl
• ipmitool/i386 (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/i386 (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/i386 openssl
• ipmitool/mips64el (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/mips64el (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/mips64el openssl
• ipmitool/mipsel (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/mipsel (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/mipsel openssl
• ipmitool/ppc64el (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/ppc64el (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/ppc64el openssl
• ipmitool/s390x (1.8.18-11 to 1.8.18-11)
  • Migration status for ipmitool/s390x (1.8.18-11 to 1.8.18-11): Will attempt migration (Any information below is purely informational)
    • Depends: ipmitool/s390x openssl
• ipmiutil/amd64 (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/amd64 (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/amd64 openssl
• ipmiutil/arm64 (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/arm64 (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/arm64 openssl
• ipmiutil/armel (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/armel (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/armel openssl
• ipmiutil/armhf (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/armhf (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/armhf openssl
• ipmiutil/i386 (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/i386 (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/i386 openssl
• ipmiutil/mips64el (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/mips64el (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/mips64el openssl
• ipmiutil/mipsel (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/mipsel (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/mipsel openssl
• ipmiutil/ppc64el (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/ppc64el (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/ppc64el openssl
• ipmiutil/s390x (3.1.8-1 to 3.1.8-1)
  • Migration status for ipmiutil/s390x (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: ipmiutil/s390x openssl
• ircii/amd64 (20210328-2 to 20210328-2)
  • Migration status for ircii/amd64 (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/amd64 openssl
• ircii/arm64 (20210328-2 to 20210328-2)
  • Migration status for ircii/arm64 (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/arm64 openssl
• ircii/armel (20210328-2 to 20210328-2)
  • Migration status for ircii/armel (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/armel openssl
• ircii/armhf (20210328-2 to 20210328-2)
  • Migration status for ircii/armhf (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/armhf openssl
• ircii/i386 (20210328-2 to 20210328-2)
  • Migration status for ircii/i386 (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/i386 openssl
• ircii/mips64el (20210328-2 to 20210328-2)
  • Migration status for ircii/mips64el (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/mips64el openssl
• ircii/mipsel (20210328-2 to 20210328-2)
  • Migration status for ircii/mipsel (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/mipsel openssl
• ircii/ppc64el (20210328-2 to 20210328-2)
  • Migration status for ircii/ppc64el (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/ppc64el openssl
• ircii/s390x (20210328-2 to 20210328-2)
  • Migration status for ircii/s390x (20210328-2 to 20210328-2): Will attempt migration (Any information below is purely informational)
    • Depends: ircii/s390x openssl
• irssi/amd64 (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/amd64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/amd64 openssl
• irssi/arm64 (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/arm64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/arm64 openssl
• irssi/armel (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/armel (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/armel openssl
• irssi/armhf (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/armhf (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/armhf openssl
• irssi/i386 (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/i386 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/i386 openssl
• irssi/mips64el (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/mips64el (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/mips64el openssl
• irssi/mipsel (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/mipsel (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/mipsel openssl
• irssi/ppc64el (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/ppc64el (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/ppc64el openssl
• irssi/s390x (1.2.3-1 to 1.2.3-1)
  • Migration status for irssi/s390x (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: irssi/s390x openssl
• isc-kea/amd64 (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/amd64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/amd64 openssl
• isc-kea/arm64 (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/arm64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/arm64 openssl
• isc-kea/armel (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/armel (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/armel openssl
• isc-kea/armhf (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/armhf (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/armhf openssl
• isc-kea/i386 (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/i386 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/i386 openssl
• isc-kea/mips64el (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/mips64el (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/mips64el openssl
• isc-kea/mipsel (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/mipsel (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/mipsel openssl
• isc-kea/ppc64el (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/ppc64el (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/ppc64el openssl
• isc-kea/s390x (2.0.2-1 to 2.0.2-1)
  • Migration status for isc-kea/s390x (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: isc-kea/s390x openssl
• istgt/amd64 (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/amd64 (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/amd64 openssl
• istgt/arm64 (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/arm64 (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/arm64 openssl
• istgt/armel (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/armel (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/armel openssl
• istgt/armhf (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/armhf (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/armhf openssl
• istgt/i386 (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/i386 (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/i386 openssl
• istgt/mips64el (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/mips64el (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/mips64el openssl
• istgt/mipsel (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/mipsel (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/mipsel openssl
• istgt/ppc64el (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/ppc64el (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/ppc64el openssl
• istgt/s390x (0.4~20111008-4 to 0.4~20111008-4)
  • Migration status for istgt/s390x (0.4~20111008-4 to 0.4~20111008-4): Will attempt migration (Any information below is purely informational)
    • Depends: istgt/s390x openssl
• isync/amd64 (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/amd64 (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/amd64 openssl
• isync/arm64 (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/arm64 (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/arm64 openssl
• isync/armel (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/armel (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/armel openssl
• isync/armhf (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/armhf (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/armhf openssl
• isync/i386 (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/i386 (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/i386 openssl
• isync/mips64el (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/mips64el (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/mips64el openssl
• isync/mipsel (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/mipsel (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/mipsel openssl
• isync/ppc64el (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/ppc64el (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/ppc64el openssl
• isync/s390x (1.4.4-3 to 1.4.4-3)
  • Migration status for isync/s390x (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
    • Depends: isync/s390x openssl
• janus/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/amd64 openssl
• janus/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/arm64 openssl
• janus/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/armel openssl
• janus/armhf (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/armhf (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/armhf openssl
• janus/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/i386 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/i386 openssl
• janus/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/mips64el openssl
• janus/mipsel (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/mipsel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/mipsel openssl
• janus/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/ppc64el openssl
• janus/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for janus/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: janus/s390x openssl
• jose/amd64 (11-2 to 11-2)
  • Migration status for jose/amd64 (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/amd64 openssl
• jose/arm64 (11-2 to 11-2)
  • Migration status for jose/arm64 (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/arm64 openssl
• jose/armel (11-2 to 11-2)
  • Migration status for jose/armel (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/armel openssl
• jose/armhf (11-2 to 11-2)
  • Migration status for jose/armhf (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/armhf openssl
• jose/i386 (11-2 to 11-2)
  • Migration status for jose/i386 (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/i386 openssl
• jose/mips64el (11-2 to 11-2)
  • Migration status for jose/mips64el (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/mips64el openssl
• jose/mipsel (11-2 to 11-2)
  • Migration status for jose/mipsel (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/mipsel openssl
• jose/ppc64el (11-2 to 11-2)
  • Migration status for jose/ppc64el (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/ppc64el openssl
• jose/s390x (11-2 to 11-2)
  • Migration status for jose/s390x (11-2 to 11-2): Will attempt migration (Any information below is purely informational)
    • Depends: jose/s390x openssl
• js-of-ocaml/amd64 (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/amd64 (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/amd64 menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/amd64 eliom/amd64
    • Implicit dependency: js-of-ocaml/amd64 nurpawiki/amd64
    • Implicit dependency: js-of-ocaml/amd64 ocaml-cohttp/amd64
    • Implicit dependency: js-of-ocaml/amd64 ocaml-logs/amd64
• js-of-ocaml/arm64 (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/arm64 (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/arm64 menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/arm64 eliom/arm64
    • Implicit dependency: js-of-ocaml/arm64 nurpawiki/arm64
    • Implicit dependency: js-of-ocaml/arm64 ocaml-cohttp/arm64
    • Implicit dependency: js-of-ocaml/arm64 ocaml-logs/arm64
• js-of-ocaml/armel (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/armel (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/armel menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/armel eliom/armel
    • Implicit dependency: js-of-ocaml/armel nurpawiki/armel
    • Implicit dependency: js-of-ocaml/armel ocaml-cohttp/armel
    • Implicit dependency: js-of-ocaml/armel ocaml-logs/armel
• js-of-ocaml/armhf (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/armhf (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/armhf menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/armhf eliom/armhf
    • Implicit dependency: js-of-ocaml/armhf nurpawiki/armhf
    • Implicit dependency: js-of-ocaml/armhf ocaml-cohttp/armhf
    • Implicit dependency: js-of-ocaml/armhf ocaml-logs/armhf
• js-of-ocaml/i386 (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/i386 (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/i386 menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/i386 eliom/i386
    • Implicit dependency: js-of-ocaml/i386 nurpawiki/i386
    • Implicit dependency: js-of-ocaml/i386 ocaml-cohttp/i386
    • Implicit dependency: js-of-ocaml/i386 ocaml-logs/i386
• js-of-ocaml/mips64el (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/mips64el (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/mips64el menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/mips64el eliom/mips64el
    • Implicit dependency: js-of-ocaml/mips64el nurpawiki/mips64el
    • Implicit dependency: js-of-ocaml/mips64el ocaml-cohttp/mips64el
    • Implicit dependency: js-of-ocaml/mips64el ocaml-logs/mips64el
• js-of-ocaml/mipsel (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/mipsel (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/mipsel menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/mipsel eliom/mipsel
    • Implicit dependency: js-of-ocaml/mipsel nurpawiki/mipsel
    • Implicit dependency: js-of-ocaml/mipsel ocaml-cohttp/mipsel
    • Implicit dependency: js-of-ocaml/mipsel ocaml-logs/mipsel
• js-of-ocaml/ppc64el (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/ppc64el (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/ppc64el menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/ppc64el eliom/ppc64el
    • Implicit dependency: js-of-ocaml/ppc64el nurpawiki/ppc64el
    • Implicit dependency: js-of-ocaml/ppc64el ocaml-cohttp/ppc64el
    • Implicit dependency: js-of-ocaml/ppc64el ocaml-logs/ppc64el
• js-of-ocaml/s390x (4.0.0-1 to 4.0.0-1)
  • Migration status for js-of-ocaml/s390x (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml/s390x menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml/s390x eliom/s390x
    • Implicit dependency: js-of-ocaml/s390x nurpawiki/s390x
    • Implicit dependency: js-of-ocaml/s390x ocaml-cohttp/s390x
    • Implicit dependency: js-of-ocaml/s390x ocaml-logs/s390x
• kamailio/amd64 (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/amd64 (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/amd64 openssl
• kamailio/arm64 (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/arm64 (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/arm64 openssl
• kamailio/armel (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/armel (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/armel openssl
• kamailio/armhf (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/armhf (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/armhf openssl
• kamailio/i386 (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/i386 (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/i386 openssl
• kamailio/mips64el (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/mips64el (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/mips64el openssl
• kamailio/mipsel (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/mipsel (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/mipsel openssl
• kamailio/ppc64el (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/ppc64el (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/ppc64el openssl
• kamailio/s390x (5.5.4-1 to 5.5.4-1)
  • Migration status for kamailio/s390x (5.5.4-1 to 5.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: kamailio/s390x openssl
• kannel/amd64 (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/amd64 (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/amd64 openssl
• kannel/arm64 (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/arm64 (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/arm64 openssl
• kannel/armel (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/armel (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/armel openssl
• kannel/armhf (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/armhf (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/armhf openssl
• kannel/i386 (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/i386 (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/i386 openssl
• kannel/mips64el (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/mips64el (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/mips64el openssl
• kannel/mipsel (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/mipsel (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/mipsel openssl
• kannel/ppc64el (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/ppc64el (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/ppc64el openssl
• kannel/s390x (1.4.5-10 to 1.4.5-10)
  • Migration status for kannel/s390x (1.4.5-10 to 1.4.5-10): Will attempt migration (Any information below is purely informational)
    • Depends: kannel/s390x openssl
• keepalived/amd64 (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/amd64 (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/amd64 openssl
• keepalived/arm64 (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/arm64 (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/arm64 openssl
• keepalived/armel (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/armel (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/armel openssl
• keepalived/armhf (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/armhf (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/armhf openssl
• keepalived/i386 (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/i386 (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/i386 openssl
• keepalived/mips64el (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/mips64el (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/mips64el openssl
• keepalived/mipsel (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/mipsel (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/mipsel openssl
• keepalived/ppc64el (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/ppc64el (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/ppc64el openssl
• keepalived/s390x (1:2.2.7-1 to 1:2.2.7-1)
  • Migration status for keepalived/s390x (1:2.2.7-1 to 1:2.2.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: keepalived/s390x openssl
• kmod/amd64 (29-1 to 29-1)
  • Migration status for kmod/amd64 (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/amd64 openssl
• kmod/arm64 (29-1 to 29-1)
  • Migration status for kmod/arm64 (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/arm64 openssl
• kmod/armel (29-1 to 29-1)
  • Migration status for kmod/armel (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/armel openssl
• kmod/armhf (29-1 to 29-1)
  • Migration status for kmod/armhf (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/armhf openssl
• kmod/i386 (29-1 to 29-1)
  • Migration status for kmod/i386 (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/i386 openssl
• kmod/mips64el (29-1 to 29-1)
  • Migration status for kmod/mips64el (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/mips64el openssl
• kmod/mipsel (29-1 to 29-1)
  • Migration status for kmod/mipsel (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/mipsel openssl
• kmod/ppc64el (29-1 to 29-1)
  • Migration status for kmod/ppc64el (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/ppc64el openssl
• kmod/s390x (29-1 to 29-1)
  • Migration status for kmod/s390x (29-1 to 29-1): Will attempt migration (Any information below is purely informational)
    • Depends: kmod/s390x openssl
• kore/amd64 (4.1.0-6 to 4.1.0-6)
  • Migration status for kore/amd64 (4.1.0-6 to 4.1.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: kore/amd64 openssl
• kore/arm64 (4.1.0-6 to 4.1.0-6)
  • Migration status for kore/arm64 (4.1.0-6 to 4.1.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: kore/arm64 openssl
• kore/armel (4.1.0-6 to 4.1.0-6)
  • Migration status for kore/armel (4.1.0-6 to 4.1.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: kore/armel openssl
• kore/armhf (4.1.0-6 to 4.1.0-6)
  • Migration status for kore/armhf (4.1.0-6 to 4.1.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: kore/armhf openssl
• krb5/amd64 (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/amd64 (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/amd64 openssl
• krb5/arm64 (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/arm64 (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/arm64 openssl
• krb5/armel (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/armel (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/armel openssl
• krb5/armhf (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/armhf (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/armhf openssl
• krb5/i386 (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/i386 (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/i386 openssl
• krb5/mips64el (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/mips64el (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/mips64el openssl
• krb5/mipsel (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/mipsel (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/mipsel openssl
• krb5/ppc64el (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/ppc64el (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/ppc64el openssl
• krb5/s390x (1.19.2-2 to 1.19.2-2)
  • Migration status for krb5/s390x (1.19.2-2 to 1.19.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krb5/s390x openssl
• kvirc/amd64 (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/amd64 (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/amd64 openssl
• kvirc/arm64 (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/arm64 (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/arm64 openssl
• kvirc/armel (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/armel (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/armel openssl
• kvirc/armhf (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/armhf (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/armhf openssl
• kvirc/i386 (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/i386 (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/i386 openssl
• kvirc/mips64el (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/mips64el (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/mips64el openssl
• kvirc/mipsel (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/mipsel (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/mipsel openssl
• kvirc/ppc64el (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/ppc64el (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/ppc64el openssl
• kvirc/s390x (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6)
  • Migration status for kvirc/s390x (4:5.0.0+dfsg-6 to 4:5.0.0+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: kvirc/s390x openssl
• lasso/amd64 (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/amd64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/amd64 openssl
• lasso/arm64 (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/arm64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/arm64 openssl
• lasso/armel (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/armel (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/armel openssl
• lasso/armhf (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/armhf (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/armhf openssl
• lasso/i386 (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/i386 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/i386 openssl
• lasso/mips64el (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/mips64el (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/mips64el openssl
• lasso/mipsel (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/mipsel (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/mipsel openssl
• lasso/ppc64el (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/ppc64el (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/ppc64el openssl
• lasso/s390x (2.8.0-1 to 2.8.0-1)
  • Migration status for lasso/s390x (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lasso/s390x openssl
• lastpass-cli/amd64 (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/amd64 (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/amd64 openssl
• lastpass-cli/arm64 (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/arm64 (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/arm64 openssl
• lastpass-cli/armel (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/armel (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/armel openssl
• lastpass-cli/armhf (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/armhf (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/armhf openssl
• lastpass-cli/i386 (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/i386 (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/i386 openssl
• lastpass-cli/mips64el (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/mips64el (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/mips64el openssl
• lastpass-cli/mipsel (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/mipsel (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/mipsel openssl
• lastpass-cli/ppc64el (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/ppc64el (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/ppc64el openssl
• lastpass-cli/s390x (1.3.3-4 to 1.3.3-4)
  • Migration status for lastpass-cli/s390x (1.3.3-4 to 1.3.3-4): Will attempt migration (Any information below is purely informational)
    • Depends: lastpass-cli/s390x openssl
• lcas/amd64 (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/amd64 (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/amd64 openssl
• lcas/arm64 (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/arm64 (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/arm64 openssl
• lcas/armel (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/armel (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/armel openssl
• lcas/armhf (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/armhf (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/armhf openssl
• lcas/i386 (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/i386 (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/i386 openssl
• lcas/mips64el (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/mips64el (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/mips64el openssl
• lcas/mipsel (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/mipsel (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/mipsel openssl
• lcas/ppc64el (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/ppc64el (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/ppc64el openssl
• lcas/s390x (1.3.19-2.1 to 1.3.19-2.1)
  • Migration status for lcas/s390x (1.3.19-2.1 to 1.3.19-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcas/s390x openssl
• lcmaps-plugins-jobrep/amd64 (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/amd64 (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/amd64 openssl
• lcmaps-plugins-jobrep/arm64 (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/arm64 (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/arm64 openssl
• lcmaps-plugins-jobrep/armel (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/armel (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/armel openssl
• lcmaps-plugins-jobrep/armhf (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/armhf (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/armhf openssl
• lcmaps-plugins-jobrep/i386 (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/i386 (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/i386 openssl
• lcmaps-plugins-jobrep/mips64el (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/mips64el (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/mips64el openssl
• lcmaps-plugins-jobrep/mipsel (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/mipsel (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/mipsel openssl
• lcmaps-plugins-jobrep/ppc64el (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/ppc64el (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/ppc64el openssl
• lcmaps-plugins-jobrep/s390x (1.5.6-1.1 to 1.5.6-1.1)
  • Migration status for lcmaps-plugins-jobrep/s390x (1.5.6-1.1 to 1.5.6-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-jobrep/s390x openssl
• lcmaps-plugins-verify-proxy/amd64 (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/amd64 (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/amd64 openssl
• lcmaps-plugins-verify-proxy/arm64 (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/arm64 (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/arm64 openssl
• lcmaps-plugins-verify-proxy/armel (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/armel (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/armel openssl
• lcmaps-plugins-verify-proxy/armhf (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/armhf (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/armhf openssl
• lcmaps-plugins-verify-proxy/i386 (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/i386 (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/i386 openssl
• lcmaps-plugins-verify-proxy/mips64el (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/mips64el (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/mips64el openssl
• lcmaps-plugins-verify-proxy/mipsel (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/mipsel (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/mipsel openssl
• lcmaps-plugins-verify-proxy/ppc64el (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/ppc64el (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/ppc64el openssl
• lcmaps-plugins-verify-proxy/s390x (1.5.10-2 to 1.5.10-2)
  • Migration status for lcmaps-plugins-verify-proxy/s390x (1.5.10-2 to 1.5.10-2): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps-plugins-verify-proxy/s390x openssl
• lcmaps/amd64 (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/amd64 (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/amd64 openssl
• lcmaps/arm64 (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/arm64 (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/arm64 openssl
• lcmaps/armel (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/armel (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/armel openssl
• lcmaps/armhf (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/armhf (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/armhf openssl
• lcmaps/i386 (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/i386 (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/i386 openssl
• lcmaps/mips64el (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/mips64el (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/mips64el openssl
• lcmaps/mipsel (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/mipsel (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/mipsel openssl
• lcmaps/ppc64el (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/ppc64el (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/ppc64el openssl
• lcmaps/s390x (1.6.6-2.1 to 1.6.6-2.1)
  • Migration status for lcmaps/s390x (1.6.6-2.1 to 1.6.6-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: lcmaps/s390x openssl
• ldns/amd64 (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/amd64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/amd64 openssl
• ldns/arm64 (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/arm64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/arm64 openssl
• ldns/armel (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/armel (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/armel openssl
• ldns/armhf (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/armhf (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/armhf openssl
• ldns/i386 (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/i386 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/i386 openssl
• ldns/mips64el (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/mips64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/mips64el openssl
• ldns/mipsel (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/mipsel (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/mipsel openssl
• ldns/ppc64el (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/ppc64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/ppc64el openssl
• ldns/s390x (1.8.1-1 to 1.8.1-1)
  • Migration status for ldns/s390x (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ldns/s390x openssl
• libapache2-mod-auth-gssapi/amd64 (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/amd64 (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/amd64 openssl
• libapache2-mod-auth-gssapi/arm64 (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/arm64 (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/arm64 openssl
• libapache2-mod-auth-gssapi/armel (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/armel (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/armel openssl
• libapache2-mod-auth-gssapi/armhf (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/armhf (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/armhf openssl
• libapache2-mod-auth-gssapi/i386 (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/i386 (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/i386 openssl
• libapache2-mod-auth-gssapi/mips64el (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/mips64el (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/mips64el openssl
• libapache2-mod-auth-gssapi/mipsel (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/mipsel (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/mipsel openssl
• libapache2-mod-auth-gssapi/ppc64el (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/ppc64el (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/ppc64el openssl
• libapache2-mod-auth-gssapi/s390x (1.6.3-1 to 1.6.3-1)
  • Migration status for libapache2-mod-auth-gssapi/s390x (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-gssapi/s390x openssl
• libapache2-mod-auth-mellon/amd64 (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/amd64 (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/amd64 openssl
• libapache2-mod-auth-mellon/arm64 (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/arm64 (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/arm64 openssl
• libapache2-mod-auth-mellon/armel (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/armel (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/armel openssl
• libapache2-mod-auth-mellon/armhf (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/armhf (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/armhf openssl
• libapache2-mod-auth-mellon/i386 (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/i386 (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/i386 openssl
• libapache2-mod-auth-mellon/mips64el (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/mips64el (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/mips64el openssl
• libapache2-mod-auth-mellon/mipsel (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/mipsel (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/mipsel openssl
• libapache2-mod-auth-mellon/ppc64el (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/ppc64el (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/ppc64el openssl
• libapache2-mod-auth-mellon/s390x (0.18.0-1 to 0.18.0-1)
  • Migration status for libapache2-mod-auth-mellon/s390x (0.18.0-1 to 0.18.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-mellon/s390x openssl
• libapache2-mod-auth-openidc/amd64 (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/amd64 (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/amd64 openssl
• libapache2-mod-auth-openidc/arm64 (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/arm64 (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/arm64 openssl
• libapache2-mod-auth-openidc/armel (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/armel (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/armel openssl
• libapache2-mod-auth-openidc/armhf (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/armhf (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/armhf openssl
• libapache2-mod-auth-openidc/i386 (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/i386 (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/i386 openssl
• libapache2-mod-auth-openidc/mips64el (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/mips64el (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/mips64el openssl
• libapache2-mod-auth-openidc/mipsel (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/mipsel (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/mipsel openssl
• libapache2-mod-auth-openidc/ppc64el (2.4.11.1-1 to 2.4.11.1-1)
  • Migration status for libapache2-mod-auth-openidc/ppc64el (2.4.11.1-1 to 2.4.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-openidc/ppc64el openssl
• libapache2-mod-auth-openidc_pu (2.4.11.1-1 to 2.4.9.4-0+deb11u1)
  • Migration status for libapache2-mod-auth-openidc_pu (2.4.11.1-1 to 2.4.9.4-0+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libapache2-mod-auth-openidc is newer in the target suite (2.4.11.1-1 2.4.9.4-0+deb11u1)
• libapache2-mod-auth-pubtkt/amd64 (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/amd64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/amd64 openssl
• libapache2-mod-auth-pubtkt/arm64 (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/arm64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/arm64 openssl
• libapache2-mod-auth-pubtkt/armel (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/armel (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/armel openssl
• libapache2-mod-auth-pubtkt/armhf (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/armhf (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/armhf openssl
• libapache2-mod-auth-pubtkt/i386 (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/i386 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/i386 openssl
• libapache2-mod-auth-pubtkt/mips64el (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/mips64el (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/mips64el openssl
• libapache2-mod-auth-pubtkt/mipsel (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/mipsel (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/mipsel openssl
• libapache2-mod-auth-pubtkt/ppc64el (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/ppc64el (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/ppc64el openssl
• libapache2-mod-auth-pubtkt/s390x (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/s390x (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-auth-pubtkt/s390x openssl
• libapache2-mod-qos/amd64 (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/amd64 (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/amd64 openssl
• libapache2-mod-qos/arm64 (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/arm64 (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/arm64 openssl
• libapache2-mod-qos/armel (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/armel (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/armel openssl
• libapache2-mod-qos/armhf (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/armhf (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/armhf openssl
• libapache2-mod-qos/i386 (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/i386 (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/i386 openssl
• libapache2-mod-qos/mips64el (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/mips64el (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/mips64el openssl
• libapache2-mod-qos/mipsel (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/mipsel (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/mipsel openssl
• libapache2-mod-qos/ppc64el (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/ppc64el (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/ppc64el openssl
• libapache2-mod-qos/s390x (11.63-1 to 11.63-1)
  • Migration status for libapache2-mod-qos/s390x (11.63-1 to 11.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: libapache2-mod-qos/s390x openssl
• libcoap2/amd64 (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/amd64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/amd64 openssl
• libcoap2/arm64 (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/arm64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/arm64 openssl
• libcoap2/armel (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/armel (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/armel openssl
• libcoap2/armhf (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/armhf (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/armhf openssl
• libcoap2/i386 (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/i386 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/i386 openssl
• libcoap2/mips64el (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/mips64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/mips64el openssl
• libcoap2/mipsel (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/mipsel (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/mipsel openssl
• libcoap2/ppc64el (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/ppc64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/ppc64el openssl
• libcoap2/s390x (4.2.1-1 to 4.2.1-1)
  • Migration status for libcoap2/s390x (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap2/s390x openssl
• libcoap3/amd64 (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/amd64 (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/amd64 openssl
• libcoap3/arm64 (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/arm64 (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/arm64 openssl
• libcoap3/armel (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/armel (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/armel openssl
• libcoap3/armhf (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/armhf (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/armhf openssl
• libcoap3/i386 (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/i386 (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/i386 openssl
• libcoap3/mips64el (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/mips64el (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/mips64el openssl
• libcoap3/mipsel (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/mipsel (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/mipsel openssl
• libcoap3/ppc64el (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/ppc64el (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/ppc64el openssl
• libcoap3/s390x (4.3.0-2 to 4.3.0-2)
  • Migration status for libcoap3/s390x (4.3.0-2 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcoap3/s390x openssl
• libcrypt-openssl-bignum-perl/amd64 (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/amd64 (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/amd64 openssl
    • Depends: libcrypt-openssl-bignum-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-openssl-bignum-perl/arm64 (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/arm64 (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/arm64 openssl
    • Depends: libcrypt-openssl-bignum-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-openssl-bignum-perl/armel (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/armel (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/armel openssl
    • Depends: libcrypt-openssl-bignum-perl/armel perl-openssl-defaults/armel
• libcrypt-openssl-bignum-perl/armhf (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/armhf (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/armhf openssl
    • Depends: libcrypt-openssl-bignum-perl/armhf perl-openssl-defaults/armhf
• libcrypt-openssl-bignum-perl/i386 (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/i386 (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/i386 openssl
    • Depends: libcrypt-openssl-bignum-perl/i386 perl-openssl-defaults/i386
• libcrypt-openssl-bignum-perl/mips64el (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/mips64el (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/mips64el openssl
    • Depends: libcrypt-openssl-bignum-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-openssl-bignum-perl/mipsel (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/mipsel (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/mipsel openssl
    • Depends: libcrypt-openssl-bignum-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-openssl-bignum-perl/ppc64el (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/ppc64el (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/ppc64el openssl
    • Depends: libcrypt-openssl-bignum-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-openssl-bignum-perl/s390x (0.09-1 to 0.09-1)
  • Migration status for libcrypt-openssl-bignum-perl/s390x (0.09-1 to 0.09-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-bignum-perl/s390x openssl
    • Depends: libcrypt-openssl-bignum-perl/s390x perl-openssl-defaults/s390x
• libcrypt-openssl-dsa-perl/amd64 (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/amd64 (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/amd64 openssl
    • Depends: libcrypt-openssl-dsa-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-openssl-dsa-perl/arm64 (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/arm64 (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/arm64 openssl
    • Depends: libcrypt-openssl-dsa-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-openssl-dsa-perl/armel (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/armel (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/armel openssl
    • Depends: libcrypt-openssl-dsa-perl/armel perl-openssl-defaults/armel
• libcrypt-openssl-dsa-perl/armhf (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/armhf (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/armhf openssl
    • Depends: libcrypt-openssl-dsa-perl/armhf perl-openssl-defaults/armhf
• libcrypt-openssl-dsa-perl/i386 (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/i386 (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/i386 openssl
    • Depends: libcrypt-openssl-dsa-perl/i386 perl-openssl-defaults/i386
• libcrypt-openssl-dsa-perl/mips64el (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/mips64el (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/mips64el openssl
    • Depends: libcrypt-openssl-dsa-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-openssl-dsa-perl/mipsel (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/mipsel (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/mipsel openssl
    • Depends: libcrypt-openssl-dsa-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-openssl-dsa-perl/ppc64el (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/ppc64el (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/ppc64el openssl
    • Depends: libcrypt-openssl-dsa-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-openssl-dsa-perl/s390x (0.20-1 to 0.20-1)
  • Migration status for libcrypt-openssl-dsa-perl/s390x (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-dsa-perl/s390x openssl
    • Depends: libcrypt-openssl-dsa-perl/s390x perl-openssl-defaults/s390x
• libcrypt-openssl-ec-perl/amd64 (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/amd64 (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/amd64 openssl
• libcrypt-openssl-ec-perl/arm64 (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/arm64 (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/arm64 openssl
• libcrypt-openssl-ec-perl/armel (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/armel (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/armel openssl
• libcrypt-openssl-ec-perl/armhf (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/armhf (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/armhf openssl
• libcrypt-openssl-ec-perl/i386 (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/i386 (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/i386 openssl
• libcrypt-openssl-ec-perl/mips64el (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/mips64el (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/mips64el openssl
• libcrypt-openssl-ec-perl/mipsel (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/mipsel (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/mipsel openssl
• libcrypt-openssl-ec-perl/ppc64el (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/ppc64el (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/ppc64el openssl
• libcrypt-openssl-ec-perl/s390x (1.32-1 to 1.32-1)
  • Migration status for libcrypt-openssl-ec-perl/s390x (1.32-1 to 1.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-ec-perl/s390x openssl
• libcrypt-openssl-pkcs10-perl/amd64 (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/amd64 (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/amd64 openssl
    • Depends: libcrypt-openssl-pkcs10-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-openssl-pkcs10-perl/arm64 (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/arm64 (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/arm64 openssl
    • Depends: libcrypt-openssl-pkcs10-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-openssl-pkcs10-perl/armel (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/armel (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/armel openssl
    • Depends: libcrypt-openssl-pkcs10-perl/armel perl-openssl-defaults/armel
• libcrypt-openssl-pkcs10-perl/armhf (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/armhf (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/armhf openssl
    • Depends: libcrypt-openssl-pkcs10-perl/armhf perl-openssl-defaults/armhf
• libcrypt-openssl-pkcs10-perl/i386 (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/i386 (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/i386 openssl
    • Depends: libcrypt-openssl-pkcs10-perl/i386 perl-openssl-defaults/i386
• libcrypt-openssl-pkcs10-perl/mips64el (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/mips64el (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/mips64el openssl
    • Depends: libcrypt-openssl-pkcs10-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-openssl-pkcs10-perl/mipsel (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/mipsel (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/mipsel openssl
    • Depends: libcrypt-openssl-pkcs10-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-openssl-pkcs10-perl/ppc64el (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/ppc64el (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/ppc64el openssl
    • Depends: libcrypt-openssl-pkcs10-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-openssl-pkcs10-perl/s390x (0.19-1 to 0.19-1)
  • Migration status for libcrypt-openssl-pkcs10-perl/s390x (0.19-1 to 0.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-pkcs10-perl/s390x openssl
    • Depends: libcrypt-openssl-pkcs10-perl/s390x perl-openssl-defaults/s390x
• libcrypt-openssl-random-perl/amd64 (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/amd64 (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/amd64 openssl
• libcrypt-openssl-random-perl/arm64 (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/arm64 (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/arm64 openssl
• libcrypt-openssl-random-perl/armel (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/armel (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/armel openssl
• libcrypt-openssl-random-perl/armhf (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/armhf (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/armhf openssl
• libcrypt-openssl-random-perl/i386 (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/i386 (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/i386 openssl
• libcrypt-openssl-random-perl/mips64el (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/mips64el (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/mips64el openssl
• libcrypt-openssl-random-perl/mipsel (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/mipsel (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/mipsel openssl
• libcrypt-openssl-random-perl/ppc64el (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/ppc64el (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/ppc64el openssl
• libcrypt-openssl-random-perl/s390x (0.15-2 to 0.15-2)
  • Migration status for libcrypt-openssl-random-perl/s390x (0.15-2 to 0.15-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-random-perl/s390x openssl
• libcrypt-openssl-rsa-perl/amd64 (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/amd64 (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/amd64 openssl
    • Depends: libcrypt-openssl-rsa-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-openssl-rsa-perl/arm64 (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/arm64 (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/arm64 openssl
    • Depends: libcrypt-openssl-rsa-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-openssl-rsa-perl/armel (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/armel (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/armel openssl
    • Depends: libcrypt-openssl-rsa-perl/armel perl-openssl-defaults/armel
• libcrypt-openssl-rsa-perl/armhf (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/armhf (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/armhf openssl
    • Depends: libcrypt-openssl-rsa-perl/armhf perl-openssl-defaults/armhf
• libcrypt-openssl-rsa-perl/i386 (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/i386 (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/i386 openssl
    • Depends: libcrypt-openssl-rsa-perl/i386 perl-openssl-defaults/i386
• libcrypt-openssl-rsa-perl/mips64el (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/mips64el (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/mips64el openssl
    • Depends: libcrypt-openssl-rsa-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-openssl-rsa-perl/mipsel (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/mipsel (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/mipsel openssl
    • Depends: libcrypt-openssl-rsa-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-openssl-rsa-perl/ppc64el (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/ppc64el (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/ppc64el openssl
    • Depends: libcrypt-openssl-rsa-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-openssl-rsa-perl/s390x (0.32-2 to 0.32-2)
  • Migration status for libcrypt-openssl-rsa-perl/s390x (0.32-2 to 0.32-2): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-rsa-perl/s390x openssl
    • Depends: libcrypt-openssl-rsa-perl/s390x perl-openssl-defaults/s390x
• libcrypt-openssl-x509-perl/amd64 (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/amd64 (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/amd64 openssl
    • Depends: libcrypt-openssl-x509-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-openssl-x509-perl/arm64 (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/arm64 (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/arm64 openssl
    • Depends: libcrypt-openssl-x509-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-openssl-x509-perl/armel (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/armel (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/armel openssl
    • Depends: libcrypt-openssl-x509-perl/armel perl-openssl-defaults/armel
• libcrypt-openssl-x509-perl/armhf (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/armhf (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/armhf openssl
    • Depends: libcrypt-openssl-x509-perl/armhf perl-openssl-defaults/armhf
• libcrypt-openssl-x509-perl/i386 (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/i386 (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/i386 openssl
    • Depends: libcrypt-openssl-x509-perl/i386 perl-openssl-defaults/i386
• libcrypt-openssl-x509-perl/mips64el (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/mips64el (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/mips64el openssl
    • Depends: libcrypt-openssl-x509-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-openssl-x509-perl/mipsel (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/mipsel (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/mipsel openssl
    • Depends: libcrypt-openssl-x509-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-openssl-x509-perl/ppc64el (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/ppc64el (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/ppc64el openssl
    • Depends: libcrypt-openssl-x509-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-openssl-x509-perl/s390x (1.9.14-1 to 1.9.14-1)
  • Migration status for libcrypt-openssl-x509-perl/s390x (1.9.14-1 to 1.9.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-openssl-x509-perl/s390x openssl
    • Depends: libcrypt-openssl-x509-perl/s390x perl-openssl-defaults/s390x
• libcrypt-smime-perl/amd64 (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/amd64 (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/amd64 openssl
    • Depends: libcrypt-smime-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-smime-perl/arm64 (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/arm64 (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/arm64 openssl
    • Depends: libcrypt-smime-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-smime-perl/armel (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/armel (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/armel openssl
    • Depends: libcrypt-smime-perl/armel perl-openssl-defaults/armel
• libcrypt-smime-perl/armhf (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/armhf (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/armhf openssl
    • Depends: libcrypt-smime-perl/armhf perl-openssl-defaults/armhf
• libcrypt-smime-perl/i386 (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/i386 (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/i386 openssl
    • Depends: libcrypt-smime-perl/i386 perl-openssl-defaults/i386
• libcrypt-smime-perl/mips64el (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/mips64el (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/mips64el openssl
    • Depends: libcrypt-smime-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-smime-perl/mipsel (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/mipsel (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/mipsel openssl
    • Depends: libcrypt-smime-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-smime-perl/ppc64el (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/ppc64el (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/ppc64el openssl
    • Depends: libcrypt-smime-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-smime-perl/s390x (0.28-1 to 0.28-1)
  • Migration status for libcrypt-smime-perl/s390x (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-smime-perl/s390x openssl
    • Depends: libcrypt-smime-perl/s390x perl-openssl-defaults/s390x
• libcrypt-ssleay-perl/amd64 (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/amd64 (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/amd64 openssl
    • Depends: libcrypt-ssleay-perl/amd64 perl-openssl-defaults/amd64
• libcrypt-ssleay-perl/arm64 (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/arm64 (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/arm64 openssl
    • Depends: libcrypt-ssleay-perl/arm64 perl-openssl-defaults/arm64
• libcrypt-ssleay-perl/armel (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/armel (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/armel openssl
    • Depends: libcrypt-ssleay-perl/armel perl-openssl-defaults/armel
• libcrypt-ssleay-perl/armhf (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/armhf (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/armhf openssl
    • Depends: libcrypt-ssleay-perl/armhf perl-openssl-defaults/armhf
• libcrypt-ssleay-perl/i386 (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/i386 (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/i386 openssl
    • Depends: libcrypt-ssleay-perl/i386 perl-openssl-defaults/i386
• libcrypt-ssleay-perl/mips64el (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/mips64el (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/mips64el openssl
    • Depends: libcrypt-ssleay-perl/mips64el perl-openssl-defaults/mips64el
• libcrypt-ssleay-perl/mipsel (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/mipsel (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/mipsel openssl
    • Depends: libcrypt-ssleay-perl/mipsel perl-openssl-defaults/mipsel
• libcrypt-ssleay-perl/ppc64el (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/ppc64el (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/ppc64el openssl
    • Depends: libcrypt-ssleay-perl/ppc64el perl-openssl-defaults/ppc64el
• libcrypt-ssleay-perl/s390x (0.73.06-1 to 0.73.06-1)
  • Migration status for libcrypt-ssleay-perl/s390x (0.73.06-1 to 0.73.06-1): Will attempt migration (Any information below is purely informational)
    • Depends: libcrypt-ssleay-perl/s390x openssl
    • Depends: libcrypt-ssleay-perl/s390x perl-openssl-defaults/s390x
• libdkim/amd64 (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/amd64 (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/amd64 openssl
• libdkim/arm64 (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/arm64 (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/arm64 openssl
• libdkim/armel (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/armel (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/armel openssl
• libdkim/armhf (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/armhf (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/armhf openssl
• libdkim/i386 (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/i386 (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/i386 openssl
• libdkim/mips64el (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/mips64el (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/mips64el openssl
• libdkim/mipsel (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/mipsel (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/mipsel openssl
• libdkim/ppc64el (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/ppc64el (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/ppc64el openssl
• libdkim/s390x (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/s390x (1:1.0.21-4 to 1:1.0.21-4): Will attempt migration (Any information below is purely informational)
    • Depends: libdkim/s390x openssl
• libdnf/amd64 (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/amd64 (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/amd64 openssl
• libdnf/arm64 (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/arm64 (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/arm64 openssl
• libdnf/armhf (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/armhf (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/armhf openssl
• libdnf/i386 (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/i386 (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/i386 openssl
• libdnf/mips64el (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/mips64el (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/mips64el openssl
• libdnf/mipsel (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/mipsel (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/mipsel openssl
• libdnf/ppc64el (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/ppc64el (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/ppc64el openssl
• libdnf/s390x (0.55.2-6 to 0.55.2-6)
  • Migration status for libdnf/s390x (0.55.2-6 to 0.55.2-6): Will attempt migration (Any information below is purely informational)
    • Depends: libdnf/s390x openssl
• libdrpm/amd64 (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/amd64 (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/amd64 openssl
• libdrpm/arm64 (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/arm64 (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/arm64 openssl
• libdrpm/armel (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/armel (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/armel openssl
• libdrpm/armhf (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/armhf (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/armhf openssl
• libdrpm/i386 (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/i386 (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/i386 openssl
• libdrpm/mips64el (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/mips64el (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/mips64el openssl
• libdrpm/mipsel (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/mipsel (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/mipsel openssl
• libdrpm/ppc64el (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/ppc64el (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/ppc64el openssl
• libdrpm/s390x (0.5.0-3 to 0.5.0-3)
  • Migration status for libdrpm/s390x (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libdrpm/s390x openssl
• libesmtp/amd64 (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/amd64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/amd64 openssl
• libesmtp/arm64 (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/arm64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/arm64 openssl
• libesmtp/armel (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/armel (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/armel openssl
• libesmtp/armhf (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/armhf (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/armhf openssl
• libesmtp/i386 (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/i386 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/i386 openssl
• libesmtp/mips64el (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/mips64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/mips64el openssl
• libesmtp/mipsel (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/mipsel (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/mipsel openssl
• libesmtp/ppc64el (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/ppc64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/ppc64el openssl
• libesmtp/s390x (1.1.0-3 to 1.1.0-3)
  • Migration status for libesmtp/s390x (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libesmtp/s390x openssl
• libevent/amd64 (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/amd64 (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/amd64 openssl
• libevent/arm64 (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/arm64 (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/arm64 openssl
• libevent/armel (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/armel (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/armel openssl
• libevent/armhf (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/armhf (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/armhf openssl
• libevent/i386 (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/i386 (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/i386 openssl
• libevent/mips64el (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/mips64el (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/mips64el openssl
• libevent/mipsel (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/mipsel (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/mipsel openssl
• libevent/ppc64el (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/ppc64el (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/ppc64el openssl
• libevent/s390x (2.1.12-stable-5 to 2.1.12-stable-5)
  • Migration status for libevent/s390x (2.1.12-stable-5 to 2.1.12-stable-5): Will attempt migration (Any information below is purely informational)
    • Depends: libevent/s390x openssl
• libevhtp/amd64 (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/amd64 (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/amd64 openssl
• libevhtp/arm64 (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/arm64 (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/arm64 openssl
• libevhtp/armel (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/armel (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/armel openssl
• libevhtp/armhf (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/armhf (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/armhf openssl
• libevhtp/i386 (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/i386 (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/i386 openssl
• libevhtp/mips64el (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/mips64el (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/mips64el openssl
• libevhtp/mipsel (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/mipsel (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/mipsel openssl
• libevhtp/ppc64el (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/ppc64el (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/ppc64el openssl
• libevhtp/s390x (1.2.18-1 to 1.2.18-1)
  • Migration status for libevhtp/s390x (1.2.18-1 to 1.2.18-1): Will attempt migration (Any information below is purely informational)
    • Depends: libevhtp/s390x openssl
• libfreefare/amd64 (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/amd64 (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/amd64 openssl
• libfreefare/arm64 (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/arm64 (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/arm64 openssl
• libfreefare/armel (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/armel (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/armel openssl
• libfreefare/armhf (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/armhf (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/armhf openssl
• libfreefare/i386 (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/i386 (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/i386 openssl
• libfreefare/mips64el (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/mips64el (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/mips64el openssl
• libfreefare/mipsel (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/mipsel (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/mipsel openssl
• libfreefare/ppc64el (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/ppc64el (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/ppc64el openssl
• libfreefare/s390x (0.4.0-2.1 to 0.4.0-2.1)
  • Migration status for libfreefare/s390x (0.4.0-2.1 to 0.4.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libfreefare/s390x openssl
• libfsapfs/amd64 (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/amd64 (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/amd64 openssl
• libfsapfs/arm64 (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/arm64 (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/arm64 openssl
• libfsapfs/armel (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/armel (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/armel openssl
• libfsapfs/armhf (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/armhf (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/armhf openssl
• libfsapfs/i386 (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/i386 (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/i386 openssl
• libfsapfs/mips64el (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/mips64el (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/mips64el openssl
• libfsapfs/mipsel (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/mipsel (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/mipsel openssl
• libfsapfs/ppc64el (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/ppc64el (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/ppc64el openssl
• libfsapfs/s390x (20201107-1 to 20201107-1)
  • Migration status for libfsapfs/s390x (20201107-1 to 20201107-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfsapfs/s390x openssl
• libgwenhywfar/amd64 (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/amd64 (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/amd64 openssl
• libgwenhywfar/arm64 (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/arm64 (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/arm64 openssl
• libgwenhywfar/armel (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/armel (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/armel openssl
• libgwenhywfar/armhf (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/armhf (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/armhf openssl
• libgwenhywfar/i386 (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/i386 (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/i386 openssl
• libgwenhywfar/mips64el (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/mips64el (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/mips64el openssl
• libgwenhywfar/mipsel (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/mipsel (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/mipsel openssl
• libgwenhywfar/ppc64el (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/ppc64el (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/ppc64el openssl
• libgwenhywfar/s390x (5.9.0-1 to 5.9.0-1)
  • Migration status for libgwenhywfar/s390x (5.9.0-1 to 5.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libgwenhywfar/s390x openssl
• libimobiledevice/amd64 (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/amd64 (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/amd64 openssl
• libimobiledevice/arm64 (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/arm64 (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/arm64 openssl
• libimobiledevice/armel (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/armel (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/armel openssl
• libimobiledevice/armhf (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/armhf (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/armhf openssl
• libimobiledevice/i386 (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/i386 (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/i386 openssl
• libimobiledevice/mips64el (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/mips64el (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/mips64el openssl
• libimobiledevice/mipsel (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/mipsel (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/mipsel openssl
• libimobiledevice/ppc64el (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/ppc64el (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/ppc64el openssl
• libimobiledevice/s390x (1.3.0-6 to 1.3.0-6)
  • Migration status for libimobiledevice/s390x (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: libimobiledevice/s390x openssl
• libjwt/amd64 (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/amd64 (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/amd64 openssl
• libjwt/arm64 (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/arm64 (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/arm64 openssl
• libjwt/armel (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/armel (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/armel openssl
• libjwt/armhf (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/armhf (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/armhf openssl
• libjwt/i386 (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/i386 (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/i386 openssl
• libjwt/mips64el (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/mips64el (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/mips64el openssl
• libjwt/mipsel (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/mipsel (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/mipsel openssl
• libjwt/ppc64el (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/ppc64el (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/ppc64el openssl
• libjwt/s390x (1.10.2-1 to 1.10.2-1)
  • Migration status for libjwt/s390x (1.10.2-1 to 1.10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: libjwt/s390x openssl
• libmongocrypt/amd64 (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/amd64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/amd64 openssl
• libmongocrypt/arm64 (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/arm64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/arm64 openssl
• libmongocrypt/armel (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/armel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/armel openssl
• libmongocrypt/armhf (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/armhf (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/armhf openssl
• libmongocrypt/i386 (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/i386 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/i386 openssl
• libmongocrypt/mips64el (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/mips64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/mips64el openssl
• libmongocrypt/mipsel (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/mipsel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/mipsel openssl
• libmongocrypt/ppc64el (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/ppc64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/ppc64el openssl
• libmongocrypt/s390x (1.4.0-1 to 1.4.0-1)
  • Migration status for libmongocrypt/s390x (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libmongocrypt/s390x openssl
• libnet-dns-sec-perl/amd64 (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/amd64 (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/amd64 openssl
• libnet-dns-sec-perl/arm64 (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/arm64 (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/arm64 openssl
• libnet-dns-sec-perl/armel (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/armel (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/armel openssl
• libnet-dns-sec-perl/armhf (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/armhf (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/armhf openssl
• libnet-dns-sec-perl/i386 (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/i386 (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/i386 openssl
• libnet-dns-sec-perl/mips64el (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/mips64el (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/mips64el openssl
• libnet-dns-sec-perl/mipsel (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/mipsel (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/mipsel openssl
• libnet-dns-sec-perl/ppc64el (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/ppc64el (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/ppc64el openssl
• libnet-dns-sec-perl/s390x (1.19-1 to 1.19-1)
  • Migration status for libnet-dns-sec-perl/s390x (1.19-1 to 1.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-dns-sec-perl/s390x openssl
• libnet-tclink-perl/amd64 (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/amd64 (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/amd64 openssl
• libnet-tclink-perl/arm64 (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/arm64 (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/arm64 openssl
• libnet-tclink-perl/armel (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/armel (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/armel openssl
• libnet-tclink-perl/armhf (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/armhf (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/armhf openssl
• libnet-tclink-perl/i386 (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/i386 (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/i386 openssl
• libnet-tclink-perl/mips64el (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/mips64el (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/mips64el openssl
• libnet-tclink-perl/mipsel (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/mipsel (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/mipsel openssl
• libnet-tclink-perl/ppc64el (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/ppc64el (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/ppc64el openssl
• libnet-tclink-perl/s390x (3.4.0-9 to 3.4.0-9)
  • Migration status for libnet-tclink-perl/s390x (3.4.0-9 to 3.4.0-9): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-tclink-perl/s390x openssl
• libnetconf2/amd64 (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/amd64 (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/amd64 openssl
• libnetconf2/arm64 (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/arm64 (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/arm64 openssl
• libnetconf2/armel (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/armel (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/armel openssl
• libnetconf2/armhf (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/armhf (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/armhf openssl
• libnetconf2/i386 (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/i386 (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/i386 openssl
• libnetconf2/mips64el (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/mips64el (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/mips64el openssl
• libnetconf2/mipsel (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/mipsel (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/mipsel openssl
• libnetconf2/ppc64el (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/ppc64el (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/ppc64el openssl
• libnetconf2/s390x (2.0.24-3 to 2.0.24-3)
  • Migration status for libnetconf2/s390x (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
    • Depends: libnetconf2/s390x openssl
• liboauth2/amd64 (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/amd64 (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/amd64 openssl
• liboauth2/arm64 (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/arm64 (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/arm64 openssl
• liboauth2/armel (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/armel (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/armel openssl
• liboauth2/armhf (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/armhf (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/armhf openssl
• liboauth2/i386 (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/i386 (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/i386 openssl
• liboauth2/mips64el (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/mips64el (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/mips64el openssl
• liboauth2/mipsel (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/mipsel (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/mipsel openssl
• liboauth2/ppc64el (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/ppc64el (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/ppc64el openssl
• liboauth2/s390x (1.4.4.2-2 to 1.4.4.2-2)
  • Migration status for liboauth2/s390x (1.4.4.2-2 to 1.4.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: liboauth2/s390x openssl
• libp11/amd64 (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/amd64 (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/amd64 openssl
• libp11/arm64 (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/arm64 (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/arm64 openssl
• libp11/armel (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/armel (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/armel openssl
• libp11/armhf (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/armhf (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/armhf openssl
• libp11/i386 (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/i386 (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/i386 openssl
• libp11/mips64el (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/mips64el (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/mips64el openssl
• libp11/mipsel (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/mipsel (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/mipsel openssl
• libp11/ppc64el (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/ppc64el (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/ppc64el openssl
• libp11/s390x (0.4.11-1 to 0.4.11-1)
  • Migration status for libp11/s390x (0.4.11-1 to 0.4.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: libp11/s390x openssl
• libpam-mount/amd64 (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/amd64 (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/amd64 openssl
• libpam-mount/arm64 (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/arm64 (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/arm64 openssl
• libpam-mount/armel (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/armel (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/armel openssl
• libpam-mount/armhf (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/armhf (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/armhf openssl
• libpam-mount/i386 (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/i386 (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/i386 openssl
• libpam-mount/mips64el (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/mips64el (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/mips64el openssl
• libpam-mount/mipsel (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/mipsel (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/mipsel openssl
• libpam-mount/ppc64el (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/ppc64el (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/ppc64el openssl
• libpam-mount/s390x (2.18-2 to 2.18-2)
  • Migration status for libpam-mount/s390x (2.18-2 to 2.18-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpam-mount/s390x openssl
• libpodofo/amd64 (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/amd64 (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/amd64 openssl
• libpodofo/arm64 (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/arm64 (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/arm64 openssl
• libpodofo/armel (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/armel (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/armel openssl
• libpodofo/armhf (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/armhf (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/armhf openssl
• libpodofo/i386 (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/i386 (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/i386 openssl
• libpodofo/mips64el (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/mips64el (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/mips64el openssl
• libpodofo/mipsel (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/mipsel (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/mipsel openssl
• libpodofo/ppc64el (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/ppc64el (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/ppc64el openssl
• libpodofo/s390x (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
  • Migration status for libpodofo/s390x (0.9.8+dfsg-2 to 0.9.8+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: libpodofo/s390x openssl
• libpoe-filter-ssl-perl/amd64 (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/amd64 (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/amd64 openssl
• libpoe-filter-ssl-perl/arm64 (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/arm64 (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/arm64 openssl
• libpoe-filter-ssl-perl/armel (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/armel (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/armel openssl
• libpoe-filter-ssl-perl/armhf (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/armhf (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/armhf openssl
• libpoe-filter-ssl-perl/i386 (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/i386 (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/i386 openssl
• libpoe-filter-ssl-perl/mips64el (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/mips64el (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/mips64el openssl
• libpoe-filter-ssl-perl/mipsel (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/mipsel (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/mipsel openssl
• libpoe-filter-ssl-perl/ppc64el (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/ppc64el (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/ppc64el openssl
• libpoe-filter-ssl-perl/s390x (0.41-1 to 0.41-1)
  • Migration status for libpoe-filter-ssl-perl/s390x (0.41-1 to 0.41-1): Will attempt migration (Any information below is purely informational)
    • Depends: libpoe-filter-ssl-perl/s390x openssl
• librabbitmq/amd64 (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/amd64 (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/amd64 openssl
• librabbitmq/arm64 (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/arm64 (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/arm64 openssl
• librabbitmq/armel (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/armel (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/armel openssl
• librabbitmq/armhf (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/armhf (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/armhf openssl
• librabbitmq/i386 (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/i386 (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/i386 openssl
• librabbitmq/mips64el (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/mips64el (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/mips64el openssl
• librabbitmq/mipsel (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/mipsel (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/mipsel openssl
• librabbitmq/ppc64el (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/ppc64el (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/ppc64el openssl
• librabbitmq/s390x (0.11.0-1 to 0.11.0-1)
  • Migration status for librabbitmq/s390x (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librabbitmq/s390x openssl
• libradsec/amd64 (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/amd64 (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/amd64 openssl
• libradsec/arm64 (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/arm64 (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/arm64 openssl
• libradsec/armel (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/armel (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/armel openssl
• libradsec/armhf (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/armhf (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/armhf openssl
• libradsec/i386 (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/i386 (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/i386 openssl
• libradsec/mips64el (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/mips64el (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/mips64el openssl
• libradsec/mipsel (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/mipsel (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/mipsel openssl
• libradsec/ppc64el (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/ppc64el (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/ppc64el openssl
• libradsec/s390x (0.0.5-5 to 0.0.5-5)
  • Migration status for libradsec/s390x (0.0.5-5 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
    • Depends: libradsec/s390x openssl
• librdkafka/amd64 (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/amd64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/amd64 openssl
• librdkafka/arm64 (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/arm64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/arm64 openssl
• librdkafka/armel (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/armel (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/armel openssl
• librdkafka/armhf (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/armhf (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/armhf openssl
• librdkafka/i386 (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/i386 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/i386 openssl
• librdkafka/mips64el (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/mips64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/mips64el openssl
• librdkafka/mipsel (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/mipsel (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/mipsel openssl
• librdkafka/ppc64el (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/ppc64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/ppc64el openssl
• librdkafka/s390x (1.8.0-1 to 1.8.0-1)
  • Migration status for librdkafka/s390x (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librdkafka/s390x openssl
• libre/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/amd64 openssl
• libre/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/arm64 openssl
• libre/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/armel openssl
• libre/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/armhf openssl
• libre/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/i386 openssl
• libre/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/mips64el openssl
• libre/mipsel (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/mipsel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/mipsel openssl
• libre/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/ppc64el openssl
• libre/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for libre/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libre/s390x openssl
• librelp/amd64 (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/amd64 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/amd64 openssl
• librelp/arm64 (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/arm64 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/arm64 openssl
• librelp/armel (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/armel (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/armel openssl
• librelp/armhf (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/armhf (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/armhf openssl
• librelp/i386 (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/i386 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/i386 openssl
• librelp/mips64el (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/mips64el (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/mips64el openssl
• librelp/mipsel (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/mipsel (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/mipsel openssl
• librelp/ppc64el (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/ppc64el (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/ppc64el openssl
• librelp/s390x (1.10.0-1 to 1.10.0-1)
  • Migration status for librelp/s390x (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: librelp/s390x openssl
• librepo/amd64 (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/amd64 (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/amd64 openssl
• librepo/arm64 (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/arm64 (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/arm64 openssl
• librepo/armel (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/armel (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/armel openssl
• librepo/armhf (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/armhf (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/armhf openssl
• librepo/i386 (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/i386 (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/i386 openssl
• librepo/mips64el (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/mips64el (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/mips64el openssl
• librepo/mipsel (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/mipsel (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/mipsel openssl
• librepo/ppc64el (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/ppc64el (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/ppc64el openssl
• librepo/s390x (1.12.1-4 to 1.12.1-4)
  • Migration status for librepo/s390x (1.12.1-4 to 1.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: librepo/s390x openssl
• libshairport/amd64 (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/amd64 (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/amd64 openssl
• libshairport/arm64 (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/arm64 (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/arm64 openssl
• libshairport/armel (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/armel (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/armel openssl
• libshairport/armhf (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/armhf (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/armhf openssl
• libshairport/i386 (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/i386 (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/i386 openssl
• libshairport/mips64el (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/mips64el (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/mips64el openssl
• libshairport/mipsel (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/mipsel (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/mipsel openssl
• libshairport/ppc64el (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/ppc64el (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/ppc64el openssl
• libshairport/s390x (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3)
  • Migration status for libshairport/s390x (1.2.1~git20120510.cbed0c1-3 to 1.2.1~git20120510.cbed0c1-3): Will attempt migration (Any information below is purely informational)
    • Depends: libshairport/s390x openssl
• libshout/amd64 (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/amd64 (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/amd64 openssl
• libshout/arm64 (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/arm64 (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/arm64 openssl
• libshout/armel (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/armel (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/armel openssl
• libshout/armhf (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/armhf (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/armhf openssl
• libshout/i386 (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/i386 (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/i386 openssl
• libshout/mips64el (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/mips64el (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/mips64el openssl
• libshout/mipsel (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/mipsel (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/mipsel openssl
• libshout/ppc64el (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/ppc64el (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/ppc64el openssl
• libshout/s390x (2.4.6-1 to 2.4.6-1)
  • Migration status for libshout/s390x (2.4.6-1 to 2.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: libshout/s390x openssl
• libssh/amd64 (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/amd64 (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/amd64 openssl
• libssh/arm64 (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/arm64 (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/arm64 openssl
• libssh/armel (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/armel (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/armel openssl
• libssh/armhf (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/armhf (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/armhf openssl
• libssh/i386 (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/i386 (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/i386 openssl
• libssh/mips64el (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/mips64el (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/mips64el openssl
• libssh/mipsel (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/mipsel (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/mipsel openssl
• libssh/ppc64el (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/ppc64el (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/ppc64el openssl
• libssh/s390x (0.9.6-2 to 0.9.6-2)
  • Migration status for libssh/s390x (0.9.6-2 to 0.9.6-2): Will attempt migration (Any information below is purely informational)
    • Depends: libssh/s390x openssl
• libssh2/amd64 (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/amd64 (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/amd64 openssl
• libssh2/arm64 (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/arm64 (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/arm64 openssl
• libssh2/armel (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/armel (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/armel openssl
• libssh2/armhf (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/armhf (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/armhf openssl
• libssh2/i386 (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/i386 (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/i386 openssl
• libssh2/mips64el (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/mips64el (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/mips64el openssl
• libssh2/mipsel (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/mipsel (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/mipsel openssl
• libssh2/ppc64el (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/ppc64el (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/ppc64el openssl
• libssh2/s390x (1.10.0-3 to 1.10.0-3)
  • Migration status for libssh2/s390x (1.10.0-3 to 1.10.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: libssh2/s390x openssl
• libsylph/amd64 (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/amd64 (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/amd64 openssl
• libsylph/arm64 (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/arm64 (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/arm64 openssl
• libsylph/armel (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/armel (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/armel openssl
• libsylph/armhf (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/armhf (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/armhf openssl
• libsylph/i386 (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/i386 (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/i386 openssl
• libsylph/mips64el (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/mips64el (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/mips64el openssl
• libsylph/mipsel (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/mipsel (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/mipsel openssl
• libsylph/ppc64el (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/ppc64el (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/ppc64el openssl
• libsylph/s390x (1.1.0-21 to 1.1.0-21)
  • Migration status for libsylph/s390x (1.1.0-21 to 1.1.0-21): Will attempt migration (Any information below is purely informational)
    • Depends: libsylph/s390x openssl
• libtgowt_pu (0~git20220202.d618d0b+dfsg-2 to 0~git20210627.91d836d+dfsg-3~deb11u1)
  • Migration status for libtgowt_pu (0~git20220202.d618d0b+dfsg-2 to 0~git20210627.91d836d+dfsg-3~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libtgowt is newer in the target suite (0~git20220202.d618d0b+dfsg-2 0~git20210627.91d836d+dfsg-3~deb11u1)
• libtins/amd64 (4.0-1 to 4.0-1)
  • Migration status for libtins/amd64 (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/amd64 openssl
• libtins/arm64 (4.0-1 to 4.0-1)
  • Migration status for libtins/arm64 (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/arm64 openssl
• libtins/armel (4.0-1 to 4.0-1)
  • Migration status for libtins/armel (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/armel openssl
• libtins/armhf (4.0-1 to 4.0-1)
  • Migration status for libtins/armhf (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/armhf openssl
• libtins/i386 (4.0-1 to 4.0-1)
  • Migration status for libtins/i386 (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/i386 openssl
• libtins/mips64el (4.0-1 to 4.0-1)
  • Migration status for libtins/mips64el (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/mips64el openssl
• libtins/mipsel (4.0-1 to 4.0-1)
  • Migration status for libtins/mipsel (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/mipsel openssl
• libtins/ppc64el (4.0-1 to 4.0-1)
  • Migration status for libtins/ppc64el (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/ppc64el openssl
• libtins/s390x (4.0-1 to 4.0-1)
  • Migration status for libtins/s390x (4.0-1 to 4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libtins/s390x openssl
• libtorrent-rasterbar/amd64 (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/amd64 (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/amd64 openssl
• libtorrent-rasterbar/arm64 (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/arm64 (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/arm64 openssl
• libtorrent-rasterbar/armel (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/armel (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/armel openssl
• libtorrent-rasterbar/armhf (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/armhf (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/armhf openssl
• libtorrent-rasterbar/i386 (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/i386 (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/i386 openssl
• libtorrent-rasterbar/mips64el (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/mips64el (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/mips64el openssl
• libtorrent-rasterbar/mipsel (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/mipsel (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/mipsel openssl
• libtorrent-rasterbar/ppc64el (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/ppc64el (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/ppc64el openssl
• libtorrent-rasterbar/s390x (2.0.6-3 to 2.0.6-3)
  • Migration status for libtorrent-rasterbar/s390x (2.0.6-3 to 2.0.6-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent-rasterbar/s390x openssl
• libtorrent/amd64 (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/amd64 (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/amd64 openssl
• libtorrent/arm64 (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/arm64 (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/arm64 openssl
• libtorrent/armel (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/armel (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/armel openssl
• libtorrent/armhf (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/armhf (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/armhf openssl
• libtorrent/i386 (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/i386 (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/i386 openssl
• libtorrent/mips64el (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/mips64el (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/mips64el openssl
• libtorrent/mipsel (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/mipsel (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/mipsel openssl
• libtorrent/ppc64el (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/ppc64el (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/ppc64el openssl
• libtorrent/s390x (0.13.8-2 to 0.13.8-2)
  • Migration status for libtorrent/s390x (0.13.8-2 to 0.13.8-2): Will attempt migration (Any information below is purely informational)
    • Depends: libtorrent/s390x openssl
• libtpms/amd64 (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/amd64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/amd64 openssl
• libtpms/arm64 (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/arm64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/arm64 openssl
• libtpms/armel (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/armel (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/armel openssl
• libtpms/armhf (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/armhf (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/armhf openssl
• libtpms/i386 (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/i386 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/i386 openssl
• libtpms/mips64el (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/mips64el (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/mips64el openssl
• libtpms/mipsel (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/mipsel (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/mipsel openssl
• libtpms/ppc64el (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/ppc64el (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/ppc64el openssl
• libtpms/s390x (0.9.2-3 to 0.9.2-3)
  • Migration status for libtpms/s390x (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: libtpms/s390x openssl
• libu2f-server/amd64 (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/amd64 (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/amd64 openssl
• libu2f-server/arm64 (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/arm64 (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/arm64 openssl
• libu2f-server/armel (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/armel (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/armel openssl
• libu2f-server/armhf (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/armhf (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/armhf openssl
• libu2f-server/i386 (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/i386 (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/i386 openssl
• libu2f-server/mips64el (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/mips64el (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/mips64el openssl
• libu2f-server/mipsel (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/mipsel (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/mipsel openssl
• libu2f-server/ppc64el (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/ppc64el (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/ppc64el openssl
• libu2f-server/s390x (1.1.0-4 to 1.1.0-4)
  • Migration status for libu2f-server/s390x (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libu2f-server/s390x openssl
• libwebsockets/amd64 (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/amd64 (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/amd64 openssl
• libwebsockets/arm64 (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/arm64 (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/arm64 openssl
• libwebsockets/armel (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/armel (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/armel openssl
• libwebsockets/armhf (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/armhf (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/armhf openssl
• libwebsockets/i386 (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/i386 (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/i386 openssl
• libwebsockets/mips64el (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/mips64el (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/mips64el openssl
• libwebsockets/mipsel (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/mipsel (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/mipsel openssl
• libwebsockets/ppc64el (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/ppc64el (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/ppc64el openssl
• libwebsockets/s390x (4.0.20-3 to 4.0.20-3)
  • Migration status for libwebsockets/s390x (4.0.20-3 to 4.0.20-3): Will attempt migration (Any information below is purely informational)
    • Depends: libwebsockets/s390x openssl
• libxlsxwriter/amd64 (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/amd64 (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/amd64 openssl
• libxlsxwriter/arm64 (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/arm64 (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/arm64 openssl
• libxlsxwriter/armel (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/armel (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/armel openssl
• libxlsxwriter/armhf (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/armhf (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/armhf openssl
• libxlsxwriter/i386 (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/i386 (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/i386 openssl
• libxlsxwriter/mips64el (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/mips64el (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/mips64el openssl
• libxlsxwriter/mipsel (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/mipsel (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/mipsel openssl
• libxlsxwriter/ppc64el (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/ppc64el (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/ppc64el openssl
• libxlsxwriter/s390x (1.1.4-2 to 1.1.4-2)
  • Migration status for libxlsxwriter/s390x (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: libxlsxwriter/s390x openssl
• libxml2_pu (2.9.14+dfsg-1 to 2.9.10+dfsg-6.7+deb11u2)
  • Migration status for libxml2_pu (2.9.14+dfsg-1 to 2.9.10+dfsg-6.7+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libxml2 is newer in the target suite (2.9.14+dfsg-1 2.9.10+dfsg-6.7+deb11u2)
• libzip/amd64 (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/amd64 (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/amd64 openssl
• libzip/arm64 (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/arm64 (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/arm64 openssl
• libzip/armel (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/armel (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/armel openssl
• libzip/armhf (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/armhf (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/armhf openssl
• libzip/i386 (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/i386 (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/i386 openssl
• libzip/mips64el (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/mips64el (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/mips64el openssl
• libzip/mipsel (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/mipsel (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/mipsel openssl
• libzip/ppc64el (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/ppc64el (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/ppc64el openssl
• libzip/s390x (1.7.3-1 to 1.7.3-1)
  • Migration status for libzip/s390x (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: libzip/s390x openssl
• libzypp/amd64 (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/amd64 (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/amd64 openssl
• libzypp/arm64 (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/arm64 (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/arm64 openssl
• libzypp/armel (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/armel (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/armel openssl
• libzypp/armhf (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/armhf (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/armhf openssl
• libzypp/i386 (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/i386 (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/i386 openssl
• libzypp/mips64el (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/mips64el (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/mips64el openssl
• libzypp/mipsel (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/mipsel (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/mipsel openssl
• libzypp/ppc64el (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/ppc64el (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/ppc64el openssl
• libzypp/s390x (17.25.7-2.1 to 17.25.7-2.1)
  • Migration status for libzypp/s390x (17.25.7-2.1 to 17.25.7-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libzypp/s390x openssl
• links2/amd64 (2.26-1 to 2.26-1)
  • Migration status for links2/amd64 (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/amd64 openssl
• links2/arm64 (2.26-1 to 2.26-1)
  • Migration status for links2/arm64 (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/arm64 openssl
• links2/armel (2.26-1 to 2.26-1)
  • Migration status for links2/armel (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/armel openssl
• links2/armhf (2.26-1 to 2.26-1)
  • Migration status for links2/armhf (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/armhf openssl
• links2/i386 (2.26-1 to 2.26-1)
  • Migration status for links2/i386 (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/i386 openssl
• links2/mips64el (2.26-1 to 2.26-1)
  • Migration status for links2/mips64el (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/mips64el openssl
• links2/mipsel (2.26-1 to 2.26-1)
  • Migration status for links2/mipsel (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/mipsel openssl
• links2/ppc64el (2.26-1 to 2.26-1)
  • Migration status for links2/ppc64el (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/ppc64el openssl
• links2/s390x (2.26-1 to 2.26-1)
  • Migration status for links2/s390x (2.26-1 to 2.26-1): Will attempt migration (Any information below is purely informational)
    • Depends: links2/s390x openssl
• linux-ftpd-ssl/amd64 (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/amd64 (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/amd64 openssl
• linux-ftpd-ssl/arm64 (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/arm64 (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/arm64 openssl
• linux-ftpd-ssl/armel (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/armel (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/armel openssl
• linux-ftpd-ssl/armhf (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/armhf (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/armhf openssl
• linux-ftpd-ssl/i386 (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/i386 (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/i386 openssl
• linux-ftpd-ssl/mips64el (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/mips64el (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/mips64el openssl
• linux-ftpd-ssl/mipsel (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/mipsel (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/mipsel openssl
• linux-ftpd-ssl/ppc64el (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/ppc64el (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/ppc64el openssl
• linux-ftpd-ssl/s390x (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2)
  • Migration status for linux-ftpd-ssl/s390x (0.17.36+0.3-2.2 to 0.17.36+0.3-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: linux-ftpd-ssl/s390x openssl
• linux-signed-amd64_pu (5.17.3+1 to 5.10.113+1)
  • Migration status for linux-signed-amd64_pu (5.17.3+1 to 5.10.113+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-amd64 is newer in the target suite (5.17.3+1 5.10.113+1)
• linux-signed-arm64_pu (5.17.3+1 to 5.10.113+1)
  • Migration status for linux-signed-arm64_pu (5.17.3+1 to 5.10.113+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-arm64 is newer in the target suite (5.17.3+1 5.10.113+1)
• linux-signed-i386_pu (5.17.3+1 to 5.10.113+1)
  • Migration status for linux-signed-i386_pu (5.17.3+1 to 5.10.113+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-i386 is newer in the target suite (5.17.3+1 5.10.113+1)
• linux_pu (5.17.3-1 to 5.10.113-1)
  • Migration status for linux_pu (5.17.3-1 to 5.10.113-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux is newer in the target suite (5.17.3-1 5.10.113-1)
• lrzip_pu (0.651-2 to 0.641-1+deb11u1)
  • Migration status for lrzip_pu (0.651-2 to 0.641-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: lrzip is newer in the target suite (0.651-2 0.641-1+deb11u1)
• lua-cqueues/amd64 (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/amd64 (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/amd64 openssl
• lua-cqueues/arm64 (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/arm64 (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/arm64 openssl
• lua-cqueues/armel (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/armel (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/armel openssl
• lua-cqueues/armhf (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/armhf (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/armhf openssl
• lua-cqueues/i386 (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/i386 (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/i386 openssl
• lua-cqueues/mips64el (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/mips64el (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/mips64el openssl
• lua-cqueues/mipsel (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/mipsel (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/mipsel openssl
• lua-cqueues/ppc64el (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/ppc64el (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/ppc64el openssl
• lua-cqueues/s390x (20200726-1 to 20200726-1)
  • Migration status for lua-cqueues/s390x (20200726-1 to 20200726-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-cqueues/s390x openssl
• lua-sec/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/amd64 openssl
• lua-sec/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/arm64 openssl
• lua-sec/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/armel openssl
• lua-sec/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/armhf openssl
• lua-sec/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/i386 openssl
• lua-sec/mips64el (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/mips64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/mips64el openssl
• lua-sec/mipsel (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/mipsel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/mipsel openssl
• lua-sec/ppc64el (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/ppc64el (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/ppc64el openssl
• lua-sec/s390x (1.1.0-1 to 1.1.0-1)
  • Migration status for lua-sec/s390x (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: lua-sec/s390x openssl
• macopix/amd64 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/amd64 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/amd64 openssl
• macopix/arm64 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/arm64 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/arm64 openssl
• macopix/armel (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/armel (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/armel openssl
• macopix/armhf (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/armhf (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/armhf openssl
• macopix/i386 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/i386 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/i386 openssl
• macopix/mips64el (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/mips64el (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/mips64el openssl
• macopix/mipsel (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/mipsel (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/mipsel openssl
• macopix/ppc64el (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/ppc64el (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/ppc64el openssl
• macopix/s390x (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/s390x (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: macopix/s390x openssl
• mailfilter/amd64 (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/amd64 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/amd64 openssl
• mailfilter/arm64 (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/arm64 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/arm64 openssl
• mailfilter/armel (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/armel (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/armel openssl
• mailfilter/armhf (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/armhf (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/armhf openssl
• mailfilter/i386 (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/i386 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/i386 openssl
• mailfilter/mips64el (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/mips64el (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/mips64el openssl
• mailfilter/mipsel (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/mipsel (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/mipsel openssl
• mailfilter/ppc64el (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/ppc64el (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/ppc64el openssl
• mailfilter/s390x (0.8.7-1 to 0.8.7-1)
  • Migration status for mailfilter/s390x (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: mailfilter/s390x openssl
• medusa/amd64 (2.2-7 to 2.2-7)
  • Migration status for medusa/amd64 (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/amd64 openssl
• medusa/arm64 (2.2-7 to 2.2-7)
  • Migration status for medusa/arm64 (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/arm64 openssl
• medusa/armel (2.2-7 to 2.2-7)
  • Migration status for medusa/armel (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/armel openssl
• medusa/armhf (2.2-7 to 2.2-7)
  • Migration status for medusa/armhf (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/armhf openssl
• medusa/i386 (2.2-7 to 2.2-7)
  • Migration status for medusa/i386 (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/i386 openssl
• medusa/mips64el (2.2-7 to 2.2-7)
  • Migration status for medusa/mips64el (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/mips64el openssl
• medusa/mipsel (2.2-7 to 2.2-7)
  • Migration status for medusa/mipsel (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/mipsel openssl
• medusa/ppc64el (2.2-7 to 2.2-7)
  • Migration status for medusa/ppc64el (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/ppc64el openssl
• medusa/s390x (2.2-7 to 2.2-7)
  • Migration status for medusa/s390x (2.2-7 to 2.2-7): Will attempt migration (Any information below is purely informational)
    • Depends: medusa/s390x openssl
• memcached/amd64 (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/amd64 (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/amd64 openssl
• memcached/arm64 (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/arm64 (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/arm64 openssl
• memcached/armel (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/armel (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/armel openssl
• memcached/armhf (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/armhf (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/armhf openssl
• memcached/i386 (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/i386 (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/i386 openssl
• memcached/mips64el (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/mips64el (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/mips64el openssl
• memcached/mipsel (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/mipsel (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/mipsel openssl
• memcached/ppc64el (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/ppc64el (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/ppc64el openssl
• memcached/s390x (1.6.15-1 to 1.6.15-1)
  • Migration status for memcached/s390x (1.6.15-1 to 1.6.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: memcached/s390x openssl
• mender-client/amd64 (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/amd64 (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/amd64 golang-github-mendersoftware-openssl
    • Depends: mender-client/amd64 openssl
• mender-client/arm64 (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/arm64 (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/arm64 golang-github-mendersoftware-openssl
    • Depends: mender-client/arm64 openssl
• mender-client/armel (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/armel (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/armel golang-github-mendersoftware-openssl
    • Depends: mender-client/armel openssl
• mender-client/armhf (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/armhf (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/armhf golang-github-mendersoftware-openssl
    • Depends: mender-client/armhf openssl
• mender-client/i386 (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/i386 (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/i386 golang-github-mendersoftware-openssl
    • Depends: mender-client/i386 openssl
• mender-client/mips64el (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/mips64el (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/mips64el golang-github-mendersoftware-openssl
    • Depends: mender-client/mips64el openssl
• mender-client/ppc64el (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/ppc64el (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/ppc64el golang-github-mendersoftware-openssl
    • Depends: mender-client/ppc64el openssl
• mender-client/s390x (3.0.0+ds1-2 to 3.0.0+ds1-2)
  • Migration status for mender-client/s390x (3.0.0+ds1-2 to 3.0.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: mender-client/s390x golang-github-mendersoftware-openssl
    • Depends: mender-client/s390x openssl
• mfgtools/amd64 (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/amd64 (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/amd64 openssl
• mfgtools/arm64 (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/arm64 (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/arm64 openssl
• mfgtools/armel (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/armel (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/armel openssl
• mfgtools/armhf (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/armhf (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/armhf openssl
• mfgtools/i386 (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/i386 (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/i386 openssl
• mfgtools/mips64el (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/mips64el (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/mips64el openssl
• mfgtools/mipsel (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/mipsel (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/mipsel openssl
• mfgtools/ppc64el (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/ppc64el (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/ppc64el openssl
• mfgtools/s390x (1.4.193-1 to 1.4.193-1)
  • Migration status for mfgtools/s390x (1.4.193-1 to 1.4.193-1): Will attempt migration (Any information below is purely informational)
    • Depends: mfgtools/s390x openssl
• mini-httpd/amd64 (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/amd64 (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/amd64 openssl
• mini-httpd/arm64 (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/arm64 (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/arm64 openssl
• mini-httpd/armel (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/armel (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/armel openssl
• mini-httpd/armhf (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/armhf (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/armhf openssl
• mini-httpd/i386 (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/i386 (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/i386 openssl
• mini-httpd/mips64el (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/mips64el (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/mips64el openssl
• mini-httpd/mipsel (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/mipsel (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/mipsel openssl
• mini-httpd/ppc64el (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/ppc64el (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/ppc64el openssl
• mini-httpd/s390x (1.30-2 to 1.30-2)
  • Migration status for mini-httpd/s390x (1.30-2 to 1.30-2): Will attempt migration (Any information below is purely informational)
    • Depends: mini-httpd/s390x openssl
• mixxx/amd64 (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/amd64 (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/amd64 openssl
• mixxx/arm64 (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/arm64 (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/arm64 openssl
• mixxx/armel (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/armel (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/armel openssl
• mixxx/armhf (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/armhf (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/armhf openssl
• mixxx/i386 (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/i386 (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/i386 openssl
• mixxx/mips64el (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/mips64el (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/mips64el openssl
• mixxx/mipsel (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/mipsel (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/mipsel openssl
• mixxx/ppc64el (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/ppc64el (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/ppc64el openssl
• mixxx/s390x (2.3.2~dfsg-1 to 2.3.2~dfsg-1)
  • Migration status for mixxx/s390x (2.3.2~dfsg-1 to 2.3.2~dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mixxx/s390x openssl
• mokutil/amd64 (0.4.0-1 to 0.4.0-1)
  • Migration status for mokutil/amd64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mokutil/amd64 openssl
• mokutil/arm64 (0.4.0-1 to 0.4.0-1)
  • Migration status for mokutil/arm64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mokutil/arm64 openssl
• mokutil/armel (0.4.0-1 to 0.4.0-1)
  • Migration status for mokutil/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mokutil/armel openssl
• mokutil/armhf (0.4.0-1 to 0.4.0-1)
  • Migration status for mokutil/armhf (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mokutil/armhf openssl
• mokutil/i386 (0.4.0-1 to 0.4.0-1)
  • Migration status for mokutil/i386 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: mokutil/i386 openssl
• mold/amd64 (1.2.1+dfsg-1 to 1.2.1+dfsg-1)
  • Migration status for mold/amd64 (1.2.1+dfsg-1 to 1.2.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mold/amd64 openssl
• mold/arm64 (1.2.1+dfsg-1 to 1.2.1+dfsg-1)
  • Migration status for mold/arm64 (1.2.1+dfsg-1 to 1.2.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: mold/arm64 openssl
• mongo-cxx-driver-legacy/amd64 (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/amd64 (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/amd64 openssl
• mongo-cxx-driver-legacy/arm64 (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/arm64 (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/arm64 openssl
• mongo-cxx-driver-legacy/armel (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/armel (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/armel openssl
• mongo-cxx-driver-legacy/armhf (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/armhf (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/armhf openssl
• mongo-cxx-driver-legacy/i386 (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/i386 (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/i386 openssl
• mongo-cxx-driver-legacy/mips64el (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/mips64el (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/mips64el openssl
• mongo-cxx-driver-legacy/mipsel (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/mipsel (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/mipsel openssl
• mongo-cxx-driver-legacy/ppc64el (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/ppc64el (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/ppc64el openssl
• mongo-cxx-driver-legacy/s390x (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for mongo-cxx-driver-legacy/s390x (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: mongo-cxx-driver-legacy/s390x openssl
• monit/amd64 (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/amd64 (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/amd64 openssl
• monit/arm64 (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/arm64 (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/arm64 openssl
• monit/armel (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/armel (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/armel openssl
• monit/armhf (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/armhf (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/armhf openssl
• monit/i386 (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/i386 (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/i386 openssl
• monit/mips64el (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/mips64el (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/mips64el openssl
• monit/mipsel (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/mipsel (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/mipsel openssl
• monit/ppc64el (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/ppc64el (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/ppc64el openssl
• monit/s390x (1:5.32.0-1 to 1:5.32.0-1)
  • Migration status for monit/s390x (1:5.32.0-1 to 1:5.32.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: monit/s390x openssl
• monitoring-plugins/amd64 (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/amd64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/amd64 openssl
• monitoring-plugins/arm64 (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/arm64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/arm64 openssl
• monitoring-plugins/armel (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/armel (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/armel openssl
• monitoring-plugins/armhf (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/armhf (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/armhf openssl
• monitoring-plugins/i386 (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/i386 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/i386 openssl
• monitoring-plugins/mips64el (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/mips64el (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/mips64el openssl
• monitoring-plugins/mipsel (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/mipsel (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/mipsel openssl
• monitoring-plugins/ppc64el (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/ppc64el (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/ppc64el openssl
• monitoring-plugins/s390x (2.3.1-1 to 2.3.1-1)
  • Migration status for monitoring-plugins/s390x (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: monitoring-plugins/s390x openssl
• moonshot-gss-eap/amd64 (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/amd64 (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/amd64 openssl
• moonshot-gss-eap/arm64 (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/arm64 (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/arm64 openssl
• moonshot-gss-eap/armel (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/armel (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/armel openssl
• moonshot-gss-eap/armhf (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/armhf (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/armhf openssl
• moonshot-gss-eap/i386 (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/i386 (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/i386 openssl
• moonshot-gss-eap/mips64el (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/mips64el (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/mips64el openssl
• moonshot-gss-eap/mipsel (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/mipsel (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/mipsel openssl
• moonshot-gss-eap/ppc64el (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/ppc64el (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/ppc64el openssl
• moonshot-gss-eap/s390x (1.0.1-6 to 1.0.1-6)
  • Migration status for moonshot-gss-eap/s390x (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-gss-eap/s390x openssl
• moonshot-ui/amd64 (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/amd64 (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/amd64 openssl
• moonshot-ui/arm64 (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/arm64 (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/arm64 openssl
• moonshot-ui/armel (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/armel (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/armel openssl
• moonshot-ui/armhf (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/armhf (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/armhf openssl
• moonshot-ui/i386 (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/i386 (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/i386 openssl
• moonshot-ui/mips64el (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/mips64el (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/mips64el openssl
• moonshot-ui/mipsel (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/mipsel (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/mipsel openssl
• moonshot-ui/ppc64el (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/ppc64el (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/ppc64el openssl
• moonshot-ui/s390x (1.1.0+libsecret~2 to 1.1.0+libsecret~2)
  • Migration status for moonshot-ui/s390x (1.1.0+libsecret~2 to 1.1.0+libsecret~2): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-ui/s390x openssl
• morbig/amd64 (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/amd64 (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/amd64 menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/amd64 morsmall/amd64
• morbig/arm64 (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/arm64 (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/arm64 menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/arm64 morsmall/arm64
• morbig/armel (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/armel (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/armel menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/armel morsmall/armel
• morbig/armhf (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/armhf (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/armhf menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/armhf morsmall/armhf
• morbig/i386 (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/i386 (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/i386 menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/i386 morsmall/i386
• morbig/mips64el (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/mips64el (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/mips64el menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/mips64el morsmall/mips64el
• morbig/mipsel (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/mipsel (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/mipsel menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/mipsel morsmall/mipsel
• morbig/ppc64el (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/ppc64el (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/ppc64el menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/ppc64el morsmall/ppc64el
• morbig/s390x (0.10.4-5 to 0.10.4-5)
  • Migration status for morbig/s390x (0.10.4-5 to 0.10.4-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morbig/s390x menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: morbig/s390x morsmall/s390x
• morsmall/amd64 (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/amd64 (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/amd64 morbig/amd64 (not considered)
    • Invalidated by dependency
• morsmall/arm64 (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/arm64 (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/arm64 morbig/arm64 (not considered)
    • Invalidated by dependency
• morsmall/armel (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/armel (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/armel morbig/armel (not considered)
    • Invalidated by dependency
• morsmall/armhf (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/armhf (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/armhf morbig/armhf (not considered)
    • Invalidated by dependency
• morsmall/i386 (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/i386 (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/i386 morbig/i386 (not considered)
    • Invalidated by dependency
• morsmall/mips64el (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/mips64el (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/mips64el morbig/mips64el (not considered)
    • Invalidated by dependency
• morsmall/mipsel (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/mipsel (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/mipsel morbig/mipsel (not considered)
    • Invalidated by dependency
• morsmall/ppc64el (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/ppc64el (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/ppc64el morbig/ppc64el (not considered)
    • Invalidated by dependency
• morsmall/s390x (0.3.0-4 to 0.3.0-4)
  • Migration status for morsmall/s390x (0.3.0-4 to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: morsmall/s390x morbig/s390x (not considered)
    • Invalidated by dependency
• mosquitto/amd64 (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/amd64 (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/amd64 openssl
• mosquitto/arm64 (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/arm64 (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/arm64 openssl
• mosquitto/armel (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/armel (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/armel openssl
• mosquitto/armhf (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/armhf (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/armhf openssl
• mosquitto/i386 (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/i386 (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/i386 openssl
• mosquitto/mips64el (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/mips64el (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/mips64el openssl
• mosquitto/mipsel (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/mipsel (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/mipsel openssl
• mosquitto/ppc64el (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/ppc64el (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/ppc64el openssl
• mosquitto/s390x (2.0.11-1.1 to 2.0.11-1.1)
  • Migration status for mosquitto/s390x (2.0.11-1.1 to 2.0.11-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: mosquitto/s390x openssl
• mtd-utils/amd64 (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/amd64 (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/amd64 openssl
• mtd-utils/arm64 (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/arm64 (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/arm64 openssl
• mtd-utils/armel (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/armel (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/armel openssl
• mtd-utils/armhf (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/armhf (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/armhf openssl
• mtd-utils/i386 (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/i386 (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/i386 openssl
• mtd-utils/mips64el (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/mips64el (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/mips64el openssl
• mtd-utils/mipsel (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/mipsel (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/mipsel openssl
• mtd-utils/ppc64el (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/ppc64el (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/ppc64el openssl
• mtd-utils/s390x (1:2.1.4-1 to 1:2.1.4-1)
  • Migration status for mtd-utils/s390x (1:2.1.4-1 to 1:2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: mtd-utils/s390x openssl
• muchsync/amd64 (6-1 to 6-1)
  • Migration status for muchsync/amd64 (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/amd64 openssl
• muchsync/arm64 (6-1 to 6-1)
  • Migration status for muchsync/arm64 (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/arm64 openssl
• muchsync/armel (6-1 to 6-1)
  • Migration status for muchsync/armel (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/armel openssl
• muchsync/armhf (6-1 to 6-1)
  • Migration status for muchsync/armhf (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/armhf openssl
• muchsync/i386 (6-1 to 6-1)
  • Migration status for muchsync/i386 (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/i386 openssl
• muchsync/mips64el (6-1 to 6-1)
  • Migration status for muchsync/mips64el (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/mips64el openssl
• muchsync/mipsel (6-1 to 6-1)
  • Migration status for muchsync/mipsel (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/mipsel openssl
• muchsync/ppc64el (6-1 to 6-1)
  • Migration status for muchsync/ppc64el (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/ppc64el openssl
• muchsync/s390x (6-1 to 6-1)
  • Migration status for muchsync/s390x (6-1 to 6-1): Will attempt migration (Any information below is purely informational)
    • Depends: muchsync/s390x openssl
• mupdf/amd64 (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/amd64 (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/amd64 openssl
• mupdf/arm64 (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/arm64 (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/arm64 openssl
• mupdf/armel (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/armel (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/armel openssl
• mupdf/armhf (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/armhf (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/armhf openssl
• mupdf/i386 (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/i386 (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/i386 openssl
• mupdf/mips64el (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/mips64el (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/mips64el openssl
• mupdf/mipsel (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/mipsel (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/mipsel openssl
• mupdf/ppc64el (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/ppc64el (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/ppc64el openssl
• mupdf/s390x (1.19.0+ds1-2 to 1.19.0+ds1-2)
  • Migration status for mupdf/s390x (1.19.0+ds1-2 to 1.19.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Depends: mupdf/s390x openssl
• mutt_pu (2.2.4-1 to 2.0.5-4.1+deb11u1)
  • Migration status for mutt_pu (2.2.4-1 to 2.0.5-4.1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: mutt is newer in the target suite (2.2.4-1 2.0.5-4.1+deb11u1)
• nagios-nrpe/amd64 (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/amd64 (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/amd64 openssl
• nagios-nrpe/arm64 (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/arm64 (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/arm64 openssl
• nagios-nrpe/armel (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/armel (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/armel openssl
• nagios-nrpe/armhf (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/armhf (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/armhf openssl
• nagios-nrpe/i386 (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/i386 (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/i386 openssl
• nagios-nrpe/mips64el (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/mips64el (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/mips64el openssl
• nagios-nrpe/mipsel (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/mipsel (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/mipsel openssl
• nagios-nrpe/ppc64el (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/ppc64el (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/ppc64el openssl
• nagios-nrpe/s390x (4.0.3-1 to 4.0.3-1)
  • Migration status for nagios-nrpe/s390x (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: nagios-nrpe/s390x openssl
• nano_pu (6.3-1 to 5.4-2+deb11u1)
  • Migration status for nano_pu (6.3-1 to 5.4-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nano is newer in the target suite (6.3-1 5.4-2+deb11u1)
• nats.c/amd64 (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/amd64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/amd64 openssl
• nats.c/arm64 (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/arm64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/arm64 openssl
• nats.c/armhf (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/armhf (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/armhf openssl
• nats.c/i386 (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/i386 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/i386 openssl
• nats.c/mips64el (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/mips64el (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/mips64el openssl
• nats.c/mipsel (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/mipsel (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/mipsel openssl
• nats.c/ppc64el (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/ppc64el (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/ppc64el openssl
• nats.c/s390x (3.3.0-1 to 3.3.0-1)
  • Migration status for nats.c/s390x (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nats.c/s390x openssl
• ncrack/amd64 (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/amd64 (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/amd64 openssl
• ncrack/arm64 (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/arm64 (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/arm64 openssl
• ncrack/armel (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/armel (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/armel openssl
• ncrack/armhf (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/armhf (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/armhf openssl
• ncrack/i386 (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/i386 (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/i386 openssl
• ncrack/mips64el (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/mips64el (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/mips64el openssl
• ncrack/mipsel (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/mipsel (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/mipsel openssl
• ncrack/ppc64el (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/ppc64el (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/ppc64el openssl
• ncrack/s390x (0.7+debian-3 to 0.7+debian-3)
  • Migration status for ncrack/s390x (0.7+debian-3 to 0.7+debian-3): Will attempt migration (Any information below is purely informational)
    • Depends: ncrack/s390x openssl
• needrestart_pu (3.6-1 to 3.5-4+deb11u2)
  • Migration status for needrestart_pu (3.6-1 to 3.5-4+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: needrestart is newer in the target suite (3.6-1 3.5-4+deb11u2)
• neon27/amd64 (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/amd64 (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/amd64 openssl
• neon27/arm64 (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/arm64 (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/arm64 openssl
• neon27/armel (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/armel (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/armel openssl
• neon27/armhf (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/armhf (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/armhf openssl
• neon27/i386 (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/i386 (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/i386 openssl
• neon27/mips64el (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/mips64el (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/mips64el openssl
• neon27/mipsel (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/mipsel (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/mipsel openssl
• neon27/ppc64el (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/ppc64el (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/ppc64el openssl
• neon27/s390x (0.32.2-1 to 0.32.2-1)
  • Migration status for neon27/s390x (0.32.2-1 to 0.32.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: neon27/s390x openssl
• netatalk/amd64 (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/amd64 (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/amd64 openssl
• netatalk/arm64 (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/arm64 (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/arm64 openssl
• netatalk/armel (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/armel (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/armel openssl
• netatalk/armhf (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/armhf (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/armhf openssl
• netatalk/i386 (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/i386 (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/i386 openssl
• netatalk/mips64el (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/mips64el (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/mips64el openssl
• netatalk/mipsel (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/mipsel (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/mipsel openssl
• netatalk/ppc64el (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/ppc64el (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/ppc64el openssl
• netatalk/s390x (3.1.13~ds-1 to 3.1.13~ds-1)
  • Migration status for netatalk/s390x (3.1.13~ds-1 to 3.1.13~ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: netatalk/s390x openssl
• netkit-ftp-ssl/amd64 (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/amd64 (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/amd64 openssl
• netkit-ftp-ssl/arm64 (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/arm64 (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/arm64 openssl
• netkit-ftp-ssl/armel (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/armel (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/armel openssl
• netkit-ftp-ssl/armhf (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/armhf (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/armhf openssl
• netkit-ftp-ssl/i386 (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/i386 (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/i386 openssl
• netkit-ftp-ssl/mips64el (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/mips64el (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/mips64el openssl
• netkit-ftp-ssl/mipsel (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/mipsel (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/mipsel openssl
• netkit-ftp-ssl/ppc64el (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/ppc64el (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/ppc64el openssl
• netkit-ftp-ssl/s390x (0.17.34+really0.17-1 to 0.17.34+really0.17-1)
  • Migration status for netkit-ftp-ssl/s390x (0.17.34+really0.17-1 to 0.17.34+really0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-ftp-ssl/s390x openssl
• netkit-telnet-ssl/amd64 (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/amd64 (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/amd64 openssl
• netkit-telnet-ssl/arm64 (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/arm64 (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/arm64 openssl
• netkit-telnet-ssl/armel (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/armel (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/armel openssl
• netkit-telnet-ssl/armhf (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/armhf (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/armhf openssl
• netkit-telnet-ssl/i386 (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/i386 (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/i386 openssl
• netkit-telnet-ssl/mips64el (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/mips64el (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/mips64el openssl
• netkit-telnet-ssl/mipsel (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/mipsel (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/mipsel openssl
• netkit-telnet-ssl/ppc64el (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/ppc64el (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/ppc64el openssl
• netkit-telnet-ssl/s390x (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3)
  • Migration status for netkit-telnet-ssl/s390x (0.17.41+0.2-3.3 to 0.17.41+0.2-3.3): Will attempt migration (Any information below is purely informational)
    • Depends: netkit-telnet-ssl/s390x openssl
• netsurf/amd64 (3.10-1 to 3.10-1)
  • Migration status for netsurf/amd64 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/amd64 openssl
• netsurf/arm64 (3.10-1 to 3.10-1)
  • Migration status for netsurf/arm64 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/arm64 openssl
• netsurf/armel (3.10-1 to 3.10-1)
  • Migration status for netsurf/armel (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/armel openssl
• netsurf/armhf (3.10-1 to 3.10-1)
  • Migration status for netsurf/armhf (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/armhf openssl
• netsurf/i386 (3.10-1 to 3.10-1)
  • Migration status for netsurf/i386 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/i386 openssl
• netsurf/mips64el (3.10-1 to 3.10-1)
  • Migration status for netsurf/mips64el (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/mips64el openssl
• netsurf/mipsel (3.10-1 to 3.10-1)
  • Migration status for netsurf/mipsel (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/mipsel openssl
• netsurf/ppc64el (3.10-1 to 3.10-1)
  • Migration status for netsurf/ppc64el (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/ppc64el openssl
• netsurf/s390x (3.10-1 to 3.10-1)
  • Migration status for netsurf/s390x (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: netsurf/s390x openssl
• netty-tcnative/amd64 (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/amd64 (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/amd64 openssl
• netty-tcnative/arm64 (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/arm64 (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/arm64 openssl
• netty-tcnative/armel (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/armel (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/armel openssl
• netty-tcnative/armhf (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/armhf (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/armhf openssl
• netty-tcnative/i386 (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/i386 (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/i386 openssl
• netty-tcnative/mips64el (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/mips64el (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/mips64el openssl
• netty-tcnative/mipsel (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/mipsel (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/mipsel openssl
• netty-tcnative/ppc64el (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/ppc64el (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/ppc64el openssl
• netty-tcnative/s390x (2.0.28-1 to 2.0.28-1)
  • Migration status for netty-tcnative/s390x (2.0.28-1 to 2.0.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: netty-tcnative/s390x openssl
• network-manager-l2tp/amd64 (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/amd64 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/amd64 openssl
• network-manager-l2tp/arm64 (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/arm64 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/arm64 openssl
• network-manager-l2tp/armel (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/armel (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/armel openssl
• network-manager-l2tp/armhf (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/armhf (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/armhf openssl
• network-manager-l2tp/i386 (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/i386 (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/i386 openssl
• network-manager-l2tp/mips64el (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/mips64el (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/mips64el openssl
• network-manager-l2tp/mipsel (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/mipsel (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/mipsel openssl
• network-manager-l2tp/ppc64el (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/ppc64el (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/ppc64el openssl
• network-manager-l2tp/s390x (1.20.2-1 to 1.20.2-1)
  • Migration status for network-manager-l2tp/s390x (1.20.2-1 to 1.20.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: network-manager-l2tp/s390x openssl
• network-manager_pu (1.38.0-2 to 1.30.6-1+deb11u1)
  • Migration status for network-manager_pu (1.38.0-2 to 1.30.6-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: network-manager is newer in the target suite (1.38.0-2 1.30.6-1+deb11u1)
• nghttp2/amd64 (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/amd64 (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/amd64 openssl
• nghttp2/arm64 (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/arm64 (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/arm64 openssl
• nghttp2/armel (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/armel (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/armel openssl
• nghttp2/armhf (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/armhf (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/armhf openssl
• nghttp2/i386 (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/i386 (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/i386 openssl
• nghttp2/mips64el (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/mips64el (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/mips64el openssl
• nghttp2/mipsel (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/mipsel (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/mipsel openssl
• nghttp2/ppc64el (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/ppc64el (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/ppc64el openssl
• nghttp2/s390x (1.47.0-1 to 1.47.0-1)
  • Migration status for nghttp2/s390x (1.47.0-1 to 1.47.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nghttp2/s390x openssl
• nginx/amd64 (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/amd64 (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/amd64 openssl
• nginx/arm64 (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/arm64 (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/arm64 openssl
• nginx/armel (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/armel (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/armel openssl
• nginx/armhf (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/armhf (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/armhf openssl
• nginx/i386 (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/i386 (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/i386 openssl
• nginx/mips64el (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/mips64el (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/mips64el openssl
• nginx/mipsel (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/mipsel (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/mipsel openssl
• nginx/ppc64el (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/ppc64el (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/ppc64el openssl
• nginx/s390x (1.20.2-2 to 1.20.2-2)
  • Migration status for nginx/s390x (1.20.2-2 to 1.20.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: nginx/s390x openssl
• nginx_pu (1.20.2-2 to 1.18.0-6.1+deb11u2)
  • Migration status for nginx_pu (1.20.2-2 to 1.18.0-6.1+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nginx is newer in the target suite (1.20.2-2 1.18.0-6.1+deb11u2)
• nix/amd64 (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/amd64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/amd64 openssl
• nix/arm64 (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/arm64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/arm64 openssl
• nix/armel (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/armel (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/armel openssl
• nix/armhf (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/armhf (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/armhf openssl
• nix/i386 (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/i386 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/i386 openssl
• nix/mips64el (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/mips64el (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/mips64el openssl
• nix/mipsel (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/mipsel (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/mipsel openssl
• nix/ppc64el (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/ppc64el (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/ppc64el openssl
• nix/s390x (2.8.0-1 to 2.8.0-1)
  • Migration status for nix/s390x (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nix/s390x openssl
• nmap/amd64 (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/amd64 (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/amd64 openssl
• nmap/arm64 (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/arm64 (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/arm64 openssl
• nmap/armel (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/armel (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/armel openssl
• nmap/armhf (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/armhf (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/armhf openssl
• nmap/i386 (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/i386 (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/i386 openssl
• nmap/mips64el (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/mips64el (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/mips64el openssl
• nmap/mipsel (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/mipsel (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/mipsel openssl
• nmap/ppc64el (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/ppc64el (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/ppc64el openssl
• nmap/s390x (7.92+dfsg2-1 to 7.92+dfsg2-1)
  • Migration status for nmap/s390x (7.92+dfsg2-1 to 7.92+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: nmap/s390x openssl
• nmh/amd64 (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/amd64 (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/amd64 openssl
• nmh/arm64 (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/arm64 (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/arm64 openssl
• nmh/armel (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/armel (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/armel openssl
• nmh/armhf (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/armhf (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/armhf openssl
• nmh/i386 (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/i386 (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/i386 openssl
• nmh/mips64el (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/mips64el (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/mips64el openssl
• nmh/mipsel (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/mipsel (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/mipsel openssl
• nmh/ppc64el (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/ppc64el (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/ppc64el openssl
• nmh/s390x (1.7.1-12 to 1.7.1-12)
  • Migration status for nmh/s390x (1.7.1-12 to 1.7.1-12): Will attempt migration (Any information below is purely informational)
    • Depends: nmh/s390x openssl
• nodau/amd64 (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/amd64 (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/amd64 openssl
• nodau/arm64 (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/arm64 (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/arm64 openssl
• nodau/armel (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/armel (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/armel openssl
• nodau/armhf (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/armhf (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/armhf openssl
• nodau/i386 (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/i386 (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/i386 openssl
• nodau/mips64el (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/mips64el (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/mips64el openssl
• nodau/mipsel (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/mipsel (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/mipsel openssl
• nodau/ppc64el (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/ppc64el (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/ppc64el openssl
• nodau/s390x (0.3.8-4 to 0.3.8-4)
  • Migration status for nodau/s390x (0.3.8-4 to 0.3.8-4): Will attempt migration (Any information below is purely informational)
    • Depends: nodau/s390x openssl
• node-ejs_pu (3.1.8+~3.1.1-1 to 2.5.7-3+deb11u1)
  • Migration status for node-ejs_pu (3.1.8+~3.1.1-1 to 2.5.7-3+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-ejs is newer in the target suite (3.1.8+~3.1.1-1 2.5.7-3+deb11u1)
• node-eventsource_pu (2.0.2+~1.1.8-1 to 1.0.7-1+deb11u1)
  • Migration status for node-eventsource_pu (2.0.2+~1.1.8-1 to 1.0.7-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-eventsource is newer in the target suite (2.0.2+~1.1.8-1 1.0.7-1+deb11u1)
• node-mermaid_pu (8.14.0+~cs11.4.14-1 to 8.7.0+ds+~cs27.17.17-3+deb11u1)
  • Migration status for node-mermaid_pu (8.14.0+~cs11.4.14-1 to 8.7.0+ds+~cs27.17.17-3+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-mermaid is newer in the target suite (8.14.0+~cs11.4.14-1 8.7.0+ds+~cs27.17.17-3+deb11u1)
• node-minimist_pu (1.2.6+~cs5.3.2-1 to 1.2.5+~cs5.3.1-2+deb11u1)
  • Migration status for node-minimist_pu (1.2.6+~cs5.3.2-1 to 1.2.5+~cs5.3.1-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-minimist is newer in the target suite (1.2.6+~cs5.3.2-1 1.2.5+~cs5.3.1-2+deb11u1)
• node-moment_pu (2.29.3+ds-1 to 2.29.1+ds-2+deb11u1)
  • Migration status for node-moment_pu (2.29.3+ds-1 to 2.29.1+ds-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-moment is newer in the target suite (2.29.3+ds-1 2.29.1+ds-2+deb11u1)
• node-node-forge_pu (1.3.0~dfsg-1 to 0.10.0~dfsg-3+deb11u1)
  • Migration status for node-node-forge_pu (1.3.0~dfsg-1 to 0.10.0~dfsg-3+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-node-forge is newer in the target suite (1.3.0~dfsg-1 0.10.0~dfsg-3+deb11u1)
• node-raw-body_pu (2.5.1-1 to 2.4.1-2+deb11u1)
  • Migration status for node-raw-body_pu (2.5.1-1 to 2.4.1-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-raw-body is newer in the target suite (2.5.1-1 2.4.1-2+deb11u1)
• node-sqlite3_pu (5.0.8+ds1-1 to 5.0.0+ds1-1+deb11u1)
  • Migration status for node-sqlite3_pu (5.0.8+ds1-1 to 5.0.0+ds1-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-sqlite3 is newer in the target suite (5.0.8+ds1-1 5.0.0+ds1-1+deb11u1)
• node-url-parse_pu (1.5.10+~1.4.8-2 to 1.5.3-1+deb11u1)
  • Migration status for node-url-parse_pu (1.5.10+~1.4.8-2 to 1.5.3-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-url-parse is newer in the target suite (1.5.10+~1.4.8-2 1.5.3-1+deb11u1)
• ntopng/amd64 (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/amd64 (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/amd64 openssl
• ntopng/arm64 (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/arm64 (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/arm64 openssl
• ntopng/armhf (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/armhf (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/armhf openssl
• ntopng/i386 (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/i386 (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/i386 openssl
• ntopng/mips64el (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/mips64el (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/mips64el openssl
• ntopng/mipsel (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/mipsel (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/mipsel openssl
• ntopng/ppc64el (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1)
  • Migration status for ntopng/ppc64el (5.2.1+dfsg1-1 to 5.2.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ntopng/ppc64el openssl
• nurpawiki/amd64 (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/amd64 (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/amd64 js-of-ocaml/amd64 (not considered)
    • Invalidated by dependency
• nurpawiki/arm64 (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/arm64 (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/arm64 js-of-ocaml/arm64 (not considered)
    • Invalidated by dependency
• nurpawiki/armel (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/armel (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/armel js-of-ocaml/armel (not considered)
    • Invalidated by dependency
• nurpawiki/armhf (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/armhf (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/armhf js-of-ocaml/armhf (not considered)
    • Invalidated by dependency
• nurpawiki/i386 (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/i386 (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/i386 js-of-ocaml/i386 (not considered)
    • Invalidated by dependency
• nurpawiki/mips64el (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/mips64el (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/mips64el js-of-ocaml/mips64el (not considered)
    • Invalidated by dependency
• nurpawiki/mipsel (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/mipsel (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/mipsel js-of-ocaml/mipsel (not considered)
    • Invalidated by dependency
• nurpawiki/ppc64el (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/ppc64el (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/ppc64el js-of-ocaml/ppc64el (not considered)
    • Invalidated by dependency
• nurpawiki/s390x (1.2.4-2 to 1.2.4-2)
  • Migration status for nurpawiki/s390x (1.2.4-2 to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nurpawiki/s390x js-of-ocaml/s390x (not considered)
    • Invalidated by dependency
• nvidia-cuda-toolkit_pu (11.4.3-3 to 11.2.2-3+deb11u2)
  • Migration status for nvidia-cuda-toolkit_pu (11.4.3-3 to 11.2.2-3+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-cuda-toolkit is newer in the target suite (11.4.3-3 11.2.2-3+deb11u2)
• nvidia-graphics-drivers-tesla-470_pu (470.129.06-3 to 470.103.01-2~deb11u1)
  • Migration status for nvidia-graphics-drivers-tesla-470_pu (470.129.06-3 to 470.103.01-2~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-graphics-drivers-tesla-470 is newer in the target suite (470.129.06-3 470.103.01-2~deb11u1)
• nvidia-graphics-drivers_pu (470.129.06-3 to 470.103.01-3~deb11u2)
  • Migration status for nvidia-graphics-drivers_pu (470.129.06-3 to 470.103.01-3~deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-graphics-drivers is newer in the target suite (470.129.06-3 470.103.01-3~deb11u2)
• nvidia-persistenced_pu (470.103.01-2 to 470.103.01-2~deb11u1)
  • Migration status for nvidia-persistenced_pu (470.103.01-2 to 470.103.01-2~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-persistenced is newer in the target suite (470.103.01-2 470.103.01-2~deb11u1)
• nvidia-settings-tesla-470_pu (470.103.01-2 to 470.103.01-1~deb11u1)
  • Migration status for nvidia-settings-tesla-470_pu (470.103.01-2 to 470.103.01-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-settings-tesla-470 is newer in the target suite (470.103.01-2 470.103.01-1~deb11u1)
• nvidia-settings_pu (470.103.01-2 to 470.103.01-1~deb11u1)
  • Migration status for nvidia-settings_pu (470.103.01-2 to 470.103.01-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-settings is newer in the target suite (470.103.01-2 470.103.01-1~deb11u1)
• nvidia-xconfig_pu (470.103.01-1 to 470.103.01-1~deb11u1)
  • Migration status for nvidia-xconfig_pu (470.103.01-1 to 470.103.01-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: nvidia-xconfig is newer in the target suite (470.103.01-1 470.103.01-1~deb11u1)
• obs-advanced-scene-switcher/s390x (1.17.5-1 to 1.17.5-1)
  • Migration status for obs-advanced-scene-switcher/s390x (1.17.5-1 to 1.17.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: obs-advanced-scene-switcher/s390x obs-studio/s390x
• obs-move-transition/s390x (2.5.8-1 to 2.5.8-1)
  • Migration status for obs-move-transition/s390x (2.5.8-1 to 2.5.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: obs-move-transition/s390x obs-studio/s390x
• obs-ptz/s390x (0.10.4-1 to 0.10.4-1)
  • Migration status for obs-ptz/s390x (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: obs-ptz/s390x obs-studio/s390x
• obs-scene-notes-dock/s390x (0.0.4-1 to 0.0.4-1)
  • Migration status for obs-scene-notes-dock/s390x (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: obs-scene-notes-dock/s390x obs-studio/s390x
• obs-studio/s390x (27.2.4+dfsg1-2 to 27.2.4+dfsg1-2)
  • Migration status for obs-studio/s390x (27.2.4+dfsg1-2 to 27.2.4+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: obs-studio/s390x luajit2
• obs-text-slideshow/s390x (1.5.2-2 to 1.5.2-2)
  • Migration status for obs-text-slideshow/s390x (1.5.2-2 to 1.5.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: obs-text-slideshow/s390x obs-studio/s390x
• obs-transition-table/s390x (0.2.3+git20220221.d372847-1 to 0.2.3+git20220221.d372847-1)
  • Migration status for obs-transition-table/s390x (0.2.3+git20220221.d372847-1 to 0.2.3+git20220221.d372847-1): Will attempt migration (Any information below is purely informational)
    • Depends: obs-transition-table/s390x obs-studio/s390x
• ocaml-cohttp/amd64 (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/amd64 (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/amd64 js-of-ocaml/amd64 (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/amd64 openssl
• ocaml-cohttp/arm64 (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/arm64 (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/arm64 js-of-ocaml/arm64 (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/arm64 openssl
• ocaml-cohttp/armel (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/armel (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/armel js-of-ocaml/armel (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/armel openssl
• ocaml-cohttp/armhf (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/armhf (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/armhf js-of-ocaml/armhf (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/armhf openssl
• ocaml-cohttp/i386 (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/i386 (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/i386 js-of-ocaml/i386 (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/i386 openssl
• ocaml-cohttp/mips64el (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/mips64el (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/mips64el js-of-ocaml/mips64el (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/mips64el openssl
• ocaml-cohttp/mipsel (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/mipsel (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/mipsel js-of-ocaml/mipsel (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/mipsel openssl
• ocaml-cohttp/ppc64el (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/ppc64el (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/ppc64el js-of-ocaml/ppc64el (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/ppc64el openssl
• ocaml-cohttp/s390x (4.0.0-1 to 4.0.0-1)
  • Migration status for ocaml-cohttp/s390x (4.0.0-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-cohttp/s390x js-of-ocaml/s390x (not considered)
    • Invalidated by dependency
    • Depends: ocaml-cohttp/s390x openssl
• ocaml-logs/amd64 (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/amd64 (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/amd64 js-of-ocaml/amd64 (not considered)
    • Invalidated by dependency
• ocaml-logs/arm64 (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/arm64 (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/arm64 js-of-ocaml/arm64 (not considered)
    • Invalidated by dependency
• ocaml-logs/armel (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/armel (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/armel js-of-ocaml/armel (not considered)
    • Invalidated by dependency
• ocaml-logs/armhf (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/armhf (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/armhf js-of-ocaml/armhf (not considered)
    • Invalidated by dependency
• ocaml-logs/i386 (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/i386 (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/i386 js-of-ocaml/i386 (not considered)
    • Invalidated by dependency
• ocaml-logs/mips64el (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/mips64el (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/mips64el js-of-ocaml/mips64el (not considered)
    • Invalidated by dependency
• ocaml-logs/mipsel (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/mipsel (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/mipsel js-of-ocaml/mipsel (not considered)
    • Invalidated by dependency
• ocaml-logs/ppc64el (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/ppc64el (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/ppc64el js-of-ocaml/ppc64el (not considered)
    • Invalidated by dependency
• ocaml-logs/s390x (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-logs/s390x (0.7.0-2 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/s390x js-of-ocaml/s390x (not considered)
    • Invalidated by dependency
• ocaml-ssl/amd64 (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/amd64 (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/amd64 openssl
• ocaml-ssl/arm64 (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/arm64 (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/arm64 openssl
• ocaml-ssl/armel (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/armel (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/armel openssl
• ocaml-ssl/armhf (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/armhf (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/armhf openssl
• ocaml-ssl/i386 (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/i386 (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/i386 openssl
• ocaml-ssl/mips64el (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/mips64el (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/mips64el openssl
• ocaml-ssl/mipsel (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/mipsel (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/mipsel openssl
• ocaml-ssl/ppc64el (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/ppc64el (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/ppc64el openssl
• ocaml-ssl/s390x (0.5.10-1 to 0.5.10-1)
  • Migration status for ocaml-ssl/s390x (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocaml-ssl/s390x openssl
• ocsigenserver/amd64 (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/amd64 (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/amd64 openssl
• ocsigenserver/arm64 (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/arm64 (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/arm64 openssl
• ocsigenserver/armel (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/armel (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/armel openssl
• ocsigenserver/armhf (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/armhf (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/armhf openssl
• ocsigenserver/i386 (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/i386 (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/i386 openssl
• ocsigenserver/mips64el (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/mips64el (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/mips64el openssl
• ocsigenserver/mipsel (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/mipsel (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/mipsel openssl
• ocsigenserver/ppc64el (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/ppc64el (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/ppc64el openssl
• ocsigenserver/s390x (5.0.1-1 to 5.0.1-1)
  • Migration status for ocsigenserver/s390x (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: ocsigenserver/s390x openssl
• omniorb-dfsg/amd64 (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/amd64 (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/amd64 openssl
• omniorb-dfsg/arm64 (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/arm64 (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/arm64 openssl
• omniorb-dfsg/armel (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/armel (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/armel openssl
• omniorb-dfsg/armhf (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/armhf (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/armhf openssl
• omniorb-dfsg/i386 (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/i386 (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/i386 openssl
• omniorb-dfsg/mips64el (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/mips64el (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/mips64el openssl
• omniorb-dfsg/mipsel (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/mipsel (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/mipsel openssl
• omniorb-dfsg/ppc64el (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/ppc64el (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/ppc64el openssl
• omniorb-dfsg/s390x (4.2.5+ds1-1 to 4.2.5+ds1-1)
  • Migration status for omniorb-dfsg/s390x (4.2.5+ds1-1 to 4.2.5+ds1-1): Will attempt migration (Any information below is purely informational)
    • Depends: omniorb-dfsg/s390x openssl
• opa-ff/amd64 (10.10.3.0.11-1 to 10.10.3.0.11-1)
  • Migration status for opa-ff/amd64 (10.10.3.0.11-1 to 10.10.3.0.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: opa-ff/amd64 openssl
• opa-fm/amd64 (10.10.3.0.11-1 to 10.10.3.0.11-1)
  • Migration status for opa-fm/amd64 (10.10.3.0.11-1 to 10.10.3.0.11-1): Will attempt migration (Any information below is purely informational)
    • Depends: opa-fm/amd64 openssl
• open-iscsi/amd64 (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/amd64 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/amd64 openssl
• open-iscsi/arm64 (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/arm64 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/arm64 openssl
• open-iscsi/armel (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/armel (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/armel openssl
• open-iscsi/armhf (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/armhf (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/armhf openssl
• open-iscsi/i386 (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/i386 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/i386 openssl
• open-iscsi/mips64el (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/mips64el (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/mips64el openssl
• open-iscsi/mipsel (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/mipsel (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/mipsel openssl
• open-iscsi/ppc64el (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/ppc64el (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/ppc64el openssl
• open-iscsi/s390x (2.1.5-1 to 2.1.5-1)
  • Migration status for open-iscsi/s390x (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: open-iscsi/s390x openssl
• open-vm-tools/amd64 (2:12.0.0-2 to 2:12.0.0-2)
  • Migration status for open-vm-tools/amd64 (2:12.0.0-2 to 2:12.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: open-vm-tools/amd64 openssl
• open-vm-tools/arm64 (2:12.0.0-2 to 2:12.0.0-2)
  • Migration status for open-vm-tools/arm64 (2:12.0.0-2 to 2:12.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: open-vm-tools/arm64 openssl
• open-vm-tools/i386 (2:12.0.0-2 to 2:12.0.0-2)
  • Migration status for open-vm-tools/i386 (2:12.0.0-2 to 2:12.0.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: open-vm-tools/i386 openssl
• open3d/amd64 (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/amd64 (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/amd64 openssl
• open3d/arm64 (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/arm64 (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/arm64 openssl
• open3d/armhf (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/armhf (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/armhf openssl
• open3d/i386 (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/i386 (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/i386 openssl
• open3d/mipsel (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/mipsel (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/mipsel openssl
• open3d/ppc64el (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/ppc64el (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/ppc64el openssl
• open3d/s390x (0.15.1+ds-2 to 0.15.1+ds-2)
  • Migration status for open3d/s390x (0.15.1+ds-2 to 0.15.1+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: open3d/s390x openssl
• openboard/amd64 (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/amd64 (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/amd64 openssl
• openboard/arm64 (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/arm64 (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/arm64 openssl
• openboard/armhf (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/armhf (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/armhf openssl
• openboard/i386 (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/i386 (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/i386 openssl
• openboard/mips64el (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/mips64el (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/mips64el openssl
• openboard/mipsel (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/mipsel (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/mipsel openssl
• openboard/ppc64el (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/ppc64el (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/ppc64el openssl
• openboard/s390x (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1)
  • Migration status for openboard/s390x (1.6.1+dfsg2-1 to 1.6.1+dfsg2-1): Will attempt migration (Any information below is purely informational)
    • Depends: openboard/s390x openssl
• opencryptoki/amd64 (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/amd64 (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/amd64 openssl
• opencryptoki/arm64 (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/arm64 (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/arm64 openssl
• opencryptoki/armel (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/armel (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/armel openssl
• opencryptoki/armhf (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/armhf (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/armhf openssl
• opencryptoki/i386 (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/i386 (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/i386 openssl
• opencryptoki/mips64el (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/mips64el (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/mips64el openssl
• opencryptoki/mipsel (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/mipsel (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/mipsel openssl
• opencryptoki/ppc64el (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/ppc64el (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/ppc64el openssl
• opencryptoki/s390x (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2)
  • Migration status for opencryptoki/s390x (3.8.1+dfsg-3.2 to 3.8.1+dfsg-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: opencryptoki/s390x openssl
• opendht/amd64 (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/amd64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/amd64 openssl
• opendht/arm64 (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/arm64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/arm64 openssl
• opendht/armel (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/armel (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/armel openssl
• opendht/armhf (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/armhf (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/armhf openssl
• opendht/i386 (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/i386 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/i386 openssl
• opendht/mips64el (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/mips64el (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/mips64el openssl
• opendht/mipsel (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/mipsel (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/mipsel openssl
• opendht/ppc64el (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/ppc64el (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/ppc64el openssl
• opendht/s390x (2.3.1-1 to 2.3.1-1)
  • Migration status for opendht/s390x (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendht/s390x openssl
• opendkim/amd64 (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/amd64 (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/amd64 openssl
• opendkim/arm64 (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/arm64 (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/arm64 openssl
• opendkim/armel (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/armel (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/armel openssl
• opendkim/armhf (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/armhf (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/armhf openssl
• opendkim/i386 (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/i386 (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/i386 openssl
• opendkim/mips64el (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/mips64el (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/mips64el openssl
• opendkim/mipsel (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/mipsel (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/mipsel openssl
• opendkim/ppc64el (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/ppc64el (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/ppc64el openssl
• opendkim/s390x (2.11.0~beta2-6 to 2.11.0~beta2-6)
  • Migration status for opendkim/s390x (2.11.0~beta2-6 to 2.11.0~beta2-6): Will attempt migration (Any information below is purely informational)
    • Depends: opendkim/s390x openssl
• opendnssec/amd64 (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/amd64 (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/amd64 openssl
• opendnssec/arm64 (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/arm64 (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/arm64 openssl
• opendnssec/armel (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/armel (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/armel openssl
• opendnssec/armhf (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/armhf (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/armhf openssl
• opendnssec/i386 (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/i386 (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/i386 openssl
• opendnssec/mips64el (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/mips64el (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/mips64el openssl
• opendnssec/mipsel (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/mipsel (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/mipsel openssl
• opendnssec/ppc64el (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/ppc64el (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/ppc64el openssl
• opendnssec/s390x (1:2.1.10-1 to 1:2.1.10-1)
  • Migration status for opendnssec/s390x (1:2.1.10-1 to 1:2.1.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: opendnssec/s390x openssl
• openfortivpn/amd64 (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/amd64 (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/amd64 openssl
• openfortivpn/arm64 (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/arm64 (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/arm64 openssl
• openfortivpn/armel (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/armel (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/armel openssl
• openfortivpn/armhf (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/armhf (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/armhf openssl
• openfortivpn/i386 (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/i386 (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/i386 openssl
• openfortivpn/mips64el (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/mips64el (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/mips64el openssl
• openfortivpn/mipsel (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/mipsel (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/mipsel openssl
• openfortivpn/ppc64el (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/ppc64el (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/ppc64el openssl
• openfortivpn/s390x (1.17.1-1 to 1.17.1-1)
  • Migration status for openfortivpn/s390x (1.17.1-1 to 1.17.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openfortivpn/s390x openssl
• openhpi/amd64 (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/amd64 (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/amd64 openssl
• openhpi/arm64 (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/arm64 (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/arm64 openssl
• openhpi/armel (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/armel (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/armel openssl
• openhpi/armhf (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/armhf (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/armhf openssl
• openhpi/i386 (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/i386 (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/i386 openssl
• openhpi/mips64el (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/mips64el (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/mips64el openssl
• openhpi/mipsel (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/mipsel (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/mipsel openssl
• openhpi/ppc64el (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/ppc64el (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/ppc64el openssl
• openhpi/s390x (3.8.0-2.1 to 3.8.0-2.1)
  • Migration status for openhpi/s390x (3.8.0-2.1 to 3.8.0-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: openhpi/s390x openssl
• openipmi/amd64 (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/amd64 (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/amd64 openssl
• openipmi/arm64 (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/arm64 (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/arm64 openssl
• openipmi/armel (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/armel (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/armel openssl
• openipmi/armhf (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/armhf (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/armhf openssl
• openipmi/i386 (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/i386 (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/i386 openssl
• openipmi/mips64el (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/mips64el (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/mips64el openssl
• openipmi/mipsel (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/mipsel (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/mipsel openssl
• openipmi/ppc64el (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/ppc64el (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/ppc64el openssl
• openipmi/s390x (2.0.29-0.1 to 2.0.29-0.1)
  • Migration status for openipmi/s390x (2.0.29-0.1 to 2.0.29-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: openipmi/s390x openssl
• openjdk-17_pu (17.0.3+7-1 to 17.0.3+7-1~deb11u1)
  • Migration status for openjdk-17_pu (17.0.3+7-1 to 17.0.3+7-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openjdk-17 is newer in the target suite (17.0.3+7-1 17.0.3+7-1~deb11u1)
• openldap_pu (2.5.12+dfsg-2 to 2.4.57+dfsg-3+deb11u1)
  • Migration status for openldap_pu (2.5.12+dfsg-2 to 2.4.57+dfsg-3+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openldap is newer in the target suite (2.5.12+dfsg-2 2.4.57+dfsg-3+deb11u1)
• openrct2/amd64 (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/amd64 (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/amd64 openssl
• openrct2/arm64 (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/arm64 (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/arm64 openssl
• openrct2/armel (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/armel (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/armel openssl
• openrct2/armhf (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/armhf (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/armhf openssl
• openrct2/i386 (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/i386 (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/i386 openssl
• openrct2/mips64el (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/mips64el (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/mips64el openssl
• openrct2/mipsel (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/mipsel (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/mipsel openssl
• openrct2/ppc64el (0.4.0+ds-2 to 0.4.0+ds-2)
  • Migration status for openrct2/ppc64el (0.4.0+ds-2 to 0.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: openrct2/ppc64el openssl
• opensc/amd64 (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/amd64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/amd64 openssl
• opensc/arm64 (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/arm64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/arm64 openssl
• opensc/armel (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/armel (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/armel openssl
• opensc/armhf (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/armhf (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/armhf openssl
• opensc/i386 (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/i386 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/i386 openssl
• opensc/mips64el (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/mips64el (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/mips64el openssl
• opensc/mipsel (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/mipsel (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/mipsel openssl
• opensc/ppc64el (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/ppc64el (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/ppc64el openssl
• opensc/s390x (0.22.0-2 to 0.22.0-2)
  • Migration status for opensc/s390x (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: opensc/s390x openssl
• opensmtpd-filter-dkimsign/amd64 (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/amd64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/amd64 openssl
• opensmtpd-filter-dkimsign/arm64 (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/arm64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/arm64 openssl
• opensmtpd-filter-dkimsign/armel (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/armel (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/armel openssl
• opensmtpd-filter-dkimsign/armhf (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/armhf (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/armhf openssl
• opensmtpd-filter-dkimsign/i386 (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/i386 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/i386 openssl
• opensmtpd-filter-dkimsign/mips64el (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/mips64el (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/mips64el openssl
• opensmtpd-filter-dkimsign/mipsel (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/mipsel (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/mipsel openssl
• opensmtpd-filter-dkimsign/ppc64el (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/ppc64el (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/ppc64el openssl
• opensmtpd-filter-dkimsign/s390x (0.5-1 to 0.5-1)
  • Migration status for opensmtpd-filter-dkimsign/s390x (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd-filter-dkimsign/s390x openssl
• opensmtpd/amd64 (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/amd64 (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/amd64 openssl
• opensmtpd/arm64 (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/arm64 (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/arm64 openssl
• opensmtpd/armel (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/armel (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/armel openssl
• opensmtpd/armhf (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/armhf (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/armhf openssl
• opensmtpd/i386 (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/i386 (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/i386 openssl
• opensmtpd/mips64el (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/mips64el (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/mips64el openssl
• opensmtpd/mipsel (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/mipsel (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/mipsel openssl
• opensmtpd/ppc64el (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/ppc64el (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/ppc64el openssl
• opensmtpd/s390x (6.8.0p2-4 to 6.8.0p2-4)
  • Migration status for opensmtpd/s390x (6.8.0p2-4 to 6.8.0p2-4): Will attempt migration (Any information below is purely informational)
    • Depends: opensmtpd/s390x openssl
• openssh-ssh1/amd64 (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/amd64 (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/amd64 openssl
• openssh-ssh1/arm64 (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/arm64 (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/arm64 openssl
• openssh-ssh1/armel (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/armel (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/armel openssl
• openssh-ssh1/armhf (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/armhf (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/armhf openssl
• openssh-ssh1/i386 (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/i386 (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/i386 openssl
• openssh-ssh1/mips64el (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/mips64el (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/mips64el openssl
• openssh-ssh1/mipsel (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/mipsel (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/mipsel openssl
• openssh-ssh1/ppc64el (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/ppc64el (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/ppc64el openssl
• openssh-ssh1/s390x (1:7.5p1-13 to 1:7.5p1-13)
  • Migration status for openssh-ssh1/s390x (1:7.5p1-13 to 1:7.5p1-13): Will attempt migration (Any information below is purely informational)
    • Depends: openssh-ssh1/s390x openssl
• openssh/amd64 (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/amd64 (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/amd64 openssl
• openssh/arm64 (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/arm64 (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/arm64 openssl
• openssh/armel (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/armel (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/armel openssl
• openssh/armhf (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/armhf (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/armhf openssl
• openssh/i386 (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/i386 (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/i386 openssl
• openssh/mips64el (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/mips64el (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/mips64el openssl
• openssh/mipsel (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/mipsel (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/mipsel openssl
• openssh/ppc64el (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/ppc64el (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/ppc64el openssl
• openssh/s390x (1:9.0p1-1 to 1:9.0p1-1)
  • Migration status for openssh/s390x (1:9.0p1-1 to 1:9.0p1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssh/s390x openssl
• openssl-ibmca/s390x (1.4.0-1 to 1.4.0-1)
  • Migration status for openssl-ibmca/s390x (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: openssl-ibmca/s390x openssl
• openssl_pu (1.1.1o-1 to 1.1.1n-0+deb11u2)
  • Migration status for openssl_pu (1.1.1o-1 to 1.1.1n-0+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openssl is newer in the target suite (1.1.1o-1 1.1.1n-0+deb11u2)
• openvswitch/amd64 (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/amd64 (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/amd64 openssl
• openvswitch/arm64 (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/arm64 (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/arm64 openssl
• openvswitch/armel (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/armel (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/armel openssl
• openvswitch/armhf (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/armhf (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/armhf openssl
• openvswitch/i386 (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/i386 (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/i386 openssl
• openvswitch/mips64el (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/mips64el (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/mips64el openssl
• openvswitch/mipsel (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/mipsel (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/mipsel openssl
• openvswitch/ppc64el (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/ppc64el (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/ppc64el openssl
• openvswitch/s390x (2.15.0+ds1-10 to 2.15.0+ds1-10)
  • Migration status for openvswitch/s390x (2.15.0+ds1-10 to 2.15.0+ds1-10): Will attempt migration (Any information below is purely informational)
    • Depends: openvswitch/s390x openssl
• ophcrack/amd64 (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/amd64 (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/amd64 openssl
• ophcrack/arm64 (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/arm64 (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/arm64 openssl
• ophcrack/armel (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/armel (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/armel openssl
• ophcrack/armhf (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/armhf (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/armhf openssl
• ophcrack/i386 (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/i386 (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/i386 openssl
• ophcrack/mips64el (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/mips64el (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/mips64el openssl
• ophcrack/mipsel (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/mipsel (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/mipsel openssl
• ophcrack/ppc64el (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/ppc64el (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/ppc64el openssl
• ophcrack/s390x (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/s390x (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: ophcrack/s390x openssl
• orca_pu (42.1-2 to 3.38.2-2)
  • Migration status for orca_pu (42.1-2 to 3.38.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: orca is newer in the target suite (42.1-2 3.38.2-2)
• orthanc-gdcm/amd64 (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/amd64 (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/amd64 dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/amd64 orthanc
• orthanc-gdcm/arm64 (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/arm64 (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/arm64 dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/arm64 orthanc
• orthanc-gdcm/armel (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/armel (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/armel dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/armel orthanc
• orthanc-gdcm/armhf (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/armhf (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/armhf dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/armhf orthanc
• orthanc-gdcm/i386 (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/i386 (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/i386 dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/i386 orthanc
• orthanc-gdcm/mips64el (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/mips64el (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/mips64el dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/mips64el orthanc
• orthanc-gdcm/mipsel (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/mipsel (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/mipsel dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/mipsel orthanc
• orthanc-gdcm/ppc64el (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/ppc64el (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/ppc64el dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/ppc64el orthanc
• orthanc-gdcm/s390x (1.5-1 to 1.5-1)
  • Migration status for orthanc-gdcm/s390x (1.5-1 to 1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-gdcm/s390x dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-gdcm/s390x orthanc
• orthanc-mysql/amd64 (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/amd64 (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/amd64 dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/amd64 orthanc
• orthanc-mysql/arm64 (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/arm64 (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/arm64 dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/arm64 orthanc
• orthanc-mysql/armel (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/armel (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/armel dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/armel orthanc
• orthanc-mysql/armhf (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/armhf (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/armhf dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/armhf orthanc
• orthanc-mysql/i386 (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/i386 (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/i386 dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/i386 orthanc
• orthanc-mysql/mips64el (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/mips64el (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/mips64el dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/mips64el orthanc
• orthanc-mysql/mipsel (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/mipsel (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/mipsel dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/mipsel orthanc
• orthanc-mysql/ppc64el (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/ppc64el (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/ppc64el dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/ppc64el orthanc
• orthanc-mysql/s390x (4.3-3 to 4.3-3)
  • Migration status for orthanc-mysql/s390x (4.3-3 to 4.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-mysql/s390x dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-mysql/s390x orthanc
• osptoolkit/amd64 (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/amd64 (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/amd64 openssl
• osptoolkit/arm64 (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/arm64 (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/arm64 openssl
• osptoolkit/armel (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/armel (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/armel openssl
• osptoolkit/armhf (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/armhf (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/armhf openssl
• osptoolkit/i386 (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/i386 (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/i386 openssl
• osptoolkit/mips64el (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/mips64el (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/mips64el openssl
• osptoolkit/mipsel (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/mipsel (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/mipsel openssl
• osptoolkit/ppc64el (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/ppc64el (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/ppc64el openssl
• osptoolkit/s390x (4.13.0-1 to 4.13.0-1)
  • Migration status for osptoolkit/s390x (4.13.0-1 to 4.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osptoolkit/s390x openssl
• osslsigncode/amd64 (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/amd64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/amd64 openssl
• osslsigncode/arm64 (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/arm64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/arm64 openssl
• osslsigncode/armel (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/armel (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/armel openssl
• osslsigncode/armhf (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/armhf (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/armhf openssl
• osslsigncode/i386 (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/i386 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/i386 openssl
• osslsigncode/mips64el (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/mips64el (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/mips64el openssl
• osslsigncode/mipsel (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/mipsel (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/mipsel openssl
• osslsigncode/ppc64el (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/ppc64el (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/ppc64el openssl
• osslsigncode/s390x (2.3.0-1 to 2.3.0-1)
  • Migration status for osslsigncode/s390x (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: osslsigncode/s390x openssl
• paho.mqtt.c/amd64 (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/amd64 (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/amd64 openssl
• paho.mqtt.c/arm64 (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/arm64 (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/arm64 openssl
• paho.mqtt.c/armel (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/armel (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/armel openssl
• paho.mqtt.c/armhf (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/armhf (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/armhf openssl
• paho.mqtt.c/i386 (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/i386 (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/i386 openssl
• paho.mqtt.c/mips64el (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/mips64el (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/mips64el openssl
• paho.mqtt.c/mipsel (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/mipsel (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/mipsel openssl
• paho.mqtt.c/ppc64el (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/ppc64el (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/ppc64el openssl
• paho.mqtt.c/s390x (1.3.9-1 to 1.3.9-1)
  • Migration status for paho.mqtt.c/s390x (1.3.9-1 to 1.3.9-1): Will attempt migration (Any information below is purely informational)
    • Depends: paho.mqtt.c/s390x openssl
• pam-mysql/amd64 (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/amd64 (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/amd64 openssl
• pam-mysql/arm64 (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/arm64 (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/arm64 openssl
• pam-mysql/armel (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/armel (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/armel openssl
• pam-mysql/armhf (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/armhf (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/armhf openssl
• pam-mysql/i386 (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/i386 (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/i386 openssl
• pam-mysql/mips64el (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/mips64el (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/mips64el openssl
• pam-mysql/mipsel (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/mipsel (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/mipsel openssl
• pam-mysql/ppc64el (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/ppc64el (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/ppc64el openssl
• pam-mysql/s390x (0.8.1-5 to 0.8.1-5)
  • Migration status for pam-mysql/s390x (0.8.1-5 to 0.8.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: pam-mysql/s390x openssl
• pam-pkcs11/amd64 (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/amd64 (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/amd64 openssl
• pam-pkcs11/arm64 (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/arm64 (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/arm64 openssl
• pam-pkcs11/armel (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/armel (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/armel openssl
• pam-pkcs11/armhf (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/armhf (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/armhf openssl
• pam-pkcs11/i386 (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/i386 (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/i386 openssl
• pam-pkcs11/mips64el (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/mips64el (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/mips64el openssl
• pam-pkcs11/mipsel (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/mipsel (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/mipsel openssl
• pam-pkcs11/ppc64el (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/ppc64el (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/ppc64el openssl
• pam-pkcs11/s390x (0.6.11-4 to 0.6.11-4)
  • Migration status for pam-pkcs11/s390x (0.6.11-4 to 0.6.11-4): Will attempt migration (Any information below is purely informational)
    • Depends: pam-pkcs11/s390x openssl
• pam-ssh-agent-auth/amd64 (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/amd64 (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/amd64 openssl
• pam-ssh-agent-auth/arm64 (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/arm64 (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/arm64 openssl
• pam-ssh-agent-auth/armel (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/armel (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/armel openssl
• pam-ssh-agent-auth/armhf (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/armhf (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/armhf openssl
• pam-ssh-agent-auth/i386 (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/i386 (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/i386 openssl
• pam-ssh-agent-auth/mips64el (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/mips64el (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/mips64el openssl
• pam-ssh-agent-auth/mipsel (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/mipsel (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/mipsel openssl
• pam-ssh-agent-auth/ppc64el (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/ppc64el (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/ppc64el openssl
• pam-ssh-agent-auth/s390x (0.10.3-3.1 to 0.10.3-3.1)
  • Migration status for pam-ssh-agent-auth/s390x (0.10.3-3.1 to 0.10.3-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-ssh-agent-auth/s390x openssl
• pam-u2f/amd64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/amd64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/amd64 openssl
• pam-u2f/arm64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/arm64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/arm64 openssl
• pam-u2f/armel (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/armel (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/armel openssl
• pam-u2f/armhf (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/armhf (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/armhf openssl
• pam-u2f/i386 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/i386 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/i386 openssl
• pam-u2f/mips64el (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/mips64el (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/mips64el openssl
• pam-u2f/mipsel (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/mipsel (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/mipsel openssl
• pam-u2f/ppc64el (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/ppc64el (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/ppc64el openssl
• pam-u2f/s390x (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for pam-u2f/s390x (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-u2f/s390x openssl
• partclone/amd64 (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/amd64 (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/amd64 openssl
• partclone/arm64 (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/arm64 (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/arm64 openssl
• partclone/armel (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/armel (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/armel openssl
• partclone/armhf (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/armhf (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/armhf openssl
• partclone/i386 (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/i386 (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/i386 openssl
• partclone/mips64el (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/mips64el (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/mips64el openssl
• partclone/mipsel (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/mipsel (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/mipsel openssl
• partclone/ppc64el (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/ppc64el (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/ppc64el openssl
• partclone/s390x (0.3.20+repack-1 to 0.3.20+repack-1)
  • Migration status for partclone/s390x (0.3.20+repack-1 to 0.3.20+repack-1): Will attempt migration (Any information below is purely informational)
    • Depends: partclone/s390x openssl
• partimage/amd64 (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/amd64 (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/amd64 openssl
• partimage/arm64 (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/arm64 (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/arm64 openssl
• partimage/armel (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/armel (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/armel openssl
• partimage/armhf (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/armhf (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/armhf openssl
• partimage/i386 (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/i386 (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/i386 openssl
• partimage/mips64el (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/mips64el (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/mips64el openssl
• partimage/mipsel (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/mipsel (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/mipsel openssl
• partimage/ppc64el (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/ppc64el (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/ppc64el openssl
• partimage/s390x (0.6.9-8 to 0.6.9-8)
  • Migration status for partimage/s390x (0.6.9-8 to 0.6.9-8): Will attempt migration (Any information below is purely informational)
    • Depends: partimage/s390x openssl
• pcp/amd64 (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/amd64 (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/amd64 openssl
• pcp/arm64 (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/arm64 (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/arm64 openssl
• pcp/armel (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/armel (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/armel openssl
• pcp/armhf (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/armhf (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/armhf openssl
• pcp/i386 (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/i386 (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/i386 openssl
• pcp/mips64el (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/mips64el (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/mips64el openssl
• pcp/mipsel (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/mipsel (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/mipsel openssl
• pcp/ppc64el (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/ppc64el (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/ppc64el openssl
• pcp/s390x (5.3.7-1 to 5.3.7-1)
  • Migration status for pcp/s390x (5.3.7-1 to 5.3.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: pcp/s390x openssl
• pdns/amd64 (4.6.2-1 to 4.6.2-1)
  • Migration status for pdns/amd64 (4.6.2-1 to 4.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: pdns/amd64 openssl
• pdns/arm64 (4.6.2-1 to 4.6.2-1)
  • Migration status for pdns/arm64 (4.6.2-1 to 4.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: pdns/arm64 openssl
• pdns/mips64el (4.6.2-1 to 4.6.2-1)
  • Migration status for pdns/mips64el (4.6.2-1 to 4.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: pdns/mips64el openssl
• pdns/ppc64el (4.6.2-1 to 4.6.2-1)
  • Migration status for pdns/ppc64el (4.6.2-1 to 4.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: pdns/ppc64el openssl
• pdns/s390x (4.6.2-1 to 4.6.2-1)
  • Migration status for pdns/s390x (4.6.2-1 to 4.6.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: pdns/s390x openssl
• pen/amd64 (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/amd64 (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/amd64 openssl
• pen/arm64 (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/arm64 (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/arm64 openssl
• pen/armel (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/armel (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/armel openssl
• pen/armhf (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/armhf (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/armhf openssl
• pen/i386 (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/i386 (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/i386 openssl
• pen/mips64el (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/mips64el (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/mips64el openssl
• pen/mipsel (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/mipsel (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/mipsel openssl
• pen/ppc64el (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/ppc64el (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/ppc64el openssl
• pen/s390x (0.34.1-2 to 0.34.1-2)
  • Migration status for pen/s390x (0.34.1-2 to 0.34.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: pen/s390x openssl
• peony/amd64 (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/amd64 (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/amd64 openssl
• peony/arm64 (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/arm64 (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/arm64 openssl
• peony/armel (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/armel (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/armel openssl
• peony/armhf (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/armhf (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/armhf openssl
• peony/i386 (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/i386 (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/i386 openssl
• peony/mips64el (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/mips64el (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/mips64el openssl
• peony/mipsel (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/mipsel (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/mipsel openssl
• peony/ppc64el (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/ppc64el (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/ppc64el openssl
• peony/s390x (3.2.4-2 to 3.2.4-2)
  • Migration status for peony/s390x (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: peony/s390x openssl
• perdition/amd64 (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/amd64 (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/amd64 openssl
• perdition/arm64 (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/arm64 (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/arm64 openssl
• perdition/armel (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/armel (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/armel openssl
• perdition/armhf (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/armhf (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/armhf openssl
• perdition/i386 (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/i386 (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/i386 openssl
• perdition/mips64el (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/mips64el (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/mips64el openssl
• perdition/mipsel (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/mipsel (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/mipsel openssl
• perdition/ppc64el (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/ppc64el (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/ppc64el openssl
• perdition/s390x (2.2-3.2 to 2.2-3.2)
  • Migration status for perdition/s390x (2.2-3.2 to 2.2-3.2): Will attempt migration (Any information below is purely informational)
    • Depends: perdition/s390x openssl
• perl-openssl-defaults/amd64 (7 to 7)
  • Migration status for perl-openssl-defaults/amd64 (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/amd64 openssl
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-openssl-bignum-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-openssl-dsa-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-openssl-pkcs10-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-openssl-rsa-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-openssl-x509-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-smime-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libcrypt-ssleay-perl/amd64
    • Implicit dependency: perl-openssl-defaults/amd64 libnet-ssleay-perl
• perl-openssl-defaults/arm64 (7 to 7)
  • Migration status for perl-openssl-defaults/arm64 (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/arm64 openssl
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-openssl-bignum-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-openssl-dsa-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-openssl-pkcs10-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-openssl-rsa-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-openssl-x509-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-smime-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libcrypt-ssleay-perl/arm64
    • Implicit dependency: perl-openssl-defaults/arm64 libnet-ssleay-perl
• perl-openssl-defaults/armel (7 to 7)
  • Migration status for perl-openssl-defaults/armel (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/armel openssl
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-openssl-bignum-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-openssl-dsa-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-openssl-pkcs10-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-openssl-rsa-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-openssl-x509-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-smime-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libcrypt-ssleay-perl/armel
    • Implicit dependency: perl-openssl-defaults/armel libnet-ssleay-perl
• perl-openssl-defaults/armhf (7 to 7)
  • Migration status for perl-openssl-defaults/armhf (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/armhf openssl
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-openssl-bignum-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-openssl-dsa-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-openssl-pkcs10-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-openssl-rsa-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-openssl-x509-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-smime-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libcrypt-ssleay-perl/armhf
    • Implicit dependency: perl-openssl-defaults/armhf libnet-ssleay-perl
• perl-openssl-defaults/i386 (7 to 7)
  • Migration status for perl-openssl-defaults/i386 (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/i386 openssl
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-openssl-bignum-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-openssl-dsa-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-openssl-pkcs10-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-openssl-rsa-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-openssl-x509-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-smime-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libcrypt-ssleay-perl/i386
    • Implicit dependency: perl-openssl-defaults/i386 libnet-ssleay-perl
• perl-openssl-defaults/mips64el (7 to 7)
  • Migration status for perl-openssl-defaults/mips64el (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/mips64el openssl
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-openssl-bignum-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-openssl-dsa-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-openssl-pkcs10-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-openssl-rsa-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-openssl-x509-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-smime-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libcrypt-ssleay-perl/mips64el
    • Implicit dependency: perl-openssl-defaults/mips64el libnet-ssleay-perl
• perl-openssl-defaults/mipsel (7 to 7)
  • Migration status for perl-openssl-defaults/mipsel (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/mipsel openssl
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-openssl-bignum-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-openssl-dsa-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-openssl-pkcs10-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-openssl-rsa-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-openssl-x509-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-smime-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libcrypt-ssleay-perl/mipsel
    • Implicit dependency: perl-openssl-defaults/mipsel libnet-ssleay-perl
• perl-openssl-defaults/ppc64el (7 to 7)
  • Migration status for perl-openssl-defaults/ppc64el (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/ppc64el openssl
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-openssl-bignum-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-openssl-dsa-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-openssl-pkcs10-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-openssl-rsa-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-openssl-x509-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-smime-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libcrypt-ssleay-perl/ppc64el
    • Implicit dependency: perl-openssl-defaults/ppc64el libnet-ssleay-perl
• perl-openssl-defaults/s390x (7 to 7)
  • Migration status for perl-openssl-defaults/s390x (7 to 7): Will attempt migration (Any information below is purely informational)
    • Depends: perl-openssl-defaults/s390x openssl
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-openssl-bignum-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-openssl-dsa-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-openssl-pkcs10-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-openssl-rsa-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-openssl-x509-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-smime-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libcrypt-ssleay-perl/s390x
    • Implicit dependency: perl-openssl-defaults/s390x libnet-ssleay-perl
• pev/amd64 (0.81-7 to 0.81-7)
  • Migration status for pev/amd64 (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/amd64 openssl
• pev/arm64 (0.81-7 to 0.81-7)
  • Migration status for pev/arm64 (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/arm64 openssl
• pev/armel (0.81-7 to 0.81-7)
  • Migration status for pev/armel (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/armel openssl
• pev/armhf (0.81-7 to 0.81-7)
  • Migration status for pev/armhf (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/armhf openssl
• pev/i386 (0.81-7 to 0.81-7)
  • Migration status for pev/i386 (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/i386 openssl
• pev/mips64el (0.81-7 to 0.81-7)
  • Migration status for pev/mips64el (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/mips64el openssl
• pev/mipsel (0.81-7 to 0.81-7)
  • Migration status for pev/mipsel (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/mipsel openssl
• pev/ppc64el (0.81-7 to 0.81-7)
  • Migration status for pev/ppc64el (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/ppc64el openssl
• pev/s390x (0.81-7 to 0.81-7)
  • Migration status for pev/s390x (0.81-7 to 0.81-7): Will attempt migration (Any information below is purely informational)
    • Depends: pev/s390x openssl
• pgbackrest/amd64 (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/amd64 (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/amd64 openssl
• pgbackrest/arm64 (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/arm64 (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/arm64 openssl
• pgbackrest/armel (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/armel (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/armel openssl
• pgbackrest/armhf (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/armhf (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/armhf openssl
• pgbackrest/i386 (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/i386 (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/i386 openssl
• pgbackrest/mips64el (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/mips64el (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/mips64el openssl
• pgbackrest/mipsel (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/mipsel (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/mipsel openssl
• pgbackrest/ppc64el (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/ppc64el (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/ppc64el openssl
• pgbackrest/s390x (2.37-1 to 2.37-1)
  • Migration status for pgbackrest/s390x (2.37-1 to 2.37-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgbackrest/s390x openssl
• pgbouncer/amd64 (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/amd64 (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/amd64 openssl
• pgbouncer/arm64 (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/arm64 (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/arm64 openssl
• pgbouncer/armel (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/armel (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/armel openssl
• pgbouncer/armhf (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/armhf (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/armhf openssl
• pgbouncer/i386 (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/i386 (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/i386 openssl
• pgbouncer/mips64el (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/mips64el (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/mips64el openssl
• pgbouncer/mipsel (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/mipsel (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/mipsel openssl
• pgbouncer/ppc64el (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/ppc64el (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/ppc64el openssl
• pgbouncer/s390x (1.17.0-3 to 1.17.0-3)
  • Migration status for pgbouncer/s390x (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: pgbouncer/s390x openssl
• pgloader/amd64 (3.6.3-1 to 3.6.3-1)
  • Migration status for pgloader/amd64 (3.6.3-1 to 3.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgloader/amd64 openssl
• pgloader/arm64 (3.6.3-1 to 3.6.3-1)
  • Migration status for pgloader/arm64 (3.6.3-1 to 3.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgloader/arm64 openssl
• pgloader/armel (3.6.3-1 to 3.6.3-1)
  • Migration status for pgloader/armel (3.6.3-1 to 3.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgloader/armel openssl
• pgloader/armhf (3.6.3-1 to 3.6.3-1)
  • Migration status for pgloader/armhf (3.6.3-1 to 3.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgloader/armhf openssl
• pgloader/i386 (3.6.3-1 to 3.6.3-1)
  • Migration status for pgloader/i386 (3.6.3-1 to 3.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgloader/i386 openssl
• pgloader/ppc64el (3.6.3-1 to 3.6.3-1)
  • Migration status for pgloader/ppc64el (3.6.3-1 to 3.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgloader/ppc64el openssl
• php-guzzlehttp-psr7_pu (1.8.5-1 to 1.7.0-1+deb11u1)
  • Migration status for php-guzzlehttp-psr7_pu (1.8.5-1 to 1.7.0-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: php-guzzlehttp-psr7 is newer in the target suite (1.8.5-1 1.7.0-1+deb11u1)
• php-mongodb/amd64 (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/amd64 (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/amd64 openssl
• php-mongodb/arm64 (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/arm64 (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/arm64 openssl
• php-mongodb/armel (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/armel (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/armel openssl
• php-mongodb/armhf (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/armhf (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/armhf openssl
• php-mongodb/i386 (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/i386 (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/i386 openssl
• php-mongodb/mips64el (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/mips64el (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/mips64el openssl
• php-mongodb/mipsel (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/mipsel (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/mipsel openssl
• php-mongodb/ppc64el (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/ppc64el (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/ppc64el openssl
• php-mongodb/s390x (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4)
  • Migration status for php-mongodb/s390x (1.12.0+1.9.2+1.7.5-4 to 1.12.0+1.9.2+1.7.5-4): Will attempt migration (Any information below is purely informational)
    • Depends: php-mongodb/s390x openssl
• php-pecl-http/amd64 (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/amd64 (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/amd64 openssl
• php-pecl-http/arm64 (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/arm64 (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/arm64 openssl
• php-pecl-http/armel (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/armel (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/armel openssl
• php-pecl-http/armhf (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/armhf (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/armhf openssl
• php-pecl-http/i386 (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/i386 (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/i386 openssl
• php-pecl-http/mips64el (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/mips64el (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/mips64el openssl
• php-pecl-http/mipsel (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/mipsel (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/mipsel openssl
• php-pecl-http/ppc64el (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/ppc64el (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/ppc64el openssl
• php-pecl-http/s390x (4.2.2-1 to 4.2.2-1)
  • Migration status for php-pecl-http/s390x (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: php-pecl-http/s390x openssl
• php-twig_pu (3.4.1-1 to 2.14.3-1+deb11u1)
  • Migration status for php-twig_pu (3.4.1-1 to 2.14.3-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: php-twig is newer in the target suite (3.4.1-1 2.14.3-1+deb11u1)
• php8.1/amd64 (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/amd64 (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/amd64 openssl
• php8.1/arm64 (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/arm64 (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/arm64 openssl
• php8.1/armel (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/armel (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/armel openssl
• php8.1/armhf (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/armhf (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/armhf openssl
• php8.1/i386 (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/i386 (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/i386 openssl
• php8.1/mips64el (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/mips64el (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/mips64el openssl
• php8.1/mipsel (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/mipsel (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/mipsel openssl
• php8.1/ppc64el (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/ppc64el (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/ppc64el openssl
• php8.1/s390x (8.1.5-1 to 8.1.5-1)
  • Migration status for php8.1/s390x (8.1.5-1 to 8.1.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: php8.1/s390x openssl
• picolisp/amd64 (22.3-1 to 22.3-1)
  • Migration status for picolisp/amd64 (22.3-1 to 22.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: picolisp/amd64 openssl
• picolisp/arm64 (22.3-1 to 22.3-1)
  • Migration status for picolisp/arm64 (22.3-1 to 22.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: picolisp/arm64 openssl
• picolisp/mips64el (22.3-1 to 22.3-1)
  • Migration status for picolisp/mips64el (22.3-1 to 22.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: picolisp/mips64el openssl
• picolisp/ppc64el (22.3-1 to 22.3-1)
  • Migration status for picolisp/ppc64el (22.3-1 to 22.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: picolisp/ppc64el openssl
• picolisp/s390x (22.3-1 to 22.3-1)
  • Migration status for picolisp/s390x (22.3-1 to 22.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: picolisp/s390x openssl
• pinot/amd64 (1.21-1 to 1.21-1)
  • Migration status for pinot/amd64 (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/amd64 openssl
• pinot/arm64 (1.21-1 to 1.21-1)
  • Migration status for pinot/arm64 (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/arm64 openssl
• pinot/armel (1.21-1 to 1.21-1)
  • Migration status for pinot/armel (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/armel openssl
• pinot/armhf (1.21-1 to 1.21-1)
  • Migration status for pinot/armhf (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/armhf openssl
• pinot/i386 (1.21-1 to 1.21-1)
  • Migration status for pinot/i386 (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/i386 openssl
• pinot/mips64el (1.21-1 to 1.21-1)
  • Migration status for pinot/mips64el (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/mips64el openssl
• pinot/mipsel (1.21-1 to 1.21-1)
  • Migration status for pinot/mipsel (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/mipsel openssl
• pinot/ppc64el (1.21-1 to 1.21-1)
  • Migration status for pinot/ppc64el (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/ppc64el openssl
• pinot/s390x (1.21-1 to 1.21-1)
  • Migration status for pinot/s390x (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/s390x openssl
• pkcs11-dump/amd64 (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/amd64 (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/amd64 openssl
• pkcs11-dump/arm64 (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/arm64 (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/arm64 openssl
• pkcs11-dump/armel (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/armel (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/armel openssl
• pkcs11-dump/armhf (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/armhf (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/armhf openssl
• pkcs11-dump/i386 (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/i386 (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/i386 openssl
• pkcs11-dump/mips64el (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/mips64el (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/mips64el openssl
• pkcs11-dump/mipsel (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/mipsel (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/mipsel openssl
• pkcs11-dump/ppc64el (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/ppc64el (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/ppc64el openssl
• pkcs11-dump/s390x (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/s390x (0.3.4-1.1 to 0.3.4-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-dump/s390x openssl
• pkcs11-helper/amd64 (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/amd64 (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/amd64 openssl
• pkcs11-helper/arm64 (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/arm64 (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/arm64 openssl
• pkcs11-helper/armel (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/armel (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/armel openssl
• pkcs11-helper/armhf (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/armhf (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/armhf openssl
• pkcs11-helper/i386 (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/i386 (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/i386 openssl
• pkcs11-helper/mips64el (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/mips64el (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/mips64el openssl
• pkcs11-helper/mipsel (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/mipsel (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/mipsel openssl
• pkcs11-helper/ppc64el (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/ppc64el (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/ppc64el openssl
• pkcs11-helper/s390x (1.28-1 to 1.28-1)
  • Migration status for pkcs11-helper/s390x (1.28-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Depends: pkcs11-helper/s390x openssl
• poco/amd64 (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/amd64 (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/amd64 openssl
• poco/arm64 (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/arm64 (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/arm64 openssl
• poco/armel (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/armel (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/armel openssl
• poco/armhf (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/armhf (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/armhf openssl
• poco/i386 (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/i386 (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/i386 openssl
• poco/mips64el (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/mips64el (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/mips64el openssl
• poco/mipsel (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/mipsel (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/mipsel openssl
• poco/ppc64el (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/ppc64el (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/ppc64el openssl
• poco/s390x (1.11.0-3 to 1.11.0-3)
  • Migration status for poco/s390x (1.11.0-3 to 1.11.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: poco/s390x openssl
• polyphone/amd64 (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/amd64 (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/amd64 openssl
• polyphone/arm64 (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/arm64 (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/arm64 openssl
• polyphone/armel (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/armel (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/armel openssl
• polyphone/armhf (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/armhf (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/armhf openssl
• polyphone/i386 (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/i386 (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/i386 openssl
• polyphone/mips64el (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/mips64el (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/mips64el openssl
• polyphone/mipsel (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/mipsel (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/mipsel openssl
• polyphone/ppc64el (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2)
  • Migration status for polyphone/ppc64el (2.2.0.20210109+dfsg1-2 to 2.2.0.20210109+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: polyphone/ppc64el openssl
• postfix/amd64 (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/amd64 (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/amd64 openssl
• postfix/arm64 (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/arm64 (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/arm64 openssl
• postfix/armel (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/armel (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/armel openssl
• postfix/armhf (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/armhf (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/armhf openssl
• postfix/i386 (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/i386 (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/i386 openssl
• postfix/mips64el (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/mips64el (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/mips64el openssl
• postfix/mipsel (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/mipsel (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/mipsel openssl
• postfix/ppc64el (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/ppc64el (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/ppc64el openssl
• postfix/s390x (3.6.4-1 to 3.6.4-1)
  • Migration status for postfix/s390x (3.6.4-1 to 3.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: postfix/s390x openssl
• postfix_pu (3.6.4-1 to 3.5.13-0+deb11u1)
  • Migration status for postfix_pu (3.6.4-1 to 3.5.13-0+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: postfix is newer in the target suite (3.6.4-1 3.5.13-0+deb11u1)
• postgresql-13_pu (- to 13.7-0+deb11u1)
  • Migration status for postgresql-13_pu (- to 13.7-0+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/amd64
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/arm64
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/armel
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/armhf
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/i386
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/mips64el
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/mipsel
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/ppc64el
    • Impossible Depends: postgresql-13_pu -> libicu67/67.1-7/s390x
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/amd64
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/arm64
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/armel
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/i386
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/mips64el
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/ppc64el
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/s390x
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.59+dfsg-1+b1/amd64
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.59+dfsg-1+b1/armel
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.59+dfsg-1+b1/armhf
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.59+dfsg-1+b1/mips64el
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.59+dfsg-1+b1/mipsel
    • Impossible Depends: postgresql-13_pu -> libldap-2.4-2/2.4.59+dfsg-1+b1/s390x
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/amd64
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/arm64
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/armel
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/armhf
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/i386
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/mips64el
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/mipsel
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/ppc64el
    • Impossible Depends: postgresql-13_pu -> libperl5.32/5.32.1-6/s390x
    • NEEDS APPROVAL BY RM
• postgresql-14/amd64 (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/amd64 (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/amd64 openssl
• postgresql-14/arm64 (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/arm64 (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/arm64 openssl
• postgresql-14/armel (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/armel (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/armel openssl
• postgresql-14/armhf (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/armhf (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/armhf openssl
• postgresql-14/i386 (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/i386 (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/i386 openssl
• postgresql-14/mips64el (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/mips64el (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/mips64el openssl
• postgresql-14/mipsel (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/mipsel (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/mipsel openssl
• postgresql-14/ppc64el (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/ppc64el (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/ppc64el openssl
• postgresql-14/s390x (14.3-1 to 14.3-1)
  • Migration status for postgresql-14/s390x (14.3-1 to 14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: postgresql-14/s390x openssl
• ppp/amd64 (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/amd64 (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/amd64 openssl
• ppp/arm64 (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/arm64 (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/arm64 openssl
• ppp/armel (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/armel (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/armel openssl
• ppp/armhf (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/armhf (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/armhf openssl
• ppp/i386 (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/i386 (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/i386 openssl
• ppp/mips64el (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/mips64el (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/mips64el openssl
• ppp/mipsel (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/mipsel (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/mipsel openssl
• ppp/ppc64el (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/ppc64el (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/ppc64el openssl
• ppp/s390x (2.4.9-1+1.1 to 2.4.9-1+1.1)
  • Migration status for ppp/s390x (2.4.9-1+1.1 to 2.4.9-1+1.1): Will attempt migration (Any information below is purely informational)
    • Depends: ppp/s390x openssl
• proxytunnel/amd64 (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/amd64 (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/amd64 openssl
• proxytunnel/arm64 (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/arm64 (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/arm64 openssl
• proxytunnel/armel (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/armel (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/armel openssl
• proxytunnel/armhf (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/armhf (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/armhf openssl
• proxytunnel/i386 (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/i386 (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/i386 openssl
• proxytunnel/mips64el (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/mips64el (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/mips64el openssl
• proxytunnel/mipsel (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/mipsel (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/mipsel openssl
• proxytunnel/ppc64el (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/ppc64el (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/ppc64el openssl
• proxytunnel/s390x (1.10.20210604-1 to 1.10.20210604-1)
  • Migration status for proxytunnel/s390x (1.10.20210604-1 to 1.10.20210604-1): Will attempt migration (Any information below is purely informational)
    • Depends: proxytunnel/s390x openssl
• psi-plus/amd64 (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/amd64 (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/amd64 openssl
• psi-plus/arm64 (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/arm64 (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/arm64 openssl
• psi-plus/armel (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/armel (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/armel openssl
• psi-plus/armhf (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/armhf (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/armhf openssl
• psi-plus/i386 (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/i386 (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/i386 openssl
• psi-plus/mips64el (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/mips64el (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/mips64el openssl
• psi-plus/mipsel (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/mipsel (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/mipsel openssl
• psi-plus/ppc64el (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/ppc64el (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/ppc64el openssl
• psi-plus/s390x (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/s390x (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
    • Depends: psi-plus/s390x openssl
• pulseaudio/amd64 (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/amd64 (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/amd64 openssl
• pulseaudio/arm64 (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/arm64 (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/arm64 openssl
• pulseaudio/armel (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/armel (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/armel openssl
• pulseaudio/armhf (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/armhf (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/armhf openssl
• pulseaudio/i386 (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/i386 (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/i386 openssl
• pulseaudio/mips64el (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/mips64el (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/mips64el openssl
• pulseaudio/mipsel (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/mipsel (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/mipsel openssl
• pulseaudio/ppc64el (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/ppc64el (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/ppc64el openssl
• pulseaudio/s390x (15.0+dfsg1-4 to 15.0+dfsg1-4)
  • Migration status for pulseaudio/s390x (15.0+dfsg1-4 to 15.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
    • Depends: pulseaudio/s390x openssl
• pure-ftpd/amd64 (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/amd64 (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/amd64 openssl
• pure-ftpd/arm64 (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/arm64 (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/arm64 openssl
• pure-ftpd/armel (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/armel (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/armel openssl
• pure-ftpd/armhf (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/armhf (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/armhf openssl
• pure-ftpd/i386 (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/i386 (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/i386 openssl
• pure-ftpd/mips64el (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/mips64el (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/mips64el openssl
• pure-ftpd/mipsel (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/mipsel (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/mipsel openssl
• pure-ftpd/ppc64el (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/ppc64el (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/ppc64el openssl
• pure-ftpd/s390x (1.0.50-2.1 to 1.0.50-2.1)
  • Migration status for pure-ftpd/s390x (1.0.50-2.1 to 1.0.50-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pure-ftpd/s390x openssl
• python-scrapy_pu (2.6.1-1 to 2.4.1-2+deb11u1)
  • Migration status for python-scrapy_pu (2.6.1-1 to 2.4.1-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: python-scrapy is newer in the target suite (2.6.1-1 2.4.1-2+deb11u1)
• python-scrypt/amd64 (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/amd64 (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/amd64 openssl
• python-scrypt/arm64 (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/arm64 (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/arm64 openssl
• python-scrypt/armel (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/armel (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/armel openssl
• python-scrypt/armhf (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/armhf (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/armhf openssl
• python-scrypt/i386 (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/i386 (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/i386 openssl
• python-scrypt/mips64el (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/mips64el (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/mips64el openssl
• python-scrypt/mipsel (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/mipsel (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/mipsel openssl
• python-scrypt/ppc64el (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/ppc64el (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/ppc64el openssl
• python-scrypt/s390x (0.8.20-1 to 0.8.20-1)
  • Migration status for python-scrypt/s390x (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: python-scrypt/s390x openssl
• qca2/amd64 (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/amd64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/amd64 openssl
• qca2/arm64 (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/arm64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/arm64 openssl
• qca2/armel (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/armel (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/armel openssl
• qca2/armhf (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/armhf (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/armhf openssl
• qca2/i386 (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/i386 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/i386 openssl
• qca2/mips64el (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/mips64el (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/mips64el openssl
• qca2/mipsel (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/mipsel (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/mipsel openssl
• qca2/ppc64el (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/ppc64el (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/ppc64el openssl
• qca2/s390x (2.3.4-1 to 2.3.4-1)
  • Migration status for qca2/s390x (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: qca2/s390x openssl
• qcalcfilehash/amd64 (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/amd64 (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/amd64 openssl
• qcalcfilehash/arm64 (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/arm64 (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/arm64 openssl
• qcalcfilehash/armel (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/armel (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/armel openssl
• qcalcfilehash/armhf (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/armhf (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/armhf openssl
• qcalcfilehash/i386 (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/i386 (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/i386 openssl
• qcalcfilehash/mips64el (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/mips64el (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/mips64el openssl
• qcalcfilehash/mipsel (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/mipsel (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/mipsel openssl
• qcalcfilehash/ppc64el (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/ppc64el (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/ppc64el openssl
• qcalcfilehash/s390x (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3)
  • Migration status for qcalcfilehash/s390x (1.0.7+git20200816.1eb8770-3 to 1.0.7+git20200816.1eb8770-3): Will attempt migration (Any information below is purely informational)
    • Depends: qcalcfilehash/s390x openssl
• qemu_pu (1:7.0+dfsg-7 to 1:5.2+dfsg-11+deb11u2)
  • Migration status for qemu_pu (1:7.0+dfsg-7 to 1:5.2+dfsg-11+deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: qemu is newer in the target suite (1:7.0+dfsg-7 1:5.2+dfsg-11+deb11u2)
• qtbase-opensource-src/amd64 (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/amd64 (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/amd64 openssl
• qtbase-opensource-src/arm64 (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/arm64 (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/arm64 openssl
• qtbase-opensource-src/armel (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/armel (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/armel openssl
• qtbase-opensource-src/armhf (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/armhf (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/armhf openssl
• qtbase-opensource-src/i386 (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/i386 (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/i386 openssl
• qtbase-opensource-src/mips64el (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/mips64el (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/mips64el openssl
• qtbase-opensource-src/mipsel (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/mipsel (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/mipsel openssl
• qtbase-opensource-src/ppc64el (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/ppc64el (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/ppc64el openssl
• qtbase-opensource-src/s390x (5.15.2+dfsg-16 to 5.15.2+dfsg-16)
  • Migration status for qtbase-opensource-src/s390x (5.15.2+dfsg-16 to 5.15.2+dfsg-16): Will attempt migration (Any information below is purely informational)
    • Depends: qtbase-opensource-src/s390x openssl
• qterm/amd64 (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/amd64 (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/amd64 openssl
• qterm/arm64 (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/arm64 (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/arm64 openssl
• qterm/armel (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/armel (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/armel openssl
• qterm/armhf (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/armhf (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/armhf openssl
• qterm/i386 (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/i386 (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/i386 openssl
• qterm/mips64el (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/mips64el (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/mips64el openssl
• qterm/mipsel (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/mipsel (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/mipsel openssl
• qterm/ppc64el (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/ppc64el (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/ppc64el openssl
• qterm/s390x (1:0.7.4-2 to 1:0.7.4-2)
  • Migration status for qterm/s390x (1:0.7.4-2 to 1:0.7.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: qterm/s390x openssl
• quickfix/amd64 (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/amd64 (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/amd64 openssl
• quickfix/arm64 (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/arm64 (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/arm64 openssl
• quickfix/armel (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/armel (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/armel openssl
• quickfix/armhf (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/armhf (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/armhf openssl
• quickfix/i386 (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/i386 (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/i386 openssl
• quickfix/mips64el (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/mips64el (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/mips64el openssl
• quickfix/mipsel (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/mipsel (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/mipsel openssl
• quickfix/ppc64el (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/ppc64el (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/ppc64el openssl
• quickfix/s390x (1.15.1+dfsg-4 to 1.15.1+dfsg-4)
  • Migration status for quickfix/s390x (1.15.1+dfsg-4 to 1.15.1+dfsg-4): Will attempt migration (Any information below is purely informational)
    • Depends: quickfix/s390x openssl
• r-cran-git2r/amd64 (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/amd64 (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/amd64 openssl
• r-cran-git2r/arm64 (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/arm64 (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/arm64 openssl
• r-cran-git2r/armel (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/armel (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/armel openssl
• r-cran-git2r/armhf (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/armhf (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/armhf openssl
• r-cran-git2r/i386 (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/i386 (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/i386 openssl
• r-cran-git2r/mips64el (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/mips64el (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/mips64el openssl
• r-cran-git2r/mipsel (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/mipsel (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/mipsel openssl
• r-cran-git2r/ppc64el (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/ppc64el (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/ppc64el openssl
• r-cran-git2r/s390x (0.30.1-1 to 0.30.1-1)
  • Migration status for r-cran-git2r/s390x (0.30.1-1 to 0.30.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-git2r/s390x openssl
• r-cran-pki/amd64 (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/amd64 (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/amd64 openssl
• r-cran-pki/arm64 (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/arm64 (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/arm64 openssl
• r-cran-pki/armel (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/armel (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/armel openssl
• r-cran-pki/armhf (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/armhf (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/armhf openssl
• r-cran-pki/i386 (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/i386 (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/i386 openssl
• r-cran-pki/mips64el (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/mips64el (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/mips64el openssl
• r-cran-pki/mipsel (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/mipsel (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/mipsel openssl
• r-cran-pki/ppc64el (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/ppc64el (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/ppc64el openssl
• r-cran-pki/s390x (0.1-11-1 to 0.1-11-1)
  • Migration status for r-cran-pki/s390x (0.1-11-1 to 0.1-11-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-pki/s390x openssl
• r-cran-rsclient/amd64 (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/amd64 (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/amd64 openssl
• r-cran-rsclient/arm64 (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/arm64 (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/arm64 openssl
• r-cran-rsclient/armel (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/armel (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/armel openssl
• r-cran-rsclient/armhf (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/armhf (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/armhf openssl
• r-cran-rsclient/i386 (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/i386 (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/i386 openssl
• r-cran-rsclient/mips64el (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/mips64el (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/mips64el openssl
• r-cran-rsclient/mipsel (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/mipsel (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/mipsel openssl
• r-cran-rsclient/ppc64el (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/ppc64el (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/ppc64el openssl
• r-cran-rsclient/s390x (0.7-8-1 to 0.7-8-1)
  • Migration status for r-cran-rsclient/s390x (0.7-8-1 to 0.7-8-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-rsclient/s390x openssl
• r-cran-s2/amd64 (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/amd64 (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/amd64 openssl
• r-cran-s2/arm64 (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/arm64 (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/arm64 openssl
• r-cran-s2/armel (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/armel (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/armel openssl
• r-cran-s2/armhf (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/armhf (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/armhf openssl
• r-cran-s2/i386 (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/i386 (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/i386 openssl
• r-cran-s2/mips64el (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/mips64el (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/mips64el openssl
• r-cran-s2/mipsel (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/mipsel (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/mipsel openssl
• r-cran-s2/ppc64el (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/ppc64el (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/ppc64el openssl
• r-cran-s2/s390x (1.0.7-3 to 1.0.7-3)
  • Migration status for r-cran-s2/s390x (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-s2/s390x openssl
• radsecproxy/amd64 (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/amd64 (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/amd64 openssl
• radsecproxy/arm64 (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/arm64 (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/arm64 openssl
• radsecproxy/armel (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/armel (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/armel openssl
• radsecproxy/armhf (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/armhf (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/armhf openssl
• radsecproxy/i386 (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/i386 (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/i386 openssl
• radsecproxy/mips64el (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/mips64el (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/mips64el openssl
• radsecproxy/mipsel (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/mipsel (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/mipsel openssl
• radsecproxy/ppc64el (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/ppc64el (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/ppc64el openssl
• radsecproxy/s390x (1.9.1-1 to 1.9.1-1)
  • Migration status for radsecproxy/s390x (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: radsecproxy/s390x openssl
• rauc/amd64 (1.6-1 to 1.6-1)
  • Migration status for rauc/amd64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/amd64 openssl
• rauc/arm64 (1.6-1 to 1.6-1)
  • Migration status for rauc/arm64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/arm64 openssl
• rauc/armel (1.6-1 to 1.6-1)
  • Migration status for rauc/armel (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/armel openssl
• rauc/armhf (1.6-1 to 1.6-1)
  • Migration status for rauc/armhf (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/armhf openssl
• rauc/i386 (1.6-1 to 1.6-1)
  • Migration status for rauc/i386 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/i386 openssl
• rauc/mips64el (1.6-1 to 1.6-1)
  • Migration status for rauc/mips64el (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/mips64el openssl
• rauc/mipsel (1.6-1 to 1.6-1)
  • Migration status for rauc/mipsel (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/mipsel openssl
• rauc/ppc64el (1.6-1 to 1.6-1)
  • Migration status for rauc/ppc64el (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/ppc64el openssl
• rauc/s390x (1.6-1 to 1.6-1)
  • Migration status for rauc/s390x (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: rauc/s390x openssl
• ros-ros-comm/amd64 (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/amd64 (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/amd64 openssl
• ros-ros-comm/arm64 (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/arm64 (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/arm64 openssl
• ros-ros-comm/armel (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/armel (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/armel openssl
• ros-ros-comm/armhf (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/armhf (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/armhf openssl
• ros-ros-comm/i386 (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/i386 (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/i386 openssl
• ros-ros-comm/mips64el (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/mips64el (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/mips64el openssl
• ros-ros-comm/mipsel (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/mipsel (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/mipsel openssl
• ros-ros-comm/ppc64el (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/ppc64el (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/ppc64el openssl
• ros-ros-comm/s390x (1.15.14+ds-2 to 1.15.14+ds-2)
  • Migration status for ros-ros-comm/s390x (1.15.14+ds-2 to 1.15.14+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: ros-ros-comm/s390x openssl
• rpki-client/amd64 (7.8-1 to 7.8-1)
  • Migration status for rpki-client/amd64 (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/amd64 libretls
    • Depends: rpki-client/amd64 openssl
• rpki-client/arm64 (7.8-1 to 7.8-1)
  • Migration status for rpki-client/arm64 (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/arm64 libretls
    • Depends: rpki-client/arm64 openssl
• rpki-client/armel (7.8-1 to 7.8-1)
  • Migration status for rpki-client/armel (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/armel libretls
    • Depends: rpki-client/armel openssl
• rpki-client/armhf (7.8-1 to 7.8-1)
  • Migration status for rpki-client/armhf (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/armhf libretls
    • Depends: rpki-client/armhf openssl
• rpki-client/i386 (7.8-1 to 7.8-1)
  • Migration status for rpki-client/i386 (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/i386 libretls
    • Depends: rpki-client/i386 openssl
• rpki-client/mips64el (7.8-1 to 7.8-1)
  • Migration status for rpki-client/mips64el (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/mips64el libretls
    • Depends: rpki-client/mips64el openssl
• rpki-client/mipsel (7.8-1 to 7.8-1)
  • Migration status for rpki-client/mipsel (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/mipsel libretls
    • Depends: rpki-client/mipsel openssl
• rpki-client/ppc64el (7.8-1 to 7.8-1)
  • Migration status for rpki-client/ppc64el (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/ppc64el libretls
    • Depends: rpki-client/ppc64el openssl
• rpki-client/s390x (7.8-1 to 7.8-1)
  • Migration status for rpki-client/s390x (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: rpki-client/s390x libretls
    • Depends: rpki-client/s390x openssl
• rserve/amd64 (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/amd64 (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/amd64 openssl
• rserve/arm64 (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/arm64 (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/arm64 openssl
• rserve/armel (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/armel (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/armel openssl
• rserve/armhf (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/armhf (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/armhf openssl
• rserve/i386 (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/i386 (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/i386 openssl
• rserve/mips64el (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/mips64el (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/mips64el openssl
• rserve/mipsel (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/mipsel (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/mipsel openssl
• rserve/ppc64el (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/ppc64el (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/ppc64el openssl
• rserve/s390x (1.8-10-1 to 1.8-10-1)
  • Migration status for rserve/s390x (1.8-10-1 to 1.8-10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rserve/s390x openssl
• rsync/amd64 (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/amd64 (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/amd64 openssl
• rsync/arm64 (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/arm64 (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/arm64 openssl
• rsync/armel (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/armel (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/armel openssl
• rsync/armhf (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/armhf (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/armhf openssl
• rsync/i386 (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/i386 (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/i386 openssl
• rsync/mips64el (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/mips64el (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/mips64el openssl
• rsync/mipsel (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/mipsel (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/mipsel openssl
• rsync/ppc64el (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/ppc64el (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/ppc64el openssl
• rsync/s390x (3.2.4-1 to 3.2.4-1)
  • Migration status for rsync/s390x (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsync/s390x openssl
• rsyncrypto/amd64 (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/amd64 (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/amd64 openssl
• rsyncrypto/arm64 (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/arm64 (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/arm64 openssl
• rsyncrypto/armel (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/armel (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/armel openssl
• rsyncrypto/armhf (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/armhf (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/armhf openssl
• rsyncrypto/i386 (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/i386 (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/i386 openssl
• rsyncrypto/mips64el (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/mips64el (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/mips64el openssl
• rsyncrypto/mipsel (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/mipsel (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/mipsel openssl
• rsyncrypto/ppc64el (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/ppc64el (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/ppc64el openssl
• rsyncrypto/s390x (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/s390x (1.14-1.2 to 1.14-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: rsyncrypto/s390x openssl
• rsyslog/amd64 (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/amd64 (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/amd64 openssl
• rsyslog/arm64 (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/arm64 (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/arm64 openssl
• rsyslog/armel (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/armel (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/armel openssl
• rsyslog/armhf (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/armhf (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/armhf openssl
• rsyslog/i386 (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/i386 (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/i386 openssl
• rsyslog/mips64el (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/mips64el (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/mips64el openssl
• rsyslog/mipsel (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/mipsel (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/mipsel openssl
• rsyslog/ppc64el (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/ppc64el (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/ppc64el openssl
• rsyslog/s390x (8.2204.1-1 to 8.2204.1-1)
  • Migration status for rsyslog/s390x (8.2204.1-1 to 8.2204.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: rsyslog/s390x openssl
• rsyslog_pu (8.2204.1-1 to 8.2102.0-2+deb11u1)
  • Migration status for rsyslog_pu (8.2204.1-1 to 8.2102.0-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: rsyslog is newer in the target suite (8.2204.1-1 8.2102.0-2+deb11u1)
• ruby-eventmachine/amd64 (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/amd64 (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/amd64 openssl
• ruby-eventmachine/arm64 (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/arm64 (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/arm64 openssl
• ruby-eventmachine/armel (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/armel (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/armel openssl
• ruby-eventmachine/armhf (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/armhf (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/armhf openssl
• ruby-eventmachine/i386 (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/i386 (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/i386 openssl
• ruby-eventmachine/mips64el (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/mips64el (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/mips64el openssl
• ruby-eventmachine/mipsel (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/mipsel (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/mipsel openssl
• ruby-eventmachine/ppc64el (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/ppc64el (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/ppc64el openssl
• ruby-eventmachine/s390x (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5)
  • Migration status for ruby-eventmachine/s390x (1.3~pre20201020-b50c135-5 to 1.3~pre20201020-b50c135-5): Will attempt migration (Any information below is purely informational)
    • Depends: ruby-eventmachine/s390x openssl
• ruby-net-ssh_pu (1:7.0.0~beta1-2 to 1:6.1.0-2+deb11u1)
  • Migration status for ruby-net-ssh_pu (1:7.0.0~beta1-2 to 1:6.1.0-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ruby-net-ssh is newer in the target suite (1:7.0.0~beta1-2 1:6.1.0-2+deb11u1)
• rust-debcargo/amd64 (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/amd64 (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/amd64 rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/amd64 openssl
• rust-debcargo/arm64 (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/arm64 (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/arm64 rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/arm64 openssl
• rust-debcargo/armel (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/armel (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/armel rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/armel openssl
• rust-debcargo/armhf (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/armhf (2.5.0-3 to 2.5.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: rust-debcargo/armhf openssl
• rust-debcargo/i386 (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/i386 (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/i386 rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/i386 openssl
• rust-debcargo/mips64el (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/mips64el (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/mips64el rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/mips64el openssl
• rust-debcargo/mipsel (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/mipsel (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/mipsel rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/mipsel openssl
• rust-debcargo/ppc64el (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/ppc64el (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/ppc64el rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/ppc64el openssl
• rust-debcargo/s390x (2.5.0-3 to 2.5.0-3)
  • Migration status for rust-debcargo/s390x (2.5.0-3 to 2.5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-debcargo/s390x rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-debcargo/s390x openssl
• s-nail/amd64 (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/amd64 (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/amd64 openssl
• s-nail/arm64 (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/arm64 (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/arm64 openssl
• s-nail/armel (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/armel (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/armel openssl
• s-nail/armhf (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/armhf (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/armhf openssl
• s-nail/i386 (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/i386 (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/i386 openssl
• s-nail/mips64el (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/mips64el (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/mips64el openssl
• s-nail/mipsel (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/mipsel (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/mipsel openssl
• s-nail/ppc64el (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/ppc64el (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/ppc64el openssl
• s-nail/s390x (14.9.24-1 to 14.9.24-1)
  • Migration status for s-nail/s390x (14.9.24-1 to 14.9.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: s-nail/s390x openssl
• s3backer/amd64 (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/amd64 (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/amd64 openssl
• s3backer/arm64 (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/arm64 (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/arm64 openssl
• s3backer/armel (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/armel (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/armel openssl
• s3backer/armhf (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/armhf (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/armhf openssl
• s3backer/i386 (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/i386 (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/i386 openssl
• s3backer/mips64el (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/mips64el (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/mips64el openssl
• s3backer/mipsel (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/mipsel (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/mipsel openssl
• s3backer/ppc64el (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/ppc64el (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/ppc64el openssl
• s3backer/s390x (1.5.4-2 to 1.5.4-2)
  • Migration status for s3backer/s390x (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: s3backer/s390x openssl
• sacc/amd64 (1.05-1 to 1.05-1)
  • Migration status for sacc/amd64 (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/amd64 libretls
• sacc/arm64 (1.05-1 to 1.05-1)
  • Migration status for sacc/arm64 (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/arm64 libretls
• sacc/armel (1.05-1 to 1.05-1)
  • Migration status for sacc/armel (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/armel libretls
• sacc/armhf (1.05-1 to 1.05-1)
  • Migration status for sacc/armhf (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/armhf libretls
• sacc/i386 (1.05-1 to 1.05-1)
  • Migration status for sacc/i386 (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/i386 libretls
• sacc/mips64el (1.05-1 to 1.05-1)
  • Migration status for sacc/mips64el (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/mips64el libretls
• sacc/mipsel (1.05-1 to 1.05-1)
  • Migration status for sacc/mipsel (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/mipsel libretls
• sacc/ppc64el (1.05-1 to 1.05-1)
  • Migration status for sacc/ppc64el (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/ppc64el libretls
• sacc/s390x (1.05-1 to 1.05-1)
  • Migration status for sacc/s390x (1.05-1 to 1.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: sacc/s390x libretls
• sachesi/amd64 (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/amd64 (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/amd64 openssl
• sachesi/arm64 (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/arm64 (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/arm64 openssl
• sachesi/armel (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/armel (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/armel openssl
• sachesi/armhf (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/armhf (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/armhf openssl
• sachesi/i386 (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/i386 (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/i386 openssl
• sachesi/mips64el (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/mips64el (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/mips64el openssl
• sachesi/mipsel (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/mipsel (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/mipsel openssl
• sachesi/ppc64el (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/ppc64el (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/ppc64el openssl
• sachesi/s390x (2.0.4+ds-6 to 2.0.4+ds-6)
  • Migration status for sachesi/s390x (2.0.4+ds-6 to 2.0.4+ds-6): Will attempt migration (Any information below is purely informational)
    • Depends: sachesi/s390x openssl
• samba_pu (2:4.16.1+dfsg-8 to 2:4.13.13+dfsg-1~deb11u4)
  • Migration status for samba_pu (2:4.16.1+dfsg-8 to 2:4.13.13+dfsg-1~deb11u4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: samba is newer in the target suite (2:4.16.1+dfsg-8 2:4.13.13+dfsg-1~deb11u4)
• samdump2/amd64 (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/amd64 (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/amd64 openssl
• samdump2/arm64 (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/arm64 (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/arm64 openssl
• samdump2/armel (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/armel (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/armel openssl
• samdump2/armhf (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/armhf (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/armhf openssl
• samdump2/i386 (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/i386 (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/i386 openssl
• samdump2/mips64el (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/mips64el (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/mips64el openssl
• samdump2/mipsel (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/mipsel (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/mipsel openssl
• samdump2/ppc64el (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/ppc64el (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/ppc64el openssl
• samdump2/s390x (3.0.0-7 to 3.0.0-7)
  • Migration status for samdump2/s390x (3.0.0-7 to 3.0.0-7): Will attempt migration (Any information below is purely informational)
    • Depends: samdump2/s390x openssl
• scitokens-cpp/amd64 (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/amd64 (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/amd64 openssl
• scitokens-cpp/arm64 (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/arm64 (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/arm64 openssl
• scitokens-cpp/armel (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/armel (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/armel openssl
• scitokens-cpp/armhf (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/armhf (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/armhf openssl
• scitokens-cpp/i386 (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/i386 (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/i386 openssl
• scitokens-cpp/mips64el (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/mips64el (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/mips64el openssl
• scitokens-cpp/mipsel (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/mipsel (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/mipsel openssl
• scitokens-cpp/ppc64el (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/ppc64el (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/ppc64el openssl
• scitokens-cpp/s390x (0.7.0-2 to 0.7.0-2)
  • Migration status for scitokens-cpp/s390x (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: scitokens-cpp/s390x openssl
• scrypt/amd64 (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/amd64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/amd64 openssl
• scrypt/arm64 (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/arm64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/arm64 openssl
• scrypt/armel (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/armel (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/armel openssl
• scrypt/armhf (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/armhf (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/armhf openssl
• scrypt/i386 (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/i386 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/i386 openssl
• scrypt/mips64el (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/mips64el (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/mips64el openssl
• scrypt/mipsel (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/mipsel (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/mipsel openssl
• scrypt/ppc64el (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/ppc64el (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/ppc64el openssl
• scrypt/s390x (1.3.1-2 to 1.3.1-2)
  • Migration status for scrypt/s390x (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: scrypt/s390x openssl
• shairport-sync/amd64 (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/amd64 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/amd64 openssl
• shairport-sync/arm64 (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/arm64 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/arm64 openssl
• shairport-sync/armel (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/armel (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/armel openssl
• shairport-sync/armhf (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/armhf (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/armhf openssl
• shairport-sync/i386 (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/i386 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/i386 openssl
• shairport-sync/mips64el (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/mips64el (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/mips64el openssl
• shairport-sync/mipsel (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/mipsel (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/mipsel openssl
• shairport-sync/ppc64el (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/ppc64el (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/ppc64el openssl
• shairport-sync/s390x (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/s390x (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: shairport-sync/s390x openssl
• shellinabox/amd64 (2.21 to 2.21)
  • Migration status for shellinabox/amd64 (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/amd64 openssl
• shellinabox/arm64 (2.21 to 2.21)
  • Migration status for shellinabox/arm64 (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/arm64 openssl
• shellinabox/armel (2.21 to 2.21)
  • Migration status for shellinabox/armel (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/armel openssl
• shellinabox/armhf (2.21 to 2.21)
  • Migration status for shellinabox/armhf (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/armhf openssl
• shellinabox/i386 (2.21 to 2.21)
  • Migration status for shellinabox/i386 (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/i386 openssl
• shellinabox/mips64el (2.21 to 2.21)
  • Migration status for shellinabox/mips64el (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/mips64el openssl
• shellinabox/mipsel (2.21 to 2.21)
  • Migration status for shellinabox/mipsel (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/mipsel openssl
• shellinabox/ppc64el (2.21 to 2.21)
  • Migration status for shellinabox/ppc64el (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/ppc64el openssl
• shellinabox/s390x (2.21 to 2.21)
  • Migration status for shellinabox/s390x (2.21 to 2.21): Will attempt migration (Any information below is purely informational)
    • Depends: shellinabox/s390x openssl
• siege/amd64 (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/amd64 (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/amd64 openssl
• siege/arm64 (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/arm64 (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/arm64 openssl
• siege/armel (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/armel (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/armel openssl
• siege/armhf (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/armhf (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/armhf openssl
• siege/i386 (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/i386 (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/i386 openssl
• siege/mips64el (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/mips64el (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/mips64el openssl
• siege/mipsel (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/mipsel (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/mipsel openssl
• siege/ppc64el (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/ppc64el (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/ppc64el openssl
• siege/s390x (4.0.7-1 to 4.0.7-1)
  • Migration status for siege/s390x (4.0.7-1 to 4.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: siege/s390x openssl
• sight/amd64 (21.0.0-4 to 21.0.0-4)
  • Migration status for sight/amd64 (21.0.0-4 to 21.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sight/amd64 dcmtk (not considered)
    • Invalidated by dependency
    • Depends: sight/amd64 openssl
• simple-tpm-pk11/amd64 (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/amd64 (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/amd64 openssl
• simple-tpm-pk11/arm64 (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/arm64 (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/arm64 openssl
• simple-tpm-pk11/armel (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/armel (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/armel openssl
• simple-tpm-pk11/armhf (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/armhf (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/armhf openssl
• simple-tpm-pk11/i386 (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/i386 (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/i386 openssl
• simple-tpm-pk11/mips64el (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/mips64el (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/mips64el openssl
• simple-tpm-pk11/mipsel (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/mipsel (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/mipsel openssl
• simple-tpm-pk11/ppc64el (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/ppc64el (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/ppc64el openssl
• simple-tpm-pk11/s390x (0.06-4 to 0.06-4)
  • Migration status for simple-tpm-pk11/s390x (0.06-4 to 0.06-4): Will attempt migration (Any information below is purely informational)
    • Depends: simple-tpm-pk11/s390x openssl
• sipcrack/amd64 (0.2-4 to 0.2-4)
  • Migration status for sipcrack/amd64 (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/amd64 openssl
• sipcrack/arm64 (0.2-4 to 0.2-4)
  • Migration status for sipcrack/arm64 (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/arm64 openssl
• sipcrack/armel (0.2-4 to 0.2-4)
  • Migration status for sipcrack/armel (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/armel openssl
• sipcrack/armhf (0.2-4 to 0.2-4)
  • Migration status for sipcrack/armhf (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/armhf openssl
• sipcrack/i386 (0.2-4 to 0.2-4)
  • Migration status for sipcrack/i386 (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/i386 openssl
• sipcrack/mips64el (0.2-4 to 0.2-4)
  • Migration status for sipcrack/mips64el (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/mips64el openssl
• sipcrack/mipsel (0.2-4 to 0.2-4)
  • Migration status for sipcrack/mipsel (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/mipsel openssl
• sipcrack/ppc64el (0.2-4 to 0.2-4)
  • Migration status for sipcrack/ppc64el (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/ppc64el openssl
• sipcrack/s390x (0.2-4 to 0.2-4)
  • Migration status for sipcrack/s390x (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
    • Depends: sipcrack/s390x openssl
• slowhttptest/amd64 (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/amd64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/amd64 openssl
• slowhttptest/arm64 (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/arm64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/arm64 openssl
• slowhttptest/armel (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/armel (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/armel openssl
• slowhttptest/armhf (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/armhf (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/armhf openssl
• slowhttptest/i386 (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/i386 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/i386 openssl
• slowhttptest/mips64el (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/mips64el (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/mips64el openssl
• slowhttptest/mipsel (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/mipsel (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/mipsel openssl
• slowhttptest/ppc64el (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/ppc64el (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/ppc64el openssl
• slowhttptest/s390x (1.8.2-1 to 1.8.2-1)
  • Migration status for slowhttptest/s390x (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: slowhttptest/s390x openssl
• slrn/amd64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/amd64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/amd64 openssl
• slrn/arm64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/arm64 (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/arm64 openssl
• slrn/armel (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/armel (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/armel openssl
• slrn/armhf (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/armhf (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/armhf openssl
• slrn/i386 (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/i386 (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/i386 openssl
• slrn/mips64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/mips64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/mips64el openssl
• slrn/mipsel (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/mipsel (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/mipsel openssl
• slrn/ppc64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/ppc64el (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/ppc64el openssl
• slrn/s390x (1.0.3+dfsg-6 to 1.0.3+dfsg-6)
  • Migration status for slrn/s390x (1.0.3+dfsg-6 to 1.0.3+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: slrn/s390x openssl
• smartdns/amd64 (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/amd64 (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/amd64 openssl
• smartdns/arm64 (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/arm64 (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/arm64 openssl
• smartdns/armel (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/armel (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/armel openssl
• smartdns/armhf (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/armhf (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/armhf openssl
• smartdns/i386 (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/i386 (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/i386 openssl
• smartdns/mips64el (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/mips64el (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/mips64el openssl
• smartdns/mipsel (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/mipsel (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/mipsel openssl
• smartdns/ppc64el (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/ppc64el (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/ppc64el openssl
• smartdns/s390x (36.1+dfsg-1 to 36.1+dfsg-1)
  • Migration status for smartdns/s390x (36.1+dfsg-1 to 36.1+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: smartdns/s390x openssl
• smarty3_pu (3.1.45-1 to 3.1.39-2+deb11u1)
  • Migration status for smarty3_pu (3.1.45-1 to 3.1.39-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: smarty3 is newer in the target suite (3.1.45-1 3.1.39-2+deb11u1)
• socat/amd64 (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/amd64 (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/amd64 openssl
• socat/arm64 (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/arm64 (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/arm64 openssl
• socat/armel (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/armel (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/armel openssl
• socat/armhf (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/armhf (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/armhf openssl
• socat/i386 (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/i386 (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/i386 openssl
• socat/mips64el (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/mips64el (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/mips64el openssl
• socat/mipsel (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/mipsel (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/mipsel openssl
• socat/ppc64el (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/ppc64el (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/ppc64el openssl
• socat/s390x (1.7.4.3-3 to 1.7.4.3-3)
  • Migration status for socat/s390x (1.7.4.3-3 to 1.7.4.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: socat/s390x openssl
• softether-vpn/amd64 (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/amd64 (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/amd64 openssl
• softether-vpn/arm64 (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/arm64 (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/arm64 openssl
• softether-vpn/armel (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/armel (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/armel openssl
• softether-vpn/armhf (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/armhf (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/armhf openssl
• softether-vpn/i386 (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/i386 (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/i386 openssl
• softether-vpn/mips64el (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/mips64el (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/mips64el openssl
• softether-vpn/mipsel (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/mipsel (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/mipsel openssl
• softether-vpn/ppc64el (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/ppc64el (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/ppc64el openssl
• softether-vpn/s390x (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2)
  • Migration status for softether-vpn/s390x (5.01.9674+git20200806+8181039+dfsg2-2 to 5.01.9674+git20200806+8181039+dfsg2-2): Will attempt migration (Any information below is purely informational)
    • Depends: softether-vpn/s390x openssl
• sope/amd64 (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/amd64 (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/amd64 openssl
• sope/arm64 (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/arm64 (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/arm64 openssl
• sope/armel (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/armel (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/armel openssl
• sope/armhf (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/armhf (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/armhf openssl
• sope/i386 (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/i386 (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/i386 openssl
• sope/mips64el (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/mips64el (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/mips64el openssl
• sope/mipsel (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/mipsel (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/mipsel openssl
• sope/ppc64el (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/ppc64el (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/ppc64el openssl
• sope/s390x (5.6.0-1 to 5.6.0-1)
  • Migration status for sope/s390x (5.6.0-1 to 5.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: sope/s390x openssl
• spamassassin/amd64 (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/amd64 (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/amd64 openssl
• spamassassin/arm64 (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/arm64 (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/arm64 openssl
• spamassassin/armel (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/armel (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/armel openssl
• spamassassin/armhf (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/armhf (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/armhf openssl
• spamassassin/i386 (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/i386 (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/i386 openssl
• spamassassin/mips64el (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/mips64el (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/mips64el openssl
• spamassassin/mipsel (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/mipsel (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/mipsel openssl
• spamassassin/ppc64el (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/ppc64el (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/ppc64el openssl
• spamassassin/s390x (3.4.6-1 to 3.4.6-1)
  • Migration status for spamassassin/s390x (3.4.6-1 to 3.4.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: spamassassin/s390x openssl
• spice-gtk/amd64 (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/amd64 (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/amd64 openssl
• spice-gtk/arm64 (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/arm64 (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/arm64 openssl
• spice-gtk/armel (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/armel (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/armel openssl
• spice-gtk/armhf (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/armhf (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/armhf openssl
• spice-gtk/i386 (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/i386 (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/i386 openssl
• spice-gtk/mips64el (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/mips64el (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/mips64el openssl
• spice-gtk/mipsel (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/mipsel (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/mipsel openssl
• spice-gtk/ppc64el (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/ppc64el (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/ppc64el openssl
• spice-gtk/s390x (0.39-3.1 to 0.39-3.1)
  • Migration status for spice-gtk/s390x (0.39-3.1 to 0.39-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: spice-gtk/s390x openssl
• spiped/amd64 (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/amd64 (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/amd64 openssl
• spiped/arm64 (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/arm64 (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/arm64 openssl
• spiped/armel (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/armel (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/armel openssl
• spiped/armhf (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/armhf (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/armhf openssl
• spiped/i386 (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/i386 (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/i386 openssl
• spiped/mips64el (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/mips64el (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/mips64el openssl
• spiped/mipsel (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/mipsel (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/mipsel openssl
• spiped/ppc64el (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/ppc64el (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/ppc64el openssl
• spiped/s390x (1.6.2-2 to 1.6.2-2)
  • Migration status for spiped/s390x (1.6.2-2 to 1.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: spiped/s390x openssl
• springlobby/amd64 (0.273-1 to 0.273-1)
  • Migration status for springlobby/amd64 (0.273-1 to 0.273-1): Will attempt migration (Any information below is purely informational)
    • Depends: springlobby/amd64 openssl
• springlobby/i386 (0.273-1 to 0.273-1)
  • Migration status for springlobby/i386 (0.273-1 to 0.273-1): Will attempt migration (Any information below is purely informational)
    • Depends: springlobby/i386 openssl
• sqlcipher/amd64 (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/amd64 (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/amd64 openssl
• sqlcipher/arm64 (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/arm64 (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/arm64 openssl
• sqlcipher/armel (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/armel (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/armel openssl
• sqlcipher/armhf (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/armhf (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/armhf openssl
• sqlcipher/i386 (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/i386 (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/i386 openssl
• sqlcipher/mips64el (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/mips64el (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/mips64el openssl
• sqlcipher/mipsel (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/mipsel (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/mipsel openssl
• sqlcipher/ppc64el (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/ppc64el (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/ppc64el openssl
• sqlcipher/s390x (3.4.1-2 to 3.4.1-2)
  • Migration status for sqlcipher/s390x (3.4.1-2 to 3.4.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sqlcipher/s390x openssl
• squeezelite/amd64 (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/amd64 (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/amd64 openssl
• squeezelite/arm64 (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/arm64 (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/arm64 openssl
• squeezelite/armel (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/armel (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/armel openssl
• squeezelite/armhf (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/armhf (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/armhf openssl
• squeezelite/i386 (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/i386 (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/i386 openssl
• squeezelite/mips64el (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/mips64el (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/mips64el openssl
• squeezelite/mipsel (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/mipsel (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/mipsel openssl
• squeezelite/ppc64el (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/ppc64el (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/ppc64el openssl
• squeezelite/s390x (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1)
  • Migration status for squeezelite/s390x (1.9.9-1395+git20220104.874e4f9-1 to 1.9.9-1395+git20220104.874e4f9-1): Will attempt migration (Any information below is purely informational)
    • Depends: squeezelite/s390x openssl
• srt/amd64 (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/amd64 (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/amd64 openssl
• srt/arm64 (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/arm64 (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/arm64 openssl
• srt/armel (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/armel (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/armel openssl
• srt/armhf (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/armhf (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/armhf openssl
• srt/i386 (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/i386 (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/i386 openssl
• srt/mips64el (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/mips64el (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/mips64el openssl
• srt/mipsel (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/mipsel (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/mipsel openssl
• srt/ppc64el (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/ppc64el (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/ppc64el openssl
• srt/s390x (1.4.4-4 to 1.4.4-4)
  • Migration status for srt/s390x (1.4.4-4 to 1.4.4-4): Will attempt migration (Any information below is purely informational)
    • Depends: srt/s390x openssl
• sscg/amd64 (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/amd64 (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/amd64 openssl
• sscg/arm64 (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/arm64 (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/arm64 openssl
• sscg/armel (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/armel (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/armel openssl
• sscg/armhf (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/armhf (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/armhf openssl
• sscg/i386 (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/i386 (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/i386 openssl
• sscg/mips64el (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/mips64el (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/mips64el openssl
• sscg/mipsel (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/mipsel (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/mipsel openssl
• sscg/ppc64el (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/ppc64el (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/ppc64el openssl
• sscg/s390x (3.0.2-1 to 3.0.2-1)
  • Migration status for sscg/s390x (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: sscg/s390x openssl
• ssldump/amd64 (1.3-2 to 1.3-2)
  • Migration status for ssldump/amd64 (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/amd64 openssl
• ssldump/arm64 (1.3-2 to 1.3-2)
  • Migration status for ssldump/arm64 (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/arm64 openssl
• ssldump/armel (1.3-2 to 1.3-2)
  • Migration status for ssldump/armel (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/armel openssl
• ssldump/armhf (1.3-2 to 1.3-2)
  • Migration status for ssldump/armhf (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/armhf openssl
• ssldump/i386 (1.3-2 to 1.3-2)
  • Migration status for ssldump/i386 (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/i386 openssl
• ssldump/mips64el (1.3-2 to 1.3-2)
  • Migration status for ssldump/mips64el (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/mips64el openssl
• ssldump/mipsel (1.3-2 to 1.3-2)
  • Migration status for ssldump/mipsel (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/mipsel openssl
• ssldump/ppc64el (1.3-2 to 1.3-2)
  • Migration status for ssldump/ppc64el (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/ppc64el openssl
• ssldump/s390x (1.3-2 to 1.3-2)
  • Migration status for ssldump/s390x (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: ssldump/s390x openssl
• sslscan/amd64 (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/amd64 (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/amd64 openssl
• sslscan/arm64 (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/arm64 (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/arm64 openssl
• sslscan/armel (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/armel (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/armel openssl
• sslscan/armhf (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/armhf (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/armhf openssl
• sslscan/i386 (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/i386 (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/i386 openssl
• sslscan/mips64el (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/mips64el (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/mips64el openssl
• sslscan/mipsel (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/mipsel (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/mipsel openssl
• sslscan/ppc64el (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/ppc64el (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/ppc64el openssl
• sslscan/s390x (2.0.7-1 to 2.0.7-1)
  • Migration status for sslscan/s390x (2.0.7-1 to 2.0.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: sslscan/s390x openssl
• sslsniff/amd64 (0.8-9 to 0.8-9)
  • Migration status for sslsniff/amd64 (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/amd64 openssl
• sslsniff/arm64 (0.8-9 to 0.8-9)
  • Migration status for sslsniff/arm64 (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/arm64 openssl
• sslsniff/armel (0.8-9 to 0.8-9)
  • Migration status for sslsniff/armel (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/armel openssl
• sslsniff/armhf (0.8-9 to 0.8-9)
  • Migration status for sslsniff/armhf (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/armhf openssl
• sslsniff/i386 (0.8-9 to 0.8-9)
  • Migration status for sslsniff/i386 (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/i386 openssl
• sslsniff/mips64el (0.8-9 to 0.8-9)
  • Migration status for sslsniff/mips64el (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/mips64el openssl
• sslsniff/mipsel (0.8-9 to 0.8-9)
  • Migration status for sslsniff/mipsel (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/mipsel openssl
• sslsniff/ppc64el (0.8-9 to 0.8-9)
  • Migration status for sslsniff/ppc64el (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/ppc64el openssl
• sslsniff/s390x (0.8-9 to 0.8-9)
  • Migration status for sslsniff/s390x (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
    • Depends: sslsniff/s390x openssl
• sstp-client/amd64 (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/amd64 (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/amd64 openssl
• sstp-client/arm64 (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/arm64 (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/arm64 openssl
• sstp-client/armel (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/armel (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/armel openssl
• sstp-client/armhf (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/armhf (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/armhf openssl
• sstp-client/i386 (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/i386 (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/i386 openssl
• sstp-client/mips64el (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/mips64el (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/mips64el openssl
• sstp-client/mipsel (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/mipsel (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/mipsel openssl
• sstp-client/ppc64el (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/ppc64el (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/ppc64el openssl
• sstp-client/s390x (1.0.17-1 to 1.0.17-1)
  • Migration status for sstp-client/s390x (1.0.17-1 to 1.0.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: sstp-client/s390x openssl
• ssvnc/amd64 (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/amd64 (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/amd64 openssl
• ssvnc/arm64 (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/arm64 (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/arm64 openssl
• ssvnc/armel (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/armel (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/armel openssl
• ssvnc/armhf (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/armhf (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/armhf openssl
• ssvnc/i386 (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/i386 (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/i386 openssl
• ssvnc/mips64el (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/mips64el (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/mips64el openssl
• ssvnc/mipsel (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/mipsel (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/mipsel openssl
• ssvnc/ppc64el (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/ppc64el (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/ppc64el openssl
• ssvnc/s390x (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/s390x (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
    • Depends: ssvnc/s390x openssl
• stone/amd64 (2.4-1 to 2.4-1)
  • Migration status for stone/amd64 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/amd64 openssl
• stone/arm64 (2.4-1 to 2.4-1)
  • Migration status for stone/arm64 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/arm64 openssl
• stone/armel (2.4-1 to 2.4-1)
  • Migration status for stone/armel (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/armel openssl
• stone/armhf (2.4-1 to 2.4-1)
  • Migration status for stone/armhf (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/armhf openssl
• stone/i386 (2.4-1 to 2.4-1)
  • Migration status for stone/i386 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/i386 openssl
• stone/mips64el (2.4-1 to 2.4-1)
  • Migration status for stone/mips64el (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/mips64el openssl
• stone/mipsel (2.4-1 to 2.4-1)
  • Migration status for stone/mipsel (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/mipsel openssl
• stone/ppc64el (2.4-1 to 2.4-1)
  • Migration status for stone/ppc64el (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/ppc64el openssl
• stone/s390x (2.4-1 to 2.4-1)
  • Migration status for stone/s390x (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: stone/s390x openssl
• storm-lang/amd64 (0.5.10-1 to 0.5.10-1)
  • Migration status for storm-lang/amd64 (0.5.10-1 to 0.5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: storm-lang/amd64 openssl
• strongswan/amd64 (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/amd64 (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/amd64 openssl
• strongswan/arm64 (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/arm64 (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/arm64 openssl
• strongswan/armel (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/armel (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/armel openssl
• strongswan/armhf (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/armhf (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/armhf openssl
• strongswan/i386 (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/i386 (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/i386 openssl
• strongswan/mips64el (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/mips64el (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/mips64el openssl
• strongswan/mipsel (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/mipsel (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/mipsel openssl
• strongswan/ppc64el (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/ppc64el (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/ppc64el openssl
• strongswan/s390x (5.9.6-1 to 5.9.6-1)
  • Migration status for strongswan/s390x (5.9.6-1 to 5.9.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: strongswan/s390x openssl
• stunnel4/amd64 (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/amd64 (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/amd64 openssl
• stunnel4/arm64 (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/arm64 (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/arm64 openssl
• stunnel4/armel (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/armel (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/armel openssl
• stunnel4/armhf (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/armhf (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/armhf openssl
• stunnel4/i386 (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/i386 (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/i386 openssl
• stunnel4/mips64el (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/mips64el (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/mips64el openssl
• stunnel4/mipsel (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/mipsel (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/mipsel openssl
• stunnel4/ppc64el (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/ppc64el (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/ppc64el openssl
• stunnel4/s390x (3:5.63-1 to 3:5.63-1)
  • Migration status for stunnel4/s390x (3:5.63-1 to 3:5.63-1): Will attempt migration (Any information below is purely informational)
    • Depends: stunnel4/s390x openssl
• subversion_pu (1.14.2-2 to 1.14.1-3+deb11u1)
  • Migration status for subversion_pu (1.14.2-2 to 1.14.1-3+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: subversion is newer in the target suite (1.14.2-2 1.14.1-3+deb11u1)
• suck/amd64 (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/amd64 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/amd64 openssl
• suck/arm64 (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/arm64 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/arm64 openssl
• suck/armel (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/armel (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/armel openssl
• suck/armhf (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/armhf (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/armhf openssl
• suck/i386 (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/i386 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/i386 openssl
• suck/mips64el (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/mips64el (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/mips64el openssl
• suck/mipsel (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/mipsel (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/mipsel openssl
• suck/ppc64el (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/ppc64el (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/ppc64el openssl
• suck/s390x (4.3.4-1 to 4.3.4-1)
  • Migration status for suck/s390x (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: suck/s390x openssl
• swi-prolog/amd64 (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/amd64 (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/amd64 openssl
• swi-prolog/arm64 (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/arm64 (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/arm64 openssl
• swi-prolog/armel (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/armel (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/armel openssl
• swi-prolog/armhf (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/armhf (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/armhf openssl
• swi-prolog/i386 (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/i386 (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/i386 openssl
• swi-prolog/mips64el (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/mips64el (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/mips64el openssl
• swi-prolog/mipsel (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/mipsel (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/mipsel openssl
• swi-prolog/ppc64el (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/ppc64el (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/ppc64el openssl
• swi-prolog/s390x (8.4.2+dfsg-2 to 8.4.2+dfsg-2)
  • Migration status for swi-prolog/s390x (8.4.2+dfsg-2 to 8.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: swi-prolog/s390x openssl
• swtpm/amd64 (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/amd64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/amd64 openssl
• swtpm/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/arm64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/arm64 openssl
• swtpm/armel (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/armel openssl
• swtpm/armhf (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/armhf (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/armhf openssl
• swtpm/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/i386 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/i386 openssl
• swtpm/mips64el (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/mips64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/mips64el openssl
• swtpm/mipsel (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/mipsel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/mipsel openssl
• swtpm/ppc64el (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/ppc64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/ppc64el openssl
• swtpm/s390x (0.7.1-1 to 0.7.1-1)
  • Migration status for swtpm/s390x (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: swtpm/s390x openssl
• sylpheed/amd64 (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/amd64 (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/amd64 openssl
• sylpheed/arm64 (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/arm64 (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/arm64 openssl
• sylpheed/armel (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/armel (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/armel openssl
• sylpheed/armhf (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/armhf (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/armhf openssl
• sylpheed/i386 (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/i386 (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/i386 openssl
• sylpheed/mips64el (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/mips64el (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/mips64el openssl
• sylpheed/mipsel (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/mipsel (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/mipsel openssl
• sylpheed/ppc64el (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/ppc64el (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/ppc64el openssl
• sylpheed/s390x (3.7.0-8 to 3.7.0-8)
  • Migration status for sylpheed/s390x (3.7.0-8 to 3.7.0-8): Will attempt migration (Any information below is purely informational)
    • Depends: sylpheed/s390x openssl
• sysdig/amd64 (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/amd64 (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/amd64 openssl
• sysdig/arm64 (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/arm64 (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/arm64 openssl
• sysdig/armel (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/armel (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/armel openssl
• sysdig/armhf (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/armhf (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/armhf openssl
• sysdig/i386 (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/i386 (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/i386 openssl
• sysdig/mips64el (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/mips64el (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/mips64el openssl
• sysdig/mipsel (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/mipsel (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/mipsel openssl
• sysdig/ppc64el (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/ppc64el (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/ppc64el openssl
• sysdig/s390x (0.27.1-0.3 to 0.27.1-0.3)
  • Migration status for sysdig/s390x (0.27.1-0.3 to 0.27.1-0.3): Will attempt migration (Any information below is purely informational)
    • Depends: sysdig/s390x openssl
• syslog-ng/amd64 (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/amd64 (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/amd64 openssl
• syslog-ng/arm64 (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/arm64 (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/arm64 openssl
• syslog-ng/armel (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/armel (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/armel openssl
• syslog-ng/armhf (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/armhf (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/armhf openssl
• syslog-ng/i386 (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/i386 (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/i386 openssl
• syslog-ng/mips64el (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/mips64el (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/mips64el openssl
• syslog-ng/mipsel (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/mipsel (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/mipsel openssl
• syslog-ng/ppc64el (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/ppc64el (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/ppc64el openssl
• syslog-ng/s390x (3.35.1-1 to 3.35.1-1)
  • Migration status for syslog-ng/s390x (3.35.1-1 to 3.35.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: syslog-ng/s390x openssl
• tarantool/amd64 (2.6.0-1 to 2.6.0-1)
  • Migration status for tarantool/amd64 (2.6.0-1 to 2.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tarantool/amd64 openssl
• tarantool/i386 (2.6.0-1 to 2.6.0-1)
  • Migration status for tarantool/i386 (2.6.0-1 to 2.6.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tarantool/i386 openssl
• tcltls/amd64 (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/amd64 (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/amd64 openssl
• tcltls/arm64 (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/arm64 (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/arm64 openssl
• tcltls/armel (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/armel (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/armel openssl
• tcltls/armhf (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/armhf (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/armhf openssl
• tcltls/i386 (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/i386 (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/i386 openssl
• tcltls/mips64el (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/mips64el (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/mips64el openssl
• tcltls/mipsel (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/mipsel (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/mipsel openssl
• tcltls/ppc64el (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/ppc64el (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/ppc64el openssl
• tcltls/s390x (1.7.22-3 to 1.7.22-3)
  • Migration status for tcltls/s390x (1.7.22-3 to 1.7.22-3): Will attempt migration (Any information below is purely informational)
    • Depends: tcltls/s390x openssl
• tcltrf/amd64 (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/amd64 (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/amd64 openssl
• tcltrf/arm64 (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/arm64 (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/arm64 openssl
• tcltrf/armel (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/armel (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/armel openssl
• tcltrf/armhf (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/armhf (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/armhf openssl
• tcltrf/i386 (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/i386 (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/i386 openssl
• tcltrf/mips64el (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/mips64el (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/mips64el openssl
• tcltrf/mipsel (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/mipsel (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/mipsel openssl
• tcltrf/ppc64el (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/ppc64el (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/ppc64el openssl
• tcltrf/s390x (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1)
  • Migration status for tcltrf/s390x (2.1.4-dfsg3-2.1 to 2.1.4-dfsg3-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: tcltrf/s390x openssl
• tcpdump/amd64 (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/amd64 (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/amd64 openssl
• tcpdump/arm64 (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/arm64 (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/arm64 openssl
• tcpdump/armel (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/armel (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/armel openssl
• tcpdump/armhf (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/armhf (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/armhf openssl
• tcpdump/i386 (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/i386 (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/i386 openssl
• tcpdump/mips64el (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/mips64el (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/mips64el openssl
• tcpdump/mipsel (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/mipsel (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/mipsel openssl
• tcpdump/ppc64el (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/ppc64el (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/ppc64el openssl
• tcpdump/s390x (4.99.1-4 to 4.99.1-4)
  • Migration status for tcpdump/s390x (4.99.1-4 to 4.99.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: tcpdump/s390x openssl
• tcpdump_pu (4.99.1-4 to 4.99.0-2+deb11u1)
  • Migration status for tcpdump_pu (4.99.1-4 to 4.99.0-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: tcpdump is newer in the target suite (4.99.1-4 4.99.0-2+deb11u1)
• tcpflow/amd64 (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/amd64 (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/amd64 openssl
• tcpflow/arm64 (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/arm64 (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/arm64 openssl
• tcpflow/armel (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/armel (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/armel openssl
• tcpflow/armhf (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/armhf (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/armhf openssl
• tcpflow/i386 (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/i386 (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/i386 openssl
• tcpflow/mips64el (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/mips64el (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/mips64el openssl
• tcpflow/mipsel (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/mipsel (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/mipsel openssl
• tcpflow/ppc64el (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/ppc64el (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/ppc64el openssl
• tcpflow/s390x (1.6.1-2 to 1.6.1-2)
  • Migration status for tcpflow/s390x (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: tcpflow/s390x openssl
• telegram-desktop_pu (3.7.3+ds-1 to 3.1.1+ds-1~deb11u2)
  • Migration status for telegram-desktop_pu (3.7.3+ds-1 to 3.1.1+ds-1~deb11u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: telegram-desktop is newer in the target suite (3.7.3+ds-1 3.1.1+ds-1~deb11u2)
• tf5/amd64 (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/amd64 (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/amd64 openssl
• tf5/arm64 (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/arm64 (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/arm64 openssl
• tf5/armel (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/armel (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/armel openssl
• tf5/armhf (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/armhf (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/armhf openssl
• tf5/i386 (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/i386 (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/i386 openssl
• tf5/mips64el (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/mips64el (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/mips64el openssl
• tf5/mipsel (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/mipsel (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/mipsel openssl
• tf5/ppc64el (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/ppc64el (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/ppc64el openssl
• tf5/s390x (5.0beta8-10 to 5.0beta8-10)
  • Migration status for tf5/s390x (5.0beta8-10 to 5.0beta8-10): Will attempt migration (Any information below is purely informational)
    • Depends: tf5/s390x openssl
• tgl/amd64 (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/amd64 (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/amd64 openssl
• tgl/arm64 (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/arm64 (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/arm64 openssl
• tgl/armel (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/armel (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/armel openssl
• tgl/armhf (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/armhf (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/armhf openssl
• tgl/i386 (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/i386 (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/i386 openssl
• tgl/mips64el (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/mips64el (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/mips64el openssl
• tgl/mipsel (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/mipsel (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/mipsel openssl
• tgl/ppc64el (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/ppc64el (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/ppc64el openssl
• tgl/s390x (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3)
  • Migration status for tgl/s390x (2.0.1+git20160323.ffb04cac-3 to 2.0.1+git20160323.ffb04cac-3): Will attempt migration (Any information below is purely informational)
    • Depends: tgl/s390x openssl
• thc-ipv6/amd64 (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/amd64 (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/amd64 openssl
• thc-ipv6/arm64 (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/arm64 (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/arm64 openssl
• thc-ipv6/armel (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/armel (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/armel openssl
• thc-ipv6/armhf (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/armhf (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/armhf openssl
• thc-ipv6/i386 (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/i386 (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/i386 openssl
• thc-ipv6/mips64el (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/mips64el (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/mips64el openssl
• thc-ipv6/mipsel (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/mipsel (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/mipsel openssl
• thc-ipv6/ppc64el (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/ppc64el (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/ppc64el openssl
• thc-ipv6/s390x (3.8-1 to 3.8-1)
  • Migration status for thc-ipv6/s390x (3.8-1 to 3.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: thc-ipv6/s390x openssl
• thunderbird_pu (1:91.10.0-1 to 1:91.8.0-1~deb11u1)
  • Migration status for thunderbird_pu (1:91.10.0-1 to 1:91.8.0-1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: thunderbird is newer in the target suite (1:91.10.0-1 1:91.8.0-1~deb11u1)
• tiff_pu (4.4.0-2 to 4.2.0-1+deb11u1)
  • Migration status for tiff_pu (4.4.0-2 to 4.2.0-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: tiff is newer in the target suite (4.4.0-2 4.2.0-1+deb11u1)
• tinc/amd64 (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/amd64 (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/amd64 openssl
• tinc/arm64 (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/arm64 (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/arm64 openssl
• tinc/armel (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/armel (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/armel openssl
• tinc/armhf (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/armhf (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/armhf openssl
• tinc/i386 (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/i386 (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/i386 openssl
• tinc/mips64el (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/mips64el (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/mips64el openssl
• tinc/mipsel (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/mipsel (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/mipsel openssl
• tinc/ppc64el (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/ppc64el (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/ppc64el openssl
• tinc/s390x (1.0.36-2 to 1.0.36-2)
  • Migration status for tinc/s390x (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
    • Depends: tinc/s390x openssl
• tnftp/amd64 (20210827-4 to 20210827-4)
  • Migration status for tnftp/amd64 (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/amd64 openssl
• tnftp/arm64 (20210827-4 to 20210827-4)
  • Migration status for tnftp/arm64 (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/arm64 openssl
• tnftp/armel (20210827-4 to 20210827-4)
  • Migration status for tnftp/armel (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/armel openssl
• tnftp/armhf (20210827-4 to 20210827-4)
  • Migration status for tnftp/armhf (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/armhf openssl
• tnftp/i386 (20210827-4 to 20210827-4)
  • Migration status for tnftp/i386 (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/i386 openssl
• tnftp/mips64el (20210827-4 to 20210827-4)
  • Migration status for tnftp/mips64el (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/mips64el openssl
• tnftp/mipsel (20210827-4 to 20210827-4)
  • Migration status for tnftp/mipsel (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/mipsel openssl
• tnftp/ppc64el (20210827-4 to 20210827-4)
  • Migration status for tnftp/ppc64el (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/ppc64el openssl
• tnftp/s390x (20210827-4 to 20210827-4)
  • Migration status for tnftp/s390x (20210827-4 to 20210827-4): Will attempt migration (Any information below is purely informational)
    • Depends: tnftp/s390x openssl
• tomcat-native/amd64 (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/amd64 (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/amd64 openssl
• tomcat-native/arm64 (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/arm64 (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/arm64 openssl
• tomcat-native/armel (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/armel (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/armel openssl
• tomcat-native/armhf (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/armhf (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/armhf openssl
• tomcat-native/i386 (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/i386 (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/i386 openssl
• tomcat-native/mips64el (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/mips64el (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/mips64el openssl
• tomcat-native/mipsel (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/mipsel (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/mipsel openssl
• tomcat-native/ppc64el (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/ppc64el (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/ppc64el openssl
• tomcat-native/s390x (1.2.32-1 to 1.2.32-1)
  • Migration status for tomcat-native/s390x (1.2.32-1 to 1.2.32-1): Will attempt migration (Any information below is purely informational)
    • Depends: tomcat-native/s390x openssl
• tor/amd64 (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/amd64 (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/amd64 openssl
• tor/arm64 (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/arm64 (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/arm64 openssl
• tor/armel (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/armel (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/armel openssl
• tor/armhf (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/armhf (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/armhf openssl
• tor/i386 (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/i386 (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/i386 openssl
• tor/mips64el (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/mips64el (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/mips64el openssl
• tor/mipsel (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/mipsel (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/mipsel openssl
• tor/ppc64el (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/ppc64el (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/ppc64el openssl
• tor/s390x (0.4.7.7-1 to 0.4.7.7-1)
  • Migration status for tor/s390x (0.4.7.7-1 to 0.4.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: tor/s390x openssl
• tpm-quote-tools/amd64 (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/amd64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/amd64 openssl
• tpm-quote-tools/arm64 (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/arm64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/arm64 openssl
• tpm-quote-tools/armel (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/armel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/armel openssl
• tpm-quote-tools/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/armhf openssl
• tpm-quote-tools/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/i386 openssl
• tpm-quote-tools/mips64el (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/mips64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/mips64el openssl
• tpm-quote-tools/mipsel (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/mipsel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/mipsel openssl
• tpm-quote-tools/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/ppc64el openssl
• tpm-quote-tools/s390x (1.0.4-1 to 1.0.4-1)
  • Migration status for tpm-quote-tools/s390x (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-quote-tools/s390x openssl
• tpm-tools/amd64 (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/amd64 (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/amd64 openssl
• tpm-tools/arm64 (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/arm64 (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/arm64 openssl
• tpm-tools/armel (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/armel (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/armel openssl
• tpm-tools/armhf (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/armhf (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/armhf openssl
• tpm-tools/i386 (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/i386 (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/i386 openssl
• tpm-tools/mips64el (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/mips64el (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/mips64el openssl
• tpm-tools/mipsel (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/mipsel (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/mipsel openssl
• tpm-tools/ppc64el (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/ppc64el (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/ppc64el openssl
• tpm-tools/s390x (1.3.9.1-0.2 to 1.3.9.1-0.2)
  • Migration status for tpm-tools/s390x (1.3.9.1-0.2 to 1.3.9.1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: tpm-tools/s390x openssl
• tpm2-tools/amd64 (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/amd64 (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/amd64 openssl
• tpm2-tools/arm64 (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/arm64 (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/arm64 openssl
• tpm2-tools/armel (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/armel (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/armel openssl
• tpm2-tools/armhf (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/armhf (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/armhf openssl
• tpm2-tools/i386 (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/i386 (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/i386 openssl
• tpm2-tools/mips64el (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/mips64el (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/mips64el openssl
• tpm2-tools/mipsel (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/mipsel (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/mipsel openssl
• tpm2-tools/ppc64el (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/ppc64el (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/ppc64el openssl
• tpm2-tools/s390x (5.2-1 to 5.2-1)
  • Migration status for tpm2-tools/s390x (5.2-1 to 5.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tools/s390x openssl
• tpm2-tss/amd64 (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/amd64 (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/amd64 openssl
• tpm2-tss/arm64 (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/arm64 (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/arm64 openssl
• tpm2-tss/armel (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/armel (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/armel openssl
• tpm2-tss/armhf (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/armhf (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/armhf openssl
• tpm2-tss/i386 (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/i386 (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/i386 openssl
• tpm2-tss/mips64el (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/mips64el (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/mips64el openssl
• tpm2-tss/mipsel (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/mipsel (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/mipsel openssl
• tpm2-tss/ppc64el (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/ppc64el (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/ppc64el openssl
• tpm2-tss/s390x (3.2.0-1 to 3.2.0-1)
  • Migration status for tpm2-tss/s390x (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-tss/s390x openssl
• trojan/amd64 (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/amd64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/amd64 openssl
• trojan/arm64 (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/arm64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/arm64 openssl
• trojan/armel (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/armel (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/armel openssl
• trojan/armhf (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/armhf (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/armhf openssl
• trojan/i386 (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/i386 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/i386 openssl
• trojan/mips64el (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/mips64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/mips64el openssl
• trojan/mipsel (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/mipsel (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/mipsel openssl
• trojan/ppc64el (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/ppc64el (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/ppc64el openssl
• trojan/s390x (1.16.0-1 to 1.16.0-1)
  • Migration status for trojan/s390x (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: trojan/s390x openssl
• trousers/amd64 (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/amd64 (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/amd64 openssl
• trousers/arm64 (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/arm64 (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/arm64 openssl
• trousers/armel (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/armel (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/armel openssl
• trousers/armhf (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/armhf (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/armhf openssl
• trousers/i386 (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/i386 (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/i386 openssl
• trousers/mips64el (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/mips64el (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/mips64el openssl
• trousers/mipsel (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/mipsel (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/mipsel openssl
• trousers/ppc64el (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/ppc64el (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/ppc64el openssl
• trousers/s390x (0.3.15-0.2 to 0.3.15-0.2)
  • Migration status for trousers/s390x (0.3.15-0.2 to 0.3.15-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: trousers/s390x openssl
• tsdecrypt/amd64 (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/amd64 (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/amd64 openssl
• tsdecrypt/arm64 (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/arm64 (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/arm64 openssl
• tsdecrypt/armel (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/armel (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/armel openssl
• tsdecrypt/armhf (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/armhf (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/armhf openssl
• tsdecrypt/i386 (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/i386 (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/i386 openssl
• tsdecrypt/mips64el (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/mips64el (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/mips64el openssl
• tsdecrypt/mipsel (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/mipsel (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/mipsel openssl
• tsdecrypt/ppc64el (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/ppc64el (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/ppc64el openssl
• tsdecrypt/s390x (10.0-2 to 10.0-2)
  • Migration status for tsdecrypt/s390x (10.0-2 to 10.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: tsdecrypt/s390x openssl
• tss2/amd64 (1045-1.2 to 1045-1.2)
  • Migration status for tss2/amd64 (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/amd64 openssl
• tss2/arm64 (1045-1.2 to 1045-1.2)
  • Migration status for tss2/arm64 (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/arm64 openssl
• tss2/armel (1045-1.2 to 1045-1.2)
  • Migration status for tss2/armel (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/armel openssl
• tss2/armhf (1045-1.2 to 1045-1.2)
  • Migration status for tss2/armhf (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/armhf openssl
• tss2/i386 (1045-1.2 to 1045-1.2)
  • Migration status for tss2/i386 (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/i386 openssl
• tss2/mips64el (1045-1.2 to 1045-1.2)
  • Migration status for tss2/mips64el (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/mips64el openssl
• tss2/mipsel (1045-1.2 to 1045-1.2)
  • Migration status for tss2/mipsel (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/mipsel openssl
• tss2/ppc64el (1045-1.2 to 1045-1.2)
  • Migration status for tss2/ppc64el (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/ppc64el openssl
• tss2/s390x (1045-1.2 to 1045-1.2)
  • Migration status for tss2/s390x (1045-1.2 to 1045-1.2): Will attempt migration (Any information below is purely informational)
    • Depends: tss2/s390x openssl
• twisted_pu (22.4.0-2 to 20.3.0-7+deb11u1)
  • Migration status for twisted_pu (22.4.0-2 to 20.3.0-7+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: twisted is newer in the target suite (22.4.0-2 20.3.0-7+deb11u1)
• tzdata_pu (2022a-1 to 2021a-1+deb11u3)
  • Migration status for tzdata_pu (2022a-1 to 2021a-1+deb11u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: tzdata is newer in the target suite (2022a-1 2021a-1+deb11u3)
• u-boot/amd64 (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/amd64 (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/amd64 openssl
• u-boot/arm64 (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/arm64 (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/arm64 openssl
• u-boot/armel (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/armel (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/armel openssl
• u-boot/armhf (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/armhf (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/armhf openssl
• u-boot/i386 (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/i386 (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/i386 openssl
• u-boot/mips64el (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/mips64el (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/mips64el openssl
• u-boot/mipsel (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/mipsel (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/mipsel openssl
• u-boot/ppc64el (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/ppc64el (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/ppc64el openssl
• u-boot/s390x (2022.04+dfsg-2 to 2022.04+dfsg-2)
  • Migration status for u-boot/s390x (2022.04+dfsg-2 to 2022.04+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: u-boot/s390x openssl
• uftp/amd64 (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/amd64 (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/amd64 openssl
• uftp/arm64 (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/arm64 (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/arm64 openssl
• uftp/armel (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/armel (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/armel openssl
• uftp/armhf (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/armhf (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/armhf openssl
• uftp/i386 (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/i386 (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/i386 openssl
• uftp/mips64el (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/mips64el (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/mips64el openssl
• uftp/mipsel (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/mipsel (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/mipsel openssl
• uftp/ppc64el (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/ppc64el (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/ppc64el openssl
• uftp/s390x (4.10.2-1.1 to 4.10.2-1.1)
  • Migration status for uftp/s390x (4.10.2-1.1 to 4.10.2-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: uftp/s390x openssl
• uget/amd64 (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/amd64 (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/amd64 openssl
• uget/arm64 (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/arm64 (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/arm64 openssl
• uget/armel (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/armel (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/armel openssl
• uget/armhf (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/armhf (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/armhf openssl
• uget/i386 (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/i386 (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/i386 openssl
• uget/mips64el (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/mips64el (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/mips64el openssl
• uget/mipsel (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/mipsel (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/mipsel openssl
• uget/ppc64el (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/ppc64el (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/ppc64el openssl
• uget/s390x (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/s390x (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: uget/s390x openssl
• uhub/amd64 (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/amd64 (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/amd64 openssl
• uhub/armel (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/armel (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/armel openssl
• uhub/armhf (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/armhf (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/armhf openssl
• uhub/i386 (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/i386 (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/i386 openssl
• uhub/mips64el (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/mips64el (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/mips64el openssl
• uhub/mipsel (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/mipsel (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/mipsel openssl
• uhub/ppc64el (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/ppc64el (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/ppc64el openssl
• uhub/s390x (0.4.1-3.1 to 0.4.1-3.1)
  • Migration status for uhub/s390x (0.4.1-3.1 to 0.4.1-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: uhub/s390x openssl
• unrar-nonfree_pu (1:6.1.7-2 to 1:6.0.3-1+deb11u1)
  • Migration status for unrar-nonfree_pu (1:6.1.7-2 to 1:6.0.3-1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: unrar-nonfree is newer in the target suite (1:6.1.7-2 1:6.0.3-1+deb11u1)
• unworkable/amd64 (0.53-5 to 0.53-5)
  • Migration status for unworkable/amd64 (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/amd64 openssl
• unworkable/arm64 (0.53-5 to 0.53-5)
  • Migration status for unworkable/arm64 (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/arm64 openssl
• unworkable/armel (0.53-5 to 0.53-5)
  • Migration status for unworkable/armel (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/armel openssl
• unworkable/armhf (0.53-5 to 0.53-5)
  • Migration status for unworkable/armhf (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/armhf openssl
• unworkable/i386 (0.53-5 to 0.53-5)
  • Migration status for unworkable/i386 (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/i386 openssl
• unworkable/mips64el (0.53-5 to 0.53-5)
  • Migration status for unworkable/mips64el (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/mips64el openssl
• unworkable/mipsel (0.53-5 to 0.53-5)
  • Migration status for unworkable/mipsel (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/mipsel openssl
• unworkable/ppc64el (0.53-5 to 0.53-5)
  • Migration status for unworkable/ppc64el (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/ppc64el openssl
• unworkable/s390x (0.53-5 to 0.53-5)
  • Migration status for unworkable/s390x (0.53-5 to 0.53-5): Will attempt migration (Any information below is purely informational)
    • Depends: unworkable/s390x openssl
• up-imapproxy/amd64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/amd64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/amd64 openssl
• up-imapproxy/arm64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/arm64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/arm64 openssl
• up-imapproxy/armel (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/armel (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/armel openssl
• up-imapproxy/armhf (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/armhf (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/armhf openssl
• up-imapproxy/i386 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/i386 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/i386 openssl
• up-imapproxy/mips64el (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/mips64el (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/mips64el openssl
• up-imapproxy/mipsel (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/mipsel (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/mipsel openssl
• up-imapproxy/ppc64el (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/ppc64el (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/ppc64el openssl
• up-imapproxy/s390x (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/s390x (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): Will attempt migration (Any information below is purely informational)
    • Depends: up-imapproxy/s390x openssl
• uw-imap/amd64 (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/amd64 (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/amd64 openssl
• uw-imap/arm64 (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/arm64 (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/arm64 openssl
• uw-imap/armel (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/armel (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/armel openssl
• uw-imap/armhf (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/armhf (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/armhf openssl
• uw-imap/i386 (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/i386 (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/i386 openssl
• uw-imap/mips64el (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/mips64el (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/mips64el openssl
• uw-imap/mipsel (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/mipsel (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/mipsel openssl
• uw-imap/ppc64el (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/ppc64el (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/ppc64el openssl
• uw-imap/s390x (8:2007f~dfsg-7 to 8:2007f~dfsg-7)
  • Migration status for uw-imap/s390x (8:2007f~dfsg-7 to 8:2007f~dfsg-7): Will attempt migration (Any information below is purely informational)
    • Depends: uw-imap/s390x openssl
• uwsgi/amd64 (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/amd64 (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/amd64 openssl
• uwsgi/arm64 (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/arm64 (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/arm64 openssl
• uwsgi/armel (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/armel (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/armel openssl
• uwsgi/armhf (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/armhf (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/armhf openssl
• uwsgi/i386 (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/i386 (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/i386 openssl
• uwsgi/mips64el (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/mips64el (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/mips64el openssl
• uwsgi/mipsel (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/mipsel (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/mipsel openssl
• uwsgi/ppc64el (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/ppc64el (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/ppc64el openssl
• uwsgi/s390x (2.0.20-4 to 2.0.20-4)
  • Migration status for uwsgi/s390x (2.0.20-4 to 2.0.20-4): Will attempt migration (Any information below is purely informational)
    • Depends: uwsgi/s390x openssl
• vboot-utils/amd64 (0~R99-14469.B-1 to 0~R99-14469.B-1)
  • Migration status for vboot-utils/amd64 (0~R99-14469.B-1 to 0~R99-14469.B-1): Will attempt migration (Any information below is purely informational)
    • Depends: vboot-utils/amd64 openssl
• vboot-utils/arm64 (0~R99-14469.B-1 to 0~R99-14469.B-1)
  • Migration status for vboot-utils/arm64 (0~R99-14469.B-1 to 0~R99-14469.B-1): Will attempt migration (Any information below is purely informational)
    • Depends: vboot-utils/arm64 openssl
• vboot-utils/armel (0~R99-14469.B-1 to 0~R99-14469.B-1)
  • Migration status for vboot-utils/armel (0~R99-14469.B-1 to 0~R99-14469.B-1): Will attempt migration (Any information below is purely informational)
    • Depends: vboot-utils/armel openssl
• vboot-utils/armhf (0~R99-14469.B-1 to 0~R99-14469.B-1)
  • Migration status for vboot-utils/armhf (0~R99-14469.B-1 to 0~R99-14469.B-1): Will attempt migration (Any information below is purely informational)
    • Depends: vboot-utils/armhf openssl
• vboot-utils/i386 (0~R99-14469.B-1 to 0~R99-14469.B-1)
  • Migration status for vboot-utils/i386 (0~R99-14469.B-1 to 0~R99-14469.B-1): Will attempt migration (Any information below is purely informational)
    • Depends: vboot-utils/i386 openssl
• vde2/amd64 (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/amd64 (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/amd64 openssl
• vde2/arm64 (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/arm64 (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/arm64 openssl
• vde2/armel (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/armel (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/armel openssl
• vde2/armhf (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/armhf (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/armhf openssl
• vde2/i386 (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/i386 (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/i386 openssl
• vde2/mips64el (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/mips64el (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/mips64el openssl
• vde2/mipsel (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/mipsel (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/mipsel openssl
• vde2/ppc64el (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/ppc64el (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/ppc64el openssl
• vde2/s390x (2.3.2+r586-8 to 2.3.2+r586-8)
  • Migration status for vde2/s390x (2.3.2+r586-8 to 2.3.2+r586-8): Will attempt migration (Any information below is purely informational)
    • Depends: vde2/s390x openssl
• veyon/amd64 (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/amd64 (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/amd64 openssl
• veyon/arm64 (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/arm64 (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/arm64 openssl
• veyon/armel (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/armel (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/armel openssl
• veyon/armhf (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/armhf (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/armhf openssl
• veyon/i386 (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/i386 (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/i386 openssl
• veyon/mips64el (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/mips64el (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/mips64el openssl
• veyon/mipsel (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/mipsel (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/mipsel openssl
• veyon/ppc64el (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/ppc64el (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/ppc64el openssl
• veyon/s390x (4.7.3+repack1-1 to 4.7.3+repack1-1)
  • Migration status for veyon/s390x (4.7.3+repack1-1 to 4.7.3+repack1-1): Will attempt migration (Any information below is purely informational)
    • Depends: veyon/s390x openssl
• virtuoso-opensource/amd64 (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2)
  • Migration status for virtuoso-opensource/amd64 (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: virtuoso-opensource/amd64 openssl
• virtuoso-opensource/arm64 (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2)
  • Migration status for virtuoso-opensource/arm64 (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: virtuoso-opensource/arm64 openssl
• virtuoso-opensource/mips64el (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2)
  • Migration status for virtuoso-opensource/mips64el (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: virtuoso-opensource/mips64el openssl
• virtuoso-opensource/ppc64el (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2)
  • Migration status for virtuoso-opensource/ppc64el (7.2.5.1+dfsg1-0.2 to 7.2.5.1+dfsg1-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: virtuoso-opensource/ppc64el openssl
• vlc-plugin-bittorrent/amd64 (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/amd64 (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/amd64 openssl
• vlc-plugin-bittorrent/arm64 (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/arm64 (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/arm64 openssl
• vlc-plugin-bittorrent/armel (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/armel (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/armel openssl
• vlc-plugin-bittorrent/armhf (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/armhf (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/armhf openssl
• vlc-plugin-bittorrent/i386 (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/i386 (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/i386 openssl
• vlc-plugin-bittorrent/mips64el (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/mips64el (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/mips64el openssl
• vlc-plugin-bittorrent/mipsel (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/mipsel (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/mipsel openssl
• vlc-plugin-bittorrent/ppc64el (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/ppc64el (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/ppc64el openssl
• vlc-plugin-bittorrent/s390x (2.14-1 to 2.14-1)
  • Migration status for vlc-plugin-bittorrent/s390x (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: vlc-plugin-bittorrent/s390x openssl
• voms-mysql-plugin/amd64 (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/amd64 (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/amd64 openssl
• voms-mysql-plugin/arm64 (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/arm64 (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/arm64 openssl
• voms-mysql-plugin/armel (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/armel (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/armel openssl
• voms-mysql-plugin/armhf (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/armhf (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/armhf openssl
• voms-mysql-plugin/i386 (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/i386 (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/i386 openssl
• voms-mysql-plugin/mips64el (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/mips64el (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/mips64el openssl
• voms-mysql-plugin/mipsel (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/mipsel (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/mipsel openssl
• voms-mysql-plugin/ppc64el (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/ppc64el (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/ppc64el openssl
• voms-mysql-plugin/s390x (3.1.7-2 to 3.1.7-2)
  • Migration status for voms-mysql-plugin/s390x (3.1.7-2 to 3.1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms-mysql-plugin/s390x openssl
• voms/amd64 (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/amd64 (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/amd64 openssl
• voms/arm64 (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/arm64 (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/arm64 openssl
• voms/armel (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/armel (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/armel openssl
• voms/armhf (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/armhf (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/armhf openssl
• voms/i386 (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/i386 (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/i386 openssl
• voms/mips64el (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/mips64el (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/mips64el openssl
• voms/mipsel (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/mipsel (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/mipsel openssl
• voms/ppc64el (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/ppc64el (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/ppc64el openssl
• voms/s390x (2.1.0~rc2-2 to 2.1.0~rc2-2)
  • Migration status for voms/s390x (2.1.0~rc2-2 to 2.1.0~rc2-2): Will attempt migration (Any information below is purely informational)
    • Depends: voms/s390x openssl
• vsftpd/amd64 (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/amd64 (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/amd64 openssl
• vsftpd/arm64 (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/arm64 (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/arm64 openssl
• vsftpd/armel (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/armel (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/armel openssl
• vsftpd/armhf (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/armhf (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/armhf openssl
• vsftpd/i386 (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/i386 (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/i386 openssl
• vsftpd/mips64el (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/mips64el (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/mips64el openssl
• vsftpd/mipsel (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/mipsel (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/mipsel openssl
• vsftpd/ppc64el (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/ppc64el (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/ppc64el openssl
• vsftpd/s390x (3.0.3-13 to 3.0.3-13)
  • Migration status for vsftpd/s390x (3.0.3-13 to 3.0.3-13): Will attempt migration (Any information below is purely informational)
    • Depends: vsftpd/s390x openssl
• vtun/amd64 (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/amd64 (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/amd64 openssl
• vtun/arm64 (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/arm64 (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/arm64 openssl
• vtun/armel (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/armel (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/armel openssl
• vtun/armhf (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/armhf (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/armhf openssl
• vtun/i386 (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/i386 (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/i386 openssl
• vtun/mips64el (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/mips64el (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/mips64el openssl
• vtun/mipsel (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/mipsel (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/mipsel openssl
• vtun/ppc64el (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/ppc64el (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/ppc64el openssl
• vtun/s390x (3.0.4-2 to 3.0.4-2)
  • Migration status for vtun/s390x (3.0.4-2 to 3.0.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: vtun/s390x openssl
• w3m/amd64 (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/amd64 (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/amd64 openssl
• w3m/arm64 (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/arm64 (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/arm64 openssl
• w3m/armel (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/armel (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/armel openssl
• w3m/armhf (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/armhf (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/armhf openssl
• w3m/i386 (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/i386 (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/i386 openssl
• w3m/mips64el (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/mips64el (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/mips64el openssl
• w3m/mipsel (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/mipsel (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/mipsel openssl
• w3m/ppc64el (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/ppc64el (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/ppc64el openssl
• w3m/s390x (0.5.3+git20220429-1 to 0.5.3+git20220429-1)
  • Migration status for w3m/s390x (0.5.3+git20220429-1 to 0.5.3+git20220429-1): Will attempt migration (Any information below is purely informational)
    • Depends: w3m/s390x openssl
• waitress_pu (2.1.1-2 to 1.4.4-1.1+deb11u1)
  • Migration status for waitress_pu (2.1.1-2 to 1.4.4-1.1+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: waitress is newer in the target suite (2.1.1-2 1.4.4-1.1+deb11u1)
• watchman/amd64 (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/amd64 (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/amd64 openssl
• watchman/arm64 (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/arm64 (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/arm64 openssl
• watchman/armel (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/armel (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/armel openssl
• watchman/armhf (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/armhf (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/armhf openssl
• watchman/i386 (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/i386 (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/i386 openssl
• watchman/mips64el (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/mips64el (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/mips64el openssl
• watchman/mipsel (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/mipsel (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/mipsel openssl
• watchman/ppc64el (4.9.0-6 to 4.9.0-6)
  • Migration status for watchman/ppc64el (4.9.0-6 to 4.9.0-6): Will attempt migration (Any information below is purely informational)
    • Depends: watchman/ppc64el openssl
• weborf/amd64 (0.19-2 to 0.19-2)
  • Migration status for weborf/amd64 (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/amd64 openssl
• weborf/arm64 (0.19-2 to 0.19-2)
  • Migration status for weborf/arm64 (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/arm64 openssl
• weborf/armel (0.19-2 to 0.19-2)
  • Migration status for weborf/armel (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/armel openssl
• weborf/armhf (0.19-2 to 0.19-2)
  • Migration status for weborf/armhf (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/armhf openssl
• weborf/i386 (0.19-2 to 0.19-2)
  • Migration status for weborf/i386 (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/i386 openssl
• weborf/mips64el (0.19-2 to 0.19-2)
  • Migration status for weborf/mips64el (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/mips64el openssl
• weborf/mipsel (0.19-2 to 0.19-2)
  • Migration status for weborf/mipsel (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/mipsel openssl
• weborf/ppc64el (0.19-2 to 0.19-2)
  • Migration status for weborf/ppc64el (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/ppc64el openssl
• weborf/s390x (0.19-2 to 0.19-2)
  • Migration status for weborf/s390x (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
    • Depends: weborf/s390x openssl
• wesnoth-1.14/amd64 (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/amd64 (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/amd64 openssl
• wesnoth-1.14/arm64 (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/arm64 (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/arm64 openssl
• wesnoth-1.14/armel (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/armel (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/armel openssl
• wesnoth-1.14/armhf (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/armhf (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/armhf openssl
• wesnoth-1.14/i386 (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/i386 (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/i386 openssl
• wesnoth-1.14/mips64el (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/mips64el (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/mips64el openssl
• wesnoth-1.14/mipsel (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/mipsel (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/mipsel openssl
• wesnoth-1.14/ppc64el (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/ppc64el (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/ppc64el openssl
• wesnoth-1.14/s390x (1:1.14.17-2 to 1:1.14.17-2)
  • Migration status for wesnoth-1.14/s390x (1:1.14.17-2 to 1:1.14.17-2): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.14/s390x openssl
• wget/amd64 (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/amd64 (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/amd64 openssl
• wget/arm64 (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/arm64 (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/arm64 openssl
• wget/armel (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/armel (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/armel openssl
• wget/armhf (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/armhf (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/armhf openssl
• wget/i386 (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/i386 (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/i386 openssl
• wget/mips64el (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/mips64el (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/mips64el openssl
• wget/mipsel (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/mipsel (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/mipsel openssl
• wget/ppc64el (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/ppc64el (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/ppc64el openssl
• wget/s390x (1.21.3-1 to 1.21.3-1)
  • Migration status for wget/s390x (1.21.3-1 to 1.21.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wget/s390x openssl
• workflow/amd64 (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/amd64 (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/amd64 openssl
• workflow/arm64 (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/arm64 (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/arm64 openssl
• workflow/armel (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/armel (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/armel openssl
• workflow/armhf (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/armhf (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/armhf openssl
• workflow/i386 (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/i386 (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/i386 openssl
• workflow/mips64el (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/mips64el (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/mips64el openssl
• workflow/mipsel (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/mipsel (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/mipsel openssl
• workflow/ppc64el (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/ppc64el (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/ppc64el openssl
• workflow/s390x (0.9.10-1 to 0.9.10-1)
  • Migration status for workflow/s390x (0.9.10-1 to 0.9.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: workflow/s390x openssl
• wpa/amd64 (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/amd64 (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/amd64 openssl
• wpa/arm64 (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/arm64 (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/arm64 openssl
• wpa/armel (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/armel (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/armel openssl
• wpa/armhf (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/armhf (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/armhf openssl
• wpa/i386 (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/i386 (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/i386 openssl
• wpa/mips64el (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/mips64el (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/mips64el openssl
• wpa/mipsel (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/mipsel (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/mipsel openssl
• wpa/ppc64el (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/ppc64el (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/ppc64el openssl
• wpa/s390x (2:2.10-9 to 2:2.10-9)
  • Migration status for wpa/s390x (2:2.10-9 to 2:2.10-9): Will attempt migration (Any information below is purely informational)
    • Depends: wpa/s390x openssl
• wrk/amd64 (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/amd64 (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/amd64 openssl
• wrk/arm64 (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/arm64 (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/arm64 openssl
• wrk/armel (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/armel (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/armel openssl
• wrk/armhf (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/armhf (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/armhf openssl
• wrk/i386 (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/i386 (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/i386 openssl
• wrk/mips64el (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/mips64el (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/mips64el openssl
• wrk/mipsel (4.1.0-3 to 4.1.0-3)
  • Migration status for wrk/mipsel (4.1.0-3 to 4.1.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: wrk/mipsel openssl
• wvstreams/amd64 (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/amd64 (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/amd64 openssl
• wvstreams/arm64 (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/arm64 (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/arm64 openssl
• wvstreams/armel (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/armel (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/armel openssl
• wvstreams/armhf (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/armhf (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/armhf openssl
• wvstreams/i386 (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/i386 (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/i386 openssl
• wvstreams/mips64el (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/mips64el (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/mips64el openssl
• wvstreams/mipsel (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/mipsel (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/mipsel openssl
• wvstreams/ppc64el (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/ppc64el (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/ppc64el openssl
• wvstreams/s390x (4.6.1-15 to 4.6.1-15)
  • Migration status for wvstreams/s390x (4.6.1-15 to 4.6.1-15): Will attempt migration (Any information below is purely informational)
    • Depends: wvstreams/s390x openssl
• x11vnc/amd64 (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/amd64 (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/amd64 openssl
• x11vnc/arm64 (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/arm64 (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/arm64 openssl
• x11vnc/armel (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/armel (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/armel openssl
• x11vnc/armhf (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/armhf (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/armhf openssl
• x11vnc/i386 (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/i386 (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/i386 openssl
• x11vnc/mips64el (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/mips64el (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/mips64el openssl
• x11vnc/mipsel (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/mipsel (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/mipsel openssl
• x11vnc/ppc64el (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/ppc64el (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/ppc64el openssl
• x11vnc/s390x (0.9.16-8 to 0.9.16-8)
  • Migration status for x11vnc/s390x (0.9.16-8 to 0.9.16-8): Will attempt migration (Any information below is purely informational)
    • Depends: x11vnc/s390x openssl
• xca/amd64 (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/amd64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/amd64 openssl
• xca/arm64 (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/arm64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/arm64 openssl
• xca/armel (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/armel (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/armel openssl
• xca/armhf (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/armhf (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/armhf openssl
• xca/i386 (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/i386 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/i386 openssl
• xca/mips64el (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/mips64el (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/mips64el openssl
• xca/mipsel (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/mipsel (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/mipsel openssl
• xca/ppc64el (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/ppc64el (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/ppc64el openssl
• xca/s390x (2.4.0-2 to 2.4.0-2)
  • Migration status for xca/s390x (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: xca/s390x openssl
• xen_pu (4.16.1-1 to 4.14.4+74-gd7b22226b5-1)
  • Migration status for xen_pu (4.16.1-1 to 4.14.4+74-gd7b22226b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: xen is newer in the target suite (4.16.1-1 4.14.4+74-gd7b22226b5-1)
• xeus/amd64 (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/amd64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/amd64 openssl
• xeus/arm64 (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/arm64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/arm64 openssl
• xeus/armel (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/armel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/armel openssl
• xeus/armhf (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/armhf (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/armhf openssl
• xeus/i386 (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/i386 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/i386 openssl
• xeus/mips64el (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/mips64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/mips64el openssl
• xeus/mipsel (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/mipsel (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/mipsel openssl
• xeus/ppc64el (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/ppc64el (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/ppc64el openssl
• xeus/s390x (1.0.4-1 to 1.0.4-1)
  • Migration status for xeus/s390x (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xeus/s390x openssl
• xml-security-c/amd64 (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/amd64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/amd64 openssl
• xml-security-c/arm64 (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/arm64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/arm64 openssl
• xml-security-c/armel (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/armel (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/armel openssl
• xml-security-c/armhf (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/armhf (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/armhf openssl
• xml-security-c/i386 (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/i386 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/i386 openssl
• xml-security-c/mips64el (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/mips64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/mips64el openssl
• xml-security-c/mipsel (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/mipsel (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/mipsel openssl
• xml-security-c/ppc64el (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/ppc64el (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/ppc64el openssl
• xml-security-c/s390x (2.0.4-1 to 2.0.4-1)
  • Migration status for xml-security-c/s390x (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: xml-security-c/s390x openssl
• xmlsec1/amd64 (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/amd64 (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/amd64 openssl
• xmlsec1/arm64 (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/arm64 (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/arm64 openssl
• xmlsec1/armel (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/armel (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/armel openssl
• xmlsec1/armhf (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/armhf (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/armhf openssl
• xmlsec1/i386 (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/i386 (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/i386 openssl
• xmlsec1/mips64el (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/mips64el (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/mips64el openssl
• xmlsec1/mipsel (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/mipsel (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/mipsel openssl
• xmlsec1/ppc64el (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/ppc64el (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/ppc64el openssl
• xmlsec1/s390x (1.2.33-1 to 1.2.33-1)
  • Migration status for xmlsec1/s390x (1.2.33-1 to 1.2.33-1): Will attempt migration (Any information below is purely informational)
    • Depends: xmlsec1/s390x openssl
• xrootd/amd64 (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/amd64 (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/amd64 openssl
• xrootd/arm64 (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/arm64 (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/arm64 openssl
• xrootd/armel (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/armel (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/armel openssl
• xrootd/armhf (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/armhf (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/armhf openssl
• xrootd/i386 (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/i386 (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/i386 openssl
• xrootd/mips64el (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/mips64el (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/mips64el openssl
• xrootd/mipsel (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/mipsel (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/mipsel openssl
• xrootd/ppc64el (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/ppc64el (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/ppc64el openssl
• xrootd/s390x (5.4.2-2 to 5.4.2-2)
  • Migration status for xrootd/s390x (5.4.2-2 to 5.4.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: xrootd/s390x openssl
• xva-img/amd64 (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/amd64 (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/amd64 openssl
• xva-img/arm64 (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/arm64 (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/arm64 openssl
• xva-img/armel (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/armel (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/armel openssl
• xva-img/armhf (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/armhf (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/armhf openssl
• xva-img/i386 (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/i386 (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/i386 openssl
• xva-img/mips64el (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/mips64el (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/mips64el openssl
• xva-img/mipsel (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/mipsel (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/mipsel openssl
• xva-img/ppc64el (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/ppc64el (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/ppc64el openssl
• xva-img/s390x (1.4.2-1 to 1.4.2-1)
  • Migration status for xva-img/s390x (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: xva-img/s390x openssl
• xymon/amd64 (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/amd64 (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/amd64 openssl
• xymon/arm64 (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/arm64 (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/arm64 openssl
• xymon/armel (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/armel (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/armel openssl
• xymon/armhf (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/armhf (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/armhf openssl
• xymon/i386 (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/i386 (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/i386 openssl
• xymon/mips64el (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/mips64el (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/mips64el openssl
• xymon/mipsel (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/mipsel (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/mipsel openssl
• xymon/ppc64el (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/ppc64el (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/ppc64el openssl
• xymon/s390x (4.3.30-1 to 4.3.30-1)
  • Migration status for xymon/s390x (4.3.30-1 to 4.3.30-1): Will attempt migration (Any information below is purely informational)
    • Depends: xymon/s390x openssl
• xz-utils_pu (5.2.5-2.1 to 5.2.5-2.1~deb11u1)
  • Migration status for xz-utils_pu (5.2.5-2.1 to 5.2.5-2.1~deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: xz-utils is newer in the target suite (5.2.5-2.1 5.2.5-2.1~deb11u1)
• yafc/amd64 (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/amd64 (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/amd64 openssl
• yafc/arm64 (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/arm64 (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/arm64 openssl
• yafc/armel (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/armel (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/armel openssl
• yafc/armhf (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/armhf (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/armhf openssl
• yafc/i386 (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/i386 (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/i386 openssl
• yafc/mips64el (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/mips64el (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/mips64el openssl
• yafc/mipsel (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/mipsel (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/mipsel openssl
• yafc/ppc64el (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/ppc64el (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/ppc64el openssl
• yafc/s390x (1.3.7-4 to 1.3.7-4)
  • Migration status for yafc/s390x (1.3.7-4 to 1.3.7-4): Will attempt migration (Any information below is purely informational)
    • Depends: yafc/s390x openssl
• yapet/amd64 (2.6-1 to 2.6-1)
  • Migration status for yapet/amd64 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/amd64 openssl
• yapet/arm64 (2.6-1 to 2.6-1)
  • Migration status for yapet/arm64 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/arm64 openssl
• yapet/armel (2.6-1 to 2.6-1)
  • Migration status for yapet/armel (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/armel openssl
• yapet/armhf (2.6-1 to 2.6-1)
  • Migration status for yapet/armhf (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/armhf openssl
• yapet/i386 (2.6-1 to 2.6-1)
  • Migration status for yapet/i386 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/i386 openssl
• yapet/mips64el (2.6-1 to 2.6-1)
  • Migration status for yapet/mips64el (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/mips64el openssl
• yapet/mipsel (2.6-1 to 2.6-1)
  • Migration status for yapet/mipsel (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/mipsel openssl
• yapet/ppc64el (2.6-1 to 2.6-1)
  • Migration status for yapet/ppc64el (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/ppc64el openssl
• yapet/s390x (2.6-1 to 2.6-1)
  • Migration status for yapet/s390x (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
    • Depends: yapet/s390x openssl
• yara/amd64 (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/amd64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/amd64 openssl
• yara/arm64 (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/arm64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/arm64 openssl
• yara/armel (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/armel (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/armel openssl
• yara/armhf (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/armhf (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/armhf openssl
• yara/i386 (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/i386 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/i386 openssl
• yara/mips64el (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/mips64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/mips64el openssl
• yara/mipsel (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/mipsel (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/mipsel openssl
• yara/ppc64el (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/ppc64el (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/ppc64el openssl
• yara/s390x (4.2.1-1 to 4.2.1-1)
  • Migration status for yara/s390x (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: yara/s390x openssl
• ylva/amd64 (1.7-2 to 1.7-2)
  • Migration status for ylva/amd64 (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/amd64 openssl
• ylva/arm64 (1.7-2 to 1.7-2)
  • Migration status for ylva/arm64 (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/arm64 openssl
• ylva/armel (1.7-2 to 1.7-2)
  • Migration status for ylva/armel (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/armel openssl
• ylva/armhf (1.7-2 to 1.7-2)
  • Migration status for ylva/armhf (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/armhf openssl
• ylva/i386 (1.7-2 to 1.7-2)
  • Migration status for ylva/i386 (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/i386 openssl
• ylva/mips64el (1.7-2 to 1.7-2)
  • Migration status for ylva/mips64el (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/mips64el openssl
• ylva/mipsel (1.7-2 to 1.7-2)
  • Migration status for ylva/mipsel (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/mipsel openssl
• ylva/ppc64el (1.7-2 to 1.7-2)
  • Migration status for ylva/ppc64el (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/ppc64el openssl
• ylva/s390x (1.7-2 to 1.7-2)
  • Migration status for ylva/s390x (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
    • Depends: ylva/s390x openssl
• yuma123/amd64 (2.12-1 to 2.12-1)
  • Migration status for yuma123/amd64 (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/amd64 openssl
• yuma123/arm64 (2.12-1 to 2.12-1)
  • Migration status for yuma123/arm64 (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/arm64 openssl
• yuma123/armel (2.12-1 to 2.12-1)
  • Migration status for yuma123/armel (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/armel openssl
• yuma123/armhf (2.12-1 to 2.12-1)
  • Migration status for yuma123/armhf (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/armhf openssl
• yuma123/i386 (2.12-1 to 2.12-1)
  • Migration status for yuma123/i386 (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/i386 openssl
• yuma123/mips64el (2.12-1 to 2.12-1)
  • Migration status for yuma123/mips64el (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/mips64el openssl
• yuma123/mipsel (2.12-1 to 2.12-1)
  • Migration status for yuma123/mipsel (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/mipsel openssl
• yuma123/ppc64el (2.12-1 to 2.12-1)
  • Migration status for yuma123/ppc64el (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/ppc64el openssl
• yuma123/s390x (2.12-1 to 2.12-1)
  • Migration status for yuma123/s390x (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: yuma123/s390x openssl
• zeroc-ice/amd64 (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/amd64 (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/amd64 openssl
• zeroc-ice/arm64 (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/arm64 (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/arm64 openssl
• zeroc-ice/armel (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/armel (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/armel openssl
• zeroc-ice/armhf (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/armhf (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/armhf openssl
• zeroc-ice/i386 (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/i386 (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/i386 openssl
• zeroc-ice/mips64el (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/mips64el (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/mips64el openssl
• zeroc-ice/mipsel (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/mipsel (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/mipsel openssl
• zeroc-ice/ppc64el (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/ppc64el (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/ppc64el openssl
• zeroc-ice/s390x (3.7.7-1 to 3.7.7-1)
  • Migration status for zeroc-ice/s390x (3.7.7-1 to 3.7.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: zeroc-ice/s390x openssl
• zfs-fuse/amd64 (0.7.0-22 to 0.7.0-22)
  • Migration status for zfs-fuse/amd64 (0.7.0-22 to 0.7.0-22): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-fuse/amd64 openssl
• zfs-fuse/armel (0.7.0-22 to 0.7.0-22)
  • Migration status for zfs-fuse/armel (0.7.0-22 to 0.7.0-22): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-fuse/armel openssl
• zfs-fuse/armhf (0.7.0-22 to 0.7.0-22)
  • Migration status for zfs-fuse/armhf (0.7.0-22 to 0.7.0-22): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-fuse/armhf openssl
• zfs-fuse/i386 (0.7.0-22 to 0.7.0-22)
  • Migration status for zfs-fuse/i386 (0.7.0-22 to 0.7.0-22): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-fuse/i386 openssl
• zfs-fuse/ppc64el (0.7.0-22 to 0.7.0-22)
  • Migration status for zfs-fuse/ppc64el (0.7.0-22 to 0.7.0-22): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-fuse/ppc64el openssl
• zfs-linux/amd64 (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/amd64 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/amd64 openssl
• zfs-linux/arm64 (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/arm64 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/arm64 openssl
• zfs-linux/armel (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/armel (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/armel openssl
• zfs-linux/armhf (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/armhf (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/armhf openssl
• zfs-linux/i386 (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/i386 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/i386 openssl
• zfs-linux/mips64el (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/mips64el (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/mips64el openssl
• zfs-linux/mipsel (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/mipsel (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/mipsel openssl
• zfs-linux/ppc64el (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/ppc64el (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/ppc64el openssl
• zfs-linux/s390x (2.1.4-1 to 2.1.4-1)
  • Migration status for zfs-linux/s390x (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: zfs-linux/s390x openssl
• zlib_pu (1:1.2.11.dfsg-4 to 1:1.2.11.dfsg-2+deb11u1)
  • Migration status for zlib_pu (1:1.2.11.dfsg-4 to 1:1.2.11.dfsg-2+deb11u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: zlib is newer in the target suite (1:1.2.11.dfsg-4 1:1.2.11.dfsg-2+deb11u1)
• znc/amd64 (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/amd64 (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/amd64 openssl
• znc/arm64 (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/arm64 (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/arm64 openssl
• znc/armel (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/armel (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/armel openssl
• znc/armhf (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/armhf (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/armhf openssl
• znc/i386 (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/i386 (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/i386 openssl
• znc/mips64el (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/mips64el (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/mips64el openssl
• znc/mipsel (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/mipsel (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/mipsel openssl
• znc/ppc64el (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/ppc64el (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/ppc64el openssl
• znc/s390x (1.8.2-2 to 1.8.2-2)
  • Migration status for znc/s390x (1.8.2-2 to 1.8.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: znc/s390x openssl
• zurl/amd64 (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/amd64 (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/amd64 openssl
• zurl/arm64 (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/arm64 (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/arm64 openssl
• zurl/armel (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/armel (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/armel openssl
• zurl/armhf (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/armhf (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/armhf openssl
• zurl/i386 (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/i386 (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/i386 openssl
• zurl/mips64el (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/mips64el (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/mips64el openssl
• zurl/mipsel (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/mipsel (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/mipsel openssl
• zurl/ppc64el (1.11.1-1 to 1.11.1-1)
  • Migration status for zurl/ppc64el (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: zurl/ppc64el openssl
• apertium-eo-es (- to 1:0.9.2-1)
  • Migration status for apertium-eo-es (- to 1: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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-eo-es.html
• apertium-eu-es (- to 0.3.4-1)
  • Migration status for apertium-eu-es (- to 0.3.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/a/apertium-eu-es.html
• apertium-hbs-mkd (- to 0.1.1-1)
  • Migration status for apertium-hbs-mkd (- 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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-hbs-mkd.html
• apertium-oc-ca (- to 1.0.7-1)
  • Migration status for apertium-oc-ca (- to 1.0.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/a/apertium-oc-ca.html
• apertium-pt-gl (- to 0.9.3-1)
  • Migration status for apertium-pt-gl (- 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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-pt-gl.html
    • autopkgtest for apertium-pt-gl/0.9.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• btrfs-progs (5.17-1 to 5.18.1-1)
  • Migration status for btrfs-progs (5.17-1 to 5.18.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
    • Depends: btrfs-progs systemd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btrfs-progs.html
• byteman (4.0.18-1 to 4.0.19-1)
  • Migration status for byteman (4.0.18-1 to 4.0.19-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/b/byteman.html
• click (- to 0.5.0-6)
  • Migration status for click (- to 0.5.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating click would introduce bugs in testing: #1008904
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for click/0.5.0-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/click.html
• datalad-container (1.1.2-1 to 1.1.6-0.1)
  • Migration status for datalad-container (1.1.2-1 to 1.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 10 days old
  • Additional info:
    • Updating datalad-container will fix bugs in testing: #1009381
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datalad-container.html
• diffoscope (215 to 216)
  • Migration status for diffoscope (215 to 216): 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/diffoscope.html
    • autopkgtest for diffoscope/216: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for reprotest/0.7.20: amd64: Pass, arm64: Pass, armhf: Pass, i386: Ignored failure, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• django-invitations (- to 1.9.3-1)
  • Migration status for django-invitations (- to 1.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.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/d/django-invitations.html
    • autopkgtest for django-invitations/1.9.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• dnarrange (- to 1.5.2-1)
  • Migration status for dnarrange (- to 1.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnarrange.html
    • autopkgtest for dnarrange/1.5.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• eslint (6.4.0~dfsg+~6.1.9-5 to 6.4.0~dfsg+~6.1.9-7)
  • Migration status for eslint (6.4.0~dfsg+~6.1.9-5 to 6.4.0~dfsg+~6.1.9-7): 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): eslint node-v8-compile-cache
    • Depends: eslint node-v8-compile-cache
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eslint.html
    • autopkgtest for eslint/6.4.0~dfsg+~6.1.9-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• falcosecurity-libs (- to 0.1.1dev+git20220316.e5c53d64-1)
  • Migration status for falcosecurity-libs (- to 0.1.1dev+git20220316.e5c53d64-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/falcosecurity-libs.html
    • Not built on buildd: arch all binaries uploaded by dkogan, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by dkogan
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): falcosecurity-libs valijson
    • Depends: falcosecurity-libs openssl
• firebird3.0 (3.0.9.33560.ds4-3 to 3.0.10.33601.ds4-1)
  • Migration status for firebird3.0 (3.0.9.33560.ds4-3 to 3.0.10.33601.ds4-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/f/firebird3.0.html
    • autopkgtest for firebird3.0/3.0.10.33601.ds4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libreoffice/1:7.3.4~rc2-1: amd64: Pass, arm64: Pass, armhf: Ignored failure
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • Required age reduced by 3 days because of autopkgtest
• firefox (- to 101.0.1-1)
  • Migration status for firefox (- to 101.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1012275, #817954, #992263
    • firefox unsatisfiable Build-Depends(-Arch) on armhf: rustc (>= 1.59)
    • missing build on armhf
    • missing build on mips64el
    • missing build on mipsel
    • missing build on ppc64el
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): firefox rust-cbindgen
    • Build-Depends(-Arch): firefox rustc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
• firejail (0.9.68-3 to 0.9.70-1)
  • Migration status for firejail (0.9.68-3 to 0.9.70-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 firejail will fix bugs in testing: #1012510
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firejail.html
    • autopkgtest for firejail/0.9.70-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• flit-scm (- to 1.6.2-1)
  • Migration status for flit-scm (- to 1.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flit-scm.html
    • autopkgtest for flit-scm/1.6.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• fvwm3 (- to 1.0.4+ds-1)
  • Migration status for fvwm3 (- to 1.0.4+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kilobyte
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fvwm3.html
• geographiclib (2.0+ds-1 to 2.1-1)
  • Migration status for geographiclib (2.0+ds-1 to 2.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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geographiclib.html
• ghc (8.8.4-3 to 9.0.2-1)
  • Migration status for ghc (8.8.4-3 to 9.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ghc/9.0.2-1: amd64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for haskell-hopenpgp/2.9.5-1: amd64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on mipsel
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf 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/ghc.html
• gnome-calculator (1:42.0-3 to 1:42.1-1)
  • Migration status for gnome-calculator (1:42.0-3 to 1:42.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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-calculator.html
• golang-github-kurin-blazer (- to 0.5.3-1)
  • Migration status for golang-github-kurin-blazer (- to 0.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-kurin-blazer.html
    • autopkgtest for golang-github-kurin-blazer/0.5.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• grub2 (2.04-20 to 2.06-3)
  • Migration status for grub2 (2.04-20 to 2.06-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:
    • Updating grub2 will fix bugs in testing: #1005834, #997100
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub2.html
• indi-aagcloudwatcher-ng (1.6+20220128183230-1 to 1.6+20220610095218-1)
  • Migration status for indi-aagcloudwatcher-ng (1.6+20220128183230-1 to 1.6+20220610095218-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/indi-aagcloudwatcher-ng.html
• indi-aok (1.1+20220129131520-1 to 2.0+20220610095947-1)
  • Migration status for indi-aok (1.1+20220129131520-1 to 2.0+20220610095947-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/indi-aok.html
• indi-apogee (1.9+20220129131520-1 to 1.9+20220610100515-1)
  • Migration status for indi-apogee (1.9+20220129131520-1 to 1.9+20220610100515-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
    • Depends: indi-apogee libapogee3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/indi-apogee.html
• indi-armadillo-platypus (1.0+20220128183230-1 to 1.0+20220610100839-1)
  • Migration status for indi-armadillo-platypus (1.0+20220128183230-1 to 1.0+20220610100839-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/indi-armadillo-platypus.html
• indi-astrolink4 (0.1+20220128183230-1 to 0.1+20220610101327-1)
  • Migration status for indi-astrolink4 (0.1+20220128183230-1 to 0.1+20220610101327-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/indi-astrolink4.html
• indi-astromechfoc (0.2+20220128183230-1 to 0.2+20220610101747-1)
  • Migration status for indi-astromechfoc (0.2+20220128183230-1 to 0.2+20220610101747-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/indi-astromechfoc.html
• indi-avalon (1.12+20220128183230-1 to 1.12+20220610102819-1)
  • Migration status for indi-avalon (1.12+20220128183230-1 to 1.12+20220610102819-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/indi-avalon.html
• indi-playerone (0.4+20220129131520-1 to 0.5+20220610020920-1)
  • Migration status for indi-playerone (0.4+20220129131520-1 to 0.5+20220610020920-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
    • Depends: indi-playerone libplayerone
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• intel-gpu-tools (1.26-2 to 1.26+git20220524-1)
  • Migration status for intel-gpu-tools (1.26-2 to 1.26+git20220524-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/intel-gpu-tools.html
• jboss-modules (2.0.2-1 to 2.0.3-1)
  • Migration status for jboss-modules (2.0.2-1 to 2.0.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/j/jboss-modules.html
• jmol (14.32.57+dfsg-1 to 14.32.59+dfsg-2)
  • Migration status for jmol (14.32.57+dfsg-1 to 14.32.59+dfsg-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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jmol.html
• jupyter-client (7.3.1-1 to 7.3.4-1)
  • Migration status for jupyter-client (7.3.1-1 to 7.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ipyparallel/7.1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • autopkgtest for jupyter-client/7.3.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-client.html
• kdump-tools (1:1.6.10 to 1:1.7)
  • Migration status for kdump-tools (1:1.6.10 to 1:1.7): 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/kdump-tools.html
    • autopkgtest for kdump-tools/1:1.7: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• lamassemble (- to 1.4.2-3)
  • Migration status for lamassemble (- to 1.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lamassemble/1.4.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ , ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lamassemble.html
• libbiblio-thesaurus-perl (0.43-2.1 to 0.43-3)
  • Migration status for libbiblio-thesaurus-perl (0.43-2.1 to 0.43-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/libb/libbiblio-thesaurus-perl.html
    • autopkgtest for libbiblio-thesaurus-perl/0.43-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcache-mmap-perl (0.11-3 to 0.11-4)
  • Migration status for libcache-mmap-perl (0.11-3 to 0.11-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/libc/libcache-mmap-perl.html
    • autopkgtest for libcache-mmap-perl/0.11-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcache-perl (2.11-1.1 to 2.11-2)
  • Migration status for libcache-perl (2.11-1.1 to 2.11-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/libc/libcache-perl.html
    • autopkgtest for libcache-perl/2.11-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcal-dav-perl (0.6-3.1 to 0.6-4)
  • Migration status for libcal-dav-perl (0.6-3.1 to 0.6-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/libc/libcal-dav-perl.html
    • autopkgtest for libcal-dav-perl/0.6-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcam-pdf-perl (1.60-3 to 1.60-4)
  • Migration status for libcam-pdf-perl (1.60-3 to 1.60-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/libc/libcam-pdf-perl.html
    • autopkgtest for libcam-pdf-perl/1.60-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcanary-stability-perl (2006-2 to 2006-3)
  • Migration status for libcanary-stability-perl (2006-2 to 2006-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libcanary-stability-perl/2006-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcanary-stability-perl.html
• libcaptcha-recaptcha-perl (0.98+ds-1 to 0.98+ds-2)
  • Migration status for libcaptcha-recaptcha-perl (0.98+ds-1 to 0.98+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/libc/libcaptcha-recaptcha-perl.html
    • autopkgtest for libcaptcha-recaptcha-perl/0.98+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcarp-assert-perl (0.21-1.1 to 0.21-2)
  • Migration status for libcarp-assert-perl (0.21-1.1 to 0.21-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/libc/libcarp-assert-perl.html
    • autopkgtest for libcarp-assert-perl/0.21-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcarp-fix-1-25-perl (1.000001-2.1 to 1.000001-3)
  • Migration status for libcarp-fix-1-25-perl (1.000001-2.1 to 1.000001-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/libc/libcarp-fix-1-25-perl.html
    • autopkgtest for libcarp-fix-1-25-perl/1.000001-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-action-renderview-perl (0.16-2.1 to 0.16-3)
  • Migration status for libcatalyst-action-renderview-perl (0.16-2.1 to 0.16-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/libc/libcatalyst-action-renderview-perl.html
    • autopkgtest for libcatalyst-action-renderview-perl/0.16-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-action-rest-perl (1.21-1 to 1.21-2)
  • Migration status for libcatalyst-action-rest-perl (1.21-1 to 1.21-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/libc/libcatalyst-action-rest-perl.html
    • autopkgtest for libcatalyst-action-rest-perl/1.21-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-action-serialize-data-serializer-perl (1.08-2.1 to 1.08-3)
  • Migration status for libcatalyst-action-serialize-data-serializer-perl (1.08-2.1 to 1.08-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/libc/libcatalyst-action-serialize-data-serializer-perl.html
    • autopkgtest for libcatalyst-action-serialize-data-serializer-perl/1.08-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-authentication-credential-authen-simple-perl (0.09-3.1 to 0.09-4)
  • Migration status for libcatalyst-authentication-credential-authen-simple-perl (0.09-3.1 to 0.09-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/libc/libcatalyst-authentication-credential-authen-simple-perl.html
    • autopkgtest for libcatalyst-authentication-credential-authen-simple-perl/0.09-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-authentication-credential-http-perl (1.018-1 to 1.018-2)
  • Migration status for libcatalyst-authentication-credential-http-perl (1.018-1 to 1.018-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/libc/libcatalyst-authentication-credential-http-perl.html
    • autopkgtest for libcatalyst-authentication-credential-http-perl/1.018-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-authentication-store-dbix-class-perl (0.1506-4 to 0.1506-5)
  • Migration status for libcatalyst-authentication-store-dbix-class-perl (0.1506-4 to 0.1506-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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatalyst-authentication-store-dbix-class-perl.html
    • autopkgtest for libcatalyst-authentication-store-dbix-class-perl/0.1506-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-component-instancepercontext-perl (0.001001-2.1 to 0.001001-3)
  • Migration status for libcatalyst-component-instancepercontext-perl (0.001001-2.1 to 0.001001-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/libc/libcatalyst-component-instancepercontext-perl.html
    • autopkgtest for libcatalyst-component-instancepercontext-perl/0.001001-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-controller-formbuilder-perl (0.06-2.1 to 0.06-3)
  • Migration status for libcatalyst-controller-formbuilder-perl (0.06-2.1 to 0.06-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/libc/libcatalyst-controller-formbuilder-perl.html
    • autopkgtest for libcatalyst-controller-formbuilder-perl/0.06-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-dispatchtype-regex-perl (5.90035-1.1 to 5.90035-2)
  • Migration status for libcatalyst-dispatchtype-regex-perl (5.90035-1.1 to 5.90035-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/libc/libcatalyst-dispatchtype-regex-perl.html
    • autopkgtest for libcatalyst-dispatchtype-regex-perl/5.90035-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-model-adaptor-perl (0.10-2.1 to 0.10-3)
  • Migration status for libcatalyst-model-adaptor-perl (0.10-2.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatalyst-model-adaptor-perl.html
    • autopkgtest for libcatalyst-model-adaptor-perl/0.10-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-model-cdbi-crud-perl (0.04-3.1 to 0.04-4)
  • Migration status for libcatalyst-model-cdbi-crud-perl (0.04-3.1 to 0.04-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/libc/libcatalyst-model-cdbi-crud-perl.html
    • autopkgtest for libcatalyst-model-cdbi-crud-perl/0.04-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-model-dbi-perl (0.32-2.1 to 0.32-3)
  • Migration status for libcatalyst-model-dbi-perl (0.32-2.1 to 0.32-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/libc/libcatalyst-model-dbi-perl.html
    • autopkgtest for libcatalyst-model-dbi-perl/0.32-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-modules-extra-perl (9+nmu1 to 10)
  • Migration status for libcatalyst-modules-extra-perl (9+nmu1 to 10): 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/libcatalyst-modules-extra-perl.html
    • autopkgtest for libcatalyst-modules-extra-perl/10: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libcatalyst-modules-perl (48+nmu1 to 49)
  • Migration status for libcatalyst-modules-perl (48+nmu1 to 49): 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/libcatalyst-modules-perl.html
    • autopkgtest for libcatalyst-modules-perl/49: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libcatalyst-plugin-authentication-credential-openid-perl (0.03+rp-3.1 to 0.03+rp-4)
  • Migration status for libcatalyst-plugin-authentication-credential-openid-perl (0.03+rp-3.1 to 0.03+rp-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/libc/libcatalyst-plugin-authentication-credential-openid-perl.html
    • autopkgtest for libcatalyst-plugin-authentication-credential-openid-perl/0.03+rp-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-authorization-acl-perl (0.16-1.1 to 0.16-2)
  • Migration status for libcatalyst-plugin-authorization-acl-perl (0.16-1.1 to 0.16-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/libc/libcatalyst-plugin-authorization-acl-perl.html
    • autopkgtest for libcatalyst-plugin-authorization-acl-perl/0.16-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-cache-perl (0.12-2.1 to 0.12-3)
  • Migration status for libcatalyst-plugin-cache-perl (0.12-2.1 to 0.12-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/libc/libcatalyst-plugin-cache-perl.html
    • autopkgtest for libcatalyst-plugin-cache-perl/0.12-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-cache-store-fastmmap-perl (0.02-4 to 0.02-5)
  • Migration status for libcatalyst-plugin-cache-store-fastmmap-perl (0.02-4 to 0.02-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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatalyst-plugin-cache-store-fastmmap-perl.html
    • autopkgtest for libcatalyst-plugin-cache-store-fastmmap-perl/0.02-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-i18n-perl (0.10-3.1 to 0.10-4)
  • Migration status for libcatalyst-plugin-i18n-perl (0.10-3.1 to 0.10-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/libc/libcatalyst-plugin-i18n-perl.html
    • autopkgtest for libcatalyst-plugin-i18n-perl/0.10-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-log-dispatch-perl (0.121-2.1 to 0.121-3)
  • Migration status for libcatalyst-plugin-log-dispatch-perl (0.121-2.1 to 0.121-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/libc/libcatalyst-plugin-log-dispatch-perl.html
    • autopkgtest for libcatalyst-plugin-log-dispatch-perl/0.121-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-session-store-cache-perl (0.01-2.1 to 0.01-3)
  • Migration status for libcatalyst-plugin-session-store-cache-perl (0.01-2.1 to 0.01-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/libc/libcatalyst-plugin-session-store-cache-perl.html
    • autopkgtest for libcatalyst-plugin-session-store-cache-perl/0.01-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-session-store-dbic-perl (0.14-3.1 to 0.14-4)
  • Migration status for libcatalyst-plugin-session-store-dbic-perl (0.14-3.1 to 0.14-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/libc/libcatalyst-plugin-session-store-dbic-perl.html
    • autopkgtest for libcatalyst-plugin-session-store-dbic-perl/0.14-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-session-store-delegate-perl (0.06-2.1 to 0.06-3)
  • Migration status for libcatalyst-plugin-session-store-delegate-perl (0.06-2.1 to 0.06-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/libc/libcatalyst-plugin-session-store-delegate-perl.html
    • autopkgtest for libcatalyst-plugin-session-store-delegate-perl/0.06-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-session-store-fastmmap-perl (0.16-2.1 to 0.16-3)
  • Migration status for libcatalyst-plugin-session-store-fastmmap-perl (0.16-2.1 to 0.16-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/libc/libcatalyst-plugin-session-store-fastmmap-perl.html
    • autopkgtest for libcatalyst-plugin-session-store-fastmmap-perl/0.16-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-session-store-file-perl (0.18-2.1 to 0.18-3)
  • Migration status for libcatalyst-plugin-session-store-file-perl (0.18-2.1 to 0.18-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/libc/libcatalyst-plugin-session-store-file-perl.html
    • autopkgtest for libcatalyst-plugin-session-store-file-perl/0.18-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-setenv-perl (0.03-3.1 to 0.03-4)
  • Migration status for libcatalyst-plugin-setenv-perl (0.03-3.1 to 0.03-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/libc/libcatalyst-plugin-setenv-perl.html
    • autopkgtest for libcatalyst-plugin-setenv-perl/0.03-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-smarturi-perl (0.041-1 to 0.041-2)
  • Migration status for libcatalyst-plugin-smarturi-perl (0.041-1 to 0.041-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/libc/libcatalyst-plugin-smarturi-perl.html
    • autopkgtest for libcatalyst-plugin-smarturi-perl/0.041-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-stacktrace-perl (0.12-2.1 to 0.12-3)
  • Migration status for libcatalyst-plugin-stacktrace-perl (0.12-2.1 to 0.12-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/libc/libcatalyst-plugin-stacktrace-perl.html
    • autopkgtest for libcatalyst-plugin-stacktrace-perl/0.12-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-subrequest-perl (0.21-1.1 to 0.21-2)
  • Migration status for libcatalyst-plugin-subrequest-perl (0.21-1.1 to 0.21-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/libc/libcatalyst-plugin-subrequest-perl.html
    • autopkgtest for libcatalyst-plugin-subrequest-perl/0.21-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-plugin-unicode-perl (0.93-3.1 to 0.93-4)
  • Migration status for libcatalyst-plugin-unicode-perl (0.93-3.1 to 0.93-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/libc/libcatalyst-plugin-unicode-perl.html
    • autopkgtest for libcatalyst-plugin-unicode-perl/0.93-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-view-component-subinclude-perl (0.10-3 to 0.10-4)
  • Migration status for libcatalyst-view-component-subinclude-perl (0.10-3 to 0.10-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/libc/libcatalyst-view-component-subinclude-perl.html
    • autopkgtest for libcatalyst-view-component-subinclude-perl/0.10-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-view-email-perl (0.36-1 to 0.36-2)
  • Migration status for libcatalyst-view-email-perl (0.36-1 to 0.36-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/libc/libcatalyst-view-email-perl.html
    • autopkgtest for libcatalyst-view-email-perl/0.36-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalyst-view-mason-perl (0.19-1.1 to 0.19-2)
  • Migration status for libcatalyst-view-mason-perl (0.19-1.1 to 0.19-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/libc/libcatalyst-view-mason-perl.html
    • autopkgtest for libcatalyst-view-mason-perl/0.19-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalystx-component-traits-perl (0.19-2.1 to 0.19-3)
  • Migration status for libcatalystx-component-traits-perl (0.19-2.1 to 0.19-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/libc/libcatalystx-component-traits-perl.html
    • autopkgtest for libcatalystx-component-traits-perl/0.19-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatalystx-injectcomponent-perl (0.025-1.1 to 0.025-2)
  • Migration status for libcatalystx-injectcomponent-perl (0.025-1.1 to 0.025-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/libc/libcatalystx-injectcomponent-perl.html
    • autopkgtest for libcatalystx-injectcomponent-perl/0.025-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatmandu-mods-perl (0.31-1.1 to 0.31-2)
  • Migration status for libcatmandu-mods-perl (0.31-1.1 to 0.31-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/libc/libcatmandu-mods-perl.html
    • autopkgtest for libcatmandu-mods-perl/0.31-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatmandu-wikidata-perl (0.06-1.1 to 0.06-2)
  • Migration status for libcatmandu-wikidata-perl (0.06-1.1 to 0.06-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/libc/libcatmandu-wikidata-perl.html
    • autopkgtest for libcatmandu-wikidata-perl/0.06-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcatmandu-xml-perl (0.16-1.1 to 0.16-2)
  • Migration status for libcatmandu-xml-perl (0.16-1.1 to 0.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libcatmandu-xml-perl/0.16-2: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcatmandu-xml-perl.html
• libcdk-perl (20150928-1 to 20150928-2)
  • Migration status for libcdk-perl (20150928-1 to 20150928-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/libc/libcdk-perl.html
    • autopkgtest for libcdk-perl/20150928-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libcgi-ajax-perl (0.707-2 to 0.707-3)
  • Migration status for libcgi-ajax-perl (0.707-2 to 0.707-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/libc/libcgi-ajax-perl.html
    • autopkgtest for libcgi-ajax-perl/0.707-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-dispatch-perl (3.12-2.1 to 3.12-3)
  • Migration status for libcgi-application-dispatch-perl (3.12-2.1 to 3.12-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/libc/libcgi-application-dispatch-perl.html
    • autopkgtest for libcgi-application-dispatch-perl/3.12-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-actiondispatch-perl (0.99-2.1 to 0.99-3)
  • Migration status for libcgi-application-plugin-actiondispatch-perl (0.99-2.1 to 0.99-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/libc/libcgi-application-plugin-actiondispatch-perl.html
    • autopkgtest for libcgi-application-plugin-actiondispatch-perl/0.99-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-autorunmode-perl (0.18-2.1 to 0.18-3)
  • Migration status for libcgi-application-plugin-autorunmode-perl (0.18-2.1 to 0.18-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/libc/libcgi-application-plugin-autorunmode-perl.html
    • autopkgtest for libcgi-application-plugin-autorunmode-perl/0.18-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-captcha-perl (0.04-2.1 to 0.04-3)
  • Migration status for libcgi-application-plugin-captcha-perl (0.04-2.1 to 0.04-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/libc/libcgi-application-plugin-captcha-perl.html
    • autopkgtest for libcgi-application-plugin-captcha-perl/0.04-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-config-simple-perl (1.01-2.1 to 1.01-3)
  • Migration status for libcgi-application-plugin-config-simple-perl (1.01-2.1 to 1.01-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/libc/libcgi-application-plugin-config-simple-perl.html
    • autopkgtest for libcgi-application-plugin-config-simple-perl/1.01-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-configauto-perl (1.33-2.1 to 1.33-3)
  • Migration status for libcgi-application-plugin-configauto-perl (1.33-2.1 to 1.33-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/libc/libcgi-application-plugin-configauto-perl.html
    • autopkgtest for libcgi-application-plugin-configauto-perl/1.33-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-dbh-perl (4.04-2 to 4.04-3)
  • Migration status for libcgi-application-plugin-dbh-perl (4.04-2 to 4.04-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/libc/libcgi-application-plugin-dbh-perl.html
    • autopkgtest for libcgi-application-plugin-dbh-perl/4.04-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-dbiprofile-perl (0.07-2.1 to 0.07-3)
  • Migration status for libcgi-application-plugin-dbiprofile-perl (0.07-2.1 to 0.07-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/libc/libcgi-application-plugin-dbiprofile-perl.html
    • autopkgtest for libcgi-application-plugin-dbiprofile-perl/0.07-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-fillinform-perl (1.15-2.1 to 1.15-3)
  • Migration status for libcgi-application-plugin-fillinform-perl (1.15-2.1 to 1.15-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/libc/libcgi-application-plugin-fillinform-perl.html
    • autopkgtest for libcgi-application-plugin-fillinform-perl/1.15-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-formstate-perl (0.12-2.1 to 0.12-3)
  • Migration status for libcgi-application-plugin-formstate-perl (0.12-2.1 to 0.12-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/libc/libcgi-application-plugin-formstate-perl.html
    • autopkgtest for libcgi-application-plugin-formstate-perl/0.12-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-forward-perl (1.06-2.1 to 1.06-3)
  • Migration status for libcgi-application-plugin-forward-perl (1.06-2.1 to 1.06-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/libc/libcgi-application-plugin-forward-perl.html
    • autopkgtest for libcgi-application-plugin-forward-perl/1.06-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-json-perl (1.02-3.1 to 1.02-4)
  • Migration status for libcgi-application-plugin-json-perl (1.02-3.1 to 1.02-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/libc/libcgi-application-plugin-json-perl.html
    • autopkgtest for libcgi-application-plugin-json-perl/1.02-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-linkintegrity-perl (0.06-3.1 to 0.06-4)
  • Migration status for libcgi-application-plugin-linkintegrity-perl (0.06-3.1 to 0.06-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/libc/libcgi-application-plugin-linkintegrity-perl.html
    • autopkgtest for libcgi-application-plugin-linkintegrity-perl/0.06-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-logdispatch-perl (1.02-2.1 to 1.02-3)
  • Migration status for libcgi-application-plugin-logdispatch-perl (1.02-2.1 to 1.02-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/libc/libcgi-application-plugin-logdispatch-perl.html
    • autopkgtest for libcgi-application-plugin-logdispatch-perl/1.02-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-protectcsrf-perl (1.01-2.1 to 1.01-3)
  • Migration status for libcgi-application-plugin-protectcsrf-perl (1.01-2.1 to 1.01-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/libc/libcgi-application-plugin-protectcsrf-perl.html
    • autopkgtest for libcgi-application-plugin-protectcsrf-perl/1.01-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-ratelimit-perl (1.0-3.1 to 1.0-4)
  • Migration status for libcgi-application-plugin-ratelimit-perl (1.0-3.1 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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcgi-application-plugin-ratelimit-perl.html
    • autopkgtest for libcgi-application-plugin-ratelimit-perl/1.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-session-perl (1.05-2.1 to 1.05-3)
  • Migration status for libcgi-application-plugin-session-perl (1.05-2.1 to 1.05-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/libc/libcgi-application-plugin-session-perl.html
    • autopkgtest for libcgi-application-plugin-session-perl/1.05-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-stream-perl (2.12-1.1 to 2.12-2)
  • Migration status for libcgi-application-plugin-stream-perl (2.12-1.1 to 2.12-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/libc/libcgi-application-plugin-stream-perl.html
    • autopkgtest for libcgi-application-plugin-stream-perl/2.12-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-application-plugin-validaterm-perl (2.5-3.1 to 2.5-4)
  • Migration status for libcgi-application-plugin-validaterm-perl (2.5-3.1 to 2.5-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/libc/libcgi-application-plugin-validaterm-perl.html
    • autopkgtest for libcgi-application-plugin-validaterm-perl/2.5-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-compress-gzip-perl (1.03-2.1 to 1.03-3)
  • Migration status for libcgi-compress-gzip-perl (1.03-2.1 to 1.03-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/libc/libcgi-compress-gzip-perl.html
    • autopkgtest for libcgi-compress-gzip-perl/1.03-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-cookie-splitter-perl (0.05-2 to 0.05-3)
  • Migration status for libcgi-cookie-splitter-perl (0.05-2 to 0.05-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/libc/libcgi-cookie-splitter-perl.html
    • autopkgtest for libcgi-cookie-splitter-perl/0.05-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-emulate-psgi-perl (0.23-1 to 0.23-2)
  • Migration status for libcgi-emulate-psgi-perl (0.23-1 to 0.23-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/libc/libcgi-emulate-psgi-perl.html
    • autopkgtest for libcgi-emulate-psgi-perl/0.23-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-expand-perl (2.05-4 to 2.05-5)
  • Migration status for libcgi-expand-perl (2.05-4 to 2.05-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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcgi-expand-perl.html
    • autopkgtest for libcgi-expand-perl/2.05-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-formalware-perl (1.16-2.1 to 1.16-3)
  • Migration status for libcgi-formalware-perl (1.16-2.1 to 1.16-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/libc/libcgi-formalware-perl.html
    • autopkgtest for libcgi-formalware-perl/1.16-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcgi-formbuilder-source-yaml-perl (1.0.8-4.1 to 1.0.8-5)
  • Migration status for libcgi-formbuilder-source-yaml-perl (1.0.8-4.1 to 1.0.8-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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcgi-formbuilder-source-yaml-perl.html
    • autopkgtest for libcgi-formbuilder-source-yaml-perl/1.0.8-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libcloud (3.4.1-3 to 3.4.1-5)
  • Migration status for libcloud (3.4.1-3 to 3.4.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcloud would introduce bugs in testing: #1010214
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcloud.html
    • autopkgtest for libcloud/3.4.1-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libintl-perl (1.26-3 to 1.26-4)
  • Migration status for libintl-perl (1.26-3 to 1.26-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:
    • Updating libintl-perl will fix bugs in testing: #1012570
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libintl-perl.html
    • autopkgtest for libintl-perl/1.26-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libmojolicious-plugin-authentication-perl (1.37-1 to 1.38-1)
  • Migration status for libmojolicious-plugin-authentication-perl (1.37-1 to 1.38-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 libmojolicious-plugin-authentication-perl will fix bugs in testing: #1010972
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmojolicious-plugin-authentication-perl.html
    • autopkgtest for libmojolicious-plugin-authentication-perl/1.38-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• metalfinder (- to 2.1.2-1)
  • Migration status for metalfinder (- to 2.1.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch all binaries not found, 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/m/metalfinder.html
    • autopkgtest for metalfinder/2.1.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• modest (- to 0.0~git20210803.2540a03+ds-2)
  • Migration status for modest (- to 0.0~git20210803.2540a03+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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modest.html
• mpdscribble (0.23-1 to 0.24-1)
  • Migration status for mpdscribble (0.23-1 to 0.24-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/mpdscribble.html
• mwrap (1.0-3 to 1.1-1)
  • Migration status for mwrap (1.0-3 to 1.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 mwrap/1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mwrap.html
• natlog (2.04.02-1 to 3.00.00-1)
  • Migration status for natlog (2.04.02-1 to 3.00.00-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
    • Depends: natlog bobcat
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/natlog.html
• node-babel-polyfills (- to 0~20220520+ds1-5)
  • Migration status for node-babel-polyfills (- to 0~20220520+ds1-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/n/node-babel-polyfills.html
    • autopkgtest for node-babel-polyfills/0~20220520+ds1-5: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• node-browserslist (4.20.3+~cs5.1.5-1 to 4.20.4+~cs5.1.6-1)
  • Migration status for node-browserslist (4.20.3+~cs5.1.5-1 to 4.20.4+~cs5.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
    • Build-Depends(-Arch): node-browserslist node-caniuse-lite
    • Build-Depends(-Arch): node-browserslist node-electron-to-chromium
    • Depends: node-browserslist node-caniuse-lite
    • Depends: node-browserslist node-electron-to-chromium
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-browserslist.html
    • autopkgtest for node-browserslist/4.20.4+~cs5.1.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• node-caniuse-lite (1.0.30001334+dfsg+~1.0.1-1 to 1.0.30001352+dfsg+~1.0.1-1)
  • Migration status for node-caniuse-lite (1.0.30001334+dfsg+~1.0.1-1 to 1.0.30001352+dfsg+~1.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
    • Build-Depends(-Arch): node-caniuse-lite node-caniuse-db
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-caniuse-lite.html
    • autopkgtest for node-caniuse-lite/1.0.30001352+dfsg+~1.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• node-dommatrix (- to 1.0.3+dfsg-3)
  • Migration status for node-dommatrix (- to 1.0.3+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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-dommatrix.html
    • autopkgtest for node-dommatrix/1.0.3+dfsg-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• node-wikibase-edit (5.0.0-1 to 5.0.1-1)
  • Migration status for node-wikibase-edit (5.0.0-1 to 5.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/n/node-wikibase-edit.html
    • autopkgtest for node-wikibase-edit/5.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• nvidia-graphics-drivers (470.129.06-3 to 470.129.06-4)
  • Migration status for nvidia-graphics-drivers (470.129.06-3 to 470.129.06-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for nvidia-graphics-drivers/470.129.06-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results
• okteta (5:0.26.8-1 to 5:0.26.9-1)
  • Migration status for okteta (5:0.26.8-1 to 5:0.26.9-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/okteta.html
• open-infrastructure-service-tools (20220525-1 to 20220609-1)
  • Migration status for open-infrastructure-service-tools (20220525-1 to 20220609-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/open-infrastructure-service-tools.html
• pipewire (0.3.51-1 to 0.3.52-1)
  • Migration status for pipewire (0.3.51-1 to 0.3.52-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
    • Depends: pipewire openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pipewire.html
    • autopkgtest for pipewire/0.3.52-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• pkg-perl-tools (0.69 to 0.70)
  • Migration status for pkg-perl-tools (0.69 to 0.70): 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/pkg-perl-tools.html
    • autopkgtest for pkg-perl-tools/0.70: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• poedit (3.0.1-1 to 3.1-1)
  • Migration status for poedit (3.0.1-1 to 3.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
    • Too young, only 1 of 5 days old
    • Depends: poedit openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poedit.html
• promod3 (- to 3.2.1+ds-4)
  • Migration status for promod3 (- to 3.2.1+ds-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/p/promod3.html
• prosody (0.12.0-1 to 0.12.1-1)
  • Migration status for prosody (0.12.0-1 to 0.12.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
    • Depends: prosody openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prosody.html
• psd-tools (- to 1.9.20+dfsg.1-1)
  • Migration status for psd-tools (- to 1.9.20+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for psd-tools/1.9.20+dfsg.1-1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by paulliu
    • 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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psd-tools.html
• pugl (0~svn32+dfsg0-3 to 0~svn32+dfsg0-4)
  • Migration status for pugl (0~svn32+dfsg0-3 to 0~svn32+dfsg0-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/p/pugl.html
• pyiosxr (0.52-1.1 to 0.52-2)
  • Migration status for pyiosxr (0.52-1.1 to 0.52-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/p/pyiosxr.html
• pytest-runner (2.11.1-1.2 to 2.11.1-2)
  • Migration status for pytest-runner (2.11.1-1.2 to 2.11.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/p/pytest-runner.html
• python-asdf (2.11.1-1 to 2.12.0-1)
  • Migration status for python-asdf (2.11.1-1 to 2.12.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/python-asdf.html
    • autopkgtest for python-asdf/2.12.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• python-kanboard (1.0.1-1.1 to 1.0.1-2)
  • Migration status for python-kanboard (1.0.1-1.1 to 1.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-kanboard.html
• python-openidc-client (0.6.0-1.1 to 0.6.0-2)
  • Migration status for python-openidc-client (0.6.0-1.1 to 0.6.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/p/python-openidc-client.html
    • autopkgtest for python-openidc-client/0.6.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-pex (- to 1.1.14-4)
  • Migration status for python-pex (- to 1.1.14-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pex would introduce bugs in testing: #1002185
    • 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/p/python-pex.html
• python-py-zipkin (0.15.0-1.1 to 0.15.0-2)
  • Migration status for python-py-zipkin (0.15.0-1.1 to 0.15.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/p/python-py-zipkin.html
• python-pysnmp4-apps (0.3.2-2.2 to 0.3.2-3)
  • Migration status for python-pysnmp4-apps (0.3.2-2.2 to 0.3.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pysnmp4-apps.html
• python-requests-ntlm (1.1.0-1.1 to 1.1.0-2)
  • Migration status for python-requests-ntlm (1.1.0-1.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-requests-ntlm.html
• python-rpaths (0.13-1.1 to 0.13-2)
  • Migration status for python-rpaths (0.13-1.1 to 0.13-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-rpaths.html
    • autopkgtest for python-rpaths/0.13-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• python-typeguard (2.2.2-1.1 to 2.2.2-2)
  • Migration status for python-typeguard (2.2.2-1.1 to 2.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-typeguard.html
    • autopkgtest for python-typeguard/2.2.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-vertica (1.0.5-4 to 1.1.0-1)
  • Migration status for python-vertica (1.0.5-4 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-vertica/1.1.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Test in progress
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-webob (1:1.8.6-1.1 to 1:1.8.6-2)
  • Migration status for python-webob (1:1.8.6-1.1 to 1:1.8.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-webob.html
• python-xarray (2022.03.0-2 to 2022.06.0~rc1-1)
  • Migration status for python-xarray (2022.03.0-2 to 2022.06.0~rc1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-xarray/2022.06.0~rc1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Not a regression, ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xarray.html
• python-yaswfp (0.9.3-1.1 to 0.9.3-2)
  • Migration status for python-yaswfp (0.9.3-1.1 to 0.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-yaswfp.html
    • autopkgtest for python-yaswfp/0.9.3-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python3.11 (- to 3.11.0~b3-2)
  • Migration status for python3.11 (- to 3.11.0~b3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python3.11/3.11.0~b3-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 1 of 5 days old
    • Depends: python3.11 openssl
    • Depends: python3.11 python3-stdlib-extensions
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.11.html
• qt6-serialbus (6.2.4-2 to 6.2.4-3)
  • Migration status for qt6-serialbus (6.2.4-2 to 6.2.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt6-serialbus.html
• qtpim-opensource-src (5.0~git20190618.8fec622c+dfsg1-10 to 5.0~git20201102.f9a8f0fc+dfsg1-2)
  • Migration status for qtpim-opensource-src (5.0~git20190618.8fec622c+dfsg1-10 to 5.0~git20201102.f9a8f0fc+dfsg1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • missing build on ppc64el
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el 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/q/qtpim-opensource-src.html
• rust-coreutils (- to 0.0.14-2)
  • Migration status for rust-coreutils (- to 0.0.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
    • Build-Depends(-Arch): rust-coreutils rust-dns-lookup
    • Build-Depends(-Arch): rust-coreutils rust-exacl
    • Build-Depends(-Arch): rust-coreutils rust-fs-extra
    • Build-Depends(-Arch): rust-coreutils rust-ioctl-sys
    • Build-Depends(-Arch): rust-coreutils rust-md-5
    • Build-Depends(-Arch): rust-coreutils rust-os-display
    • Build-Depends(-Arch): rust-coreutils rust-ouroboros
    • Build-Depends(-Arch): rust-coreutils rust-termsize
    • Build-Depends(-Arch): rust-coreutils rust-time
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-coreutils.html
• rust-exacl (0.8.0-1 to 0.9.0-1)
  • Migration status for rust-exacl (0.8.0-1 to 0.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 5 days old
    • Depends: rust-exacl rust-bindgen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-exacl.html
    • autopkgtest for rust-exacl/0.9.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rust-nix (0.23.1-1 to 0.24.1-2)
  • Migration status for rust-nix (0.23.1-1 to 0.24.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ctrlc/3.2.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-nix/0.24.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Not built on buildd: upload info for arch mipsel binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
    • Too young, only 1 of 5 days old
    • Implicit dependency: rust-nix rust-alacritty-terminal
    • Implicit dependency: rust-nix rust-ctrlc
    • Implicit dependency: rust-nix rust-libmount
    • Implicit dependency: rust-nix rust-sniffglue
    • Implicit dependency: rust-nix rust-vsock
    • Implicit dependency: rust-nix rust-wayland-client
    • Implicit dependency: rust-nix rust-wayland-commons
    • Implicit dependency: rust-nix rust-wayland-cursor
    • Implicit dependency: rust-nix rust-wayland-server
    • Implicit dependency: rust-nix rust-x11rb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nix.html
• rust-proptest (0.9.6-2 to 0.9.6-3)
  • Migration status for rust-proptest (0.9.6-2 to 0.9.6-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
    • Build-Depends(-Arch): rust-proptest rust-quick-error
    • Depends: rust-proptest rust-quick-error
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proptest.html
    • autopkgtest for rust-proptest/0.9.6-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• rust-vsock (0.2.4-2 to 0.2.4-3)
  • Migration status for rust-vsock (0.2.4-2 to 0.2.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
    • Build-Depends(-Arch): rust-vsock rust-nix
    • Depends: rust-vsock rust-nix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-vsock.html
    • autopkgtest for rust-vsock/0.2.4-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rust-wayland-client (0.29.4-1 to 0.29.4-2)
  • Migration status for rust-wayland-client (0.29.4-1 to 0.29.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/r/rust-wayland-client.html
    • autopkgtest for rust-wayland-client/0.29.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• rust-wayland-commons (0.29.4-1 to 0.29.4-2)
  • Migration status for rust-wayland-commons (0.29.4-1 to 0.29.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
    • Build-Depends(-Arch): rust-wayland-commons rust-nix
    • Depends: rust-wayland-commons rust-nix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wayland-commons.html
    • autopkgtest for rust-wayland-commons/0.29.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• rust-wayland-cursor (0.29.4-1 to 0.29.4-2)
  • Migration status for rust-wayland-cursor (0.29.4-1 to 0.29.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/r/rust-wayland-cursor.html
    • autopkgtest for rust-wayland-cursor/0.29.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• rust-wayland-server (0.29.4-1 to 0.29.4-2)
  • Migration status for rust-wayland-server (0.29.4-1 to 0.29.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/r/rust-wayland-server.html
    • autopkgtest for rust-wayland-server/0.29.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• rust-x11rb (0.8.1-3 to 0.8.1-4)
  • Migration status for rust-x11rb (0.8.1-3 to 0.8.1-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
    • Build-Depends(-Arch): rust-x11rb rust-nix
    • Depends: rust-x11rb rust-nix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-x11rb.html
    • autopkgtest for rust-x11rb/0.8.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• schroot (1.6.10-13 to 1.6.10-15)
  • Migration status for schroot (1.6.10-13 to 1.6.10-15): 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/schroot.html
• service-wrapper-java (3.5.30-3 to 3.5.50-2)
  • Migration status for service-wrapper-java (3.5.30-3 to 3.5.50-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/service-wrapper-java.html
• sphinx-autorun (1.1.0-3.1 to 1.1.0-4)
  • Migration status for sphinx-autorun (1.1.0-3.1 to 1.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-autorun.html
• sphinxcontrib-mermaid (- to 0.7.1-1)
  • Migration status for sphinxcontrib-mermaid (- 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 tincho, 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/s/sphinxcontrib-mermaid.html
    • autopkgtest for sphinxcontrib-mermaid/0.7.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• sshpubkeys (3.1.0-2.1 to 3.1.0-3)
  • Migration status for sshpubkeys (3.1.0-2.1 to 3.1.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/s/sshpubkeys.html
    • autopkgtest for sshpubkeys/3.1.0-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• symmetrica (2.0+ds-6 to 3.0.1+ds-2)
  • Migration status for symmetrica (2.0+ds-6 to 3.0.1+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/s/symmetrica.html
    • autopkgtest for symmetrica/3.0.1+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• systemd (250.4-1 to 251.2-4)
  • Migration status for systemd (250.4-1 to 251.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for kodi/2:19.4+dfsg2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for libsdl2/2.0.22+dfsg-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Regression ♻ (reference ♻)
    • autopkgtest for netplan.io/0.103-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for openssh/1:9.0p1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for postgresql-14/14.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-exporter-exporter/0.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-ipmi-exporter/1.5.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-libvirt-exporter/0.2.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-mqtt-exporter/0.1.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-postfix-exporter/0.3.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-postgres-exporter/0.10.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for prometheus-squid-exporter/1.10.3+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for pulseaudio/15.0+dfsg1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for puppet/5.5.22-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for pystemd/0.7.0-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for python-dbusmock/0.27.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for python-systemd/234-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for python-uinput/0.11.2-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for pyudev/0.22.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for qemu/1:7.0+dfsg-7: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for qlcplus/4.12.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for redis/5:6.0.16-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for remctl/3.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rpcbind/1.2.6-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rtkit/0.13-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for runit/2.1.2-45: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for rust-whoami/0.8.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for samba/2:4.16.1+dfsg-8: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for seatd/0.7.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for shibboleth-sp/3.3.0+dfsg1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for sks/1.1.6+git20210302.c3ba6d5a-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for smcroute/2.5.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for snapd/2.54.3-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for solid/5.94.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for spice-vdagent/0.22.1-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for squid/5.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for sssd/2.6.3-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for strongswan/5.9.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for suricata/1:6.0.5-3: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for swupdate/2021.11-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for syslog-ng/3.35.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for systemd/251.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for systemd-bootchart/234-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for tang/11-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for tgt/1:1.0.80-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for tinyssh/20220311-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for tor/0.4.7.7-1: amd64: Pass, arm64: Not a regression, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for tpm2-abrmd/2.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for udisks2/2.9.4-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for upower/0.99.18-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for usbauth/1.0.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for util-linux/2.38-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Not a regression, s390x: Test in progress
    • autopkgtest for vlc/3.0.17.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for vte2.91/0.68.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for webhook/2.8.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for wireplumber/0.4.10-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for wireshark/3.6.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for wlroots/0.15.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for xdg-desktop-portal/1.14.4-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Test in progress
    • autopkgtest for yder/1.4.17-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for zfs-linux/2.1.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 1 of 5 days old
    • Depends: systemd libselinux
    • Depends: systemd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systemd.html
• tifffile (20220428-2 to 20220504-1)
  • Migration status for tifffile (20220428-2 to 20220504-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for pyscanfcs/0.3.6+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for skimage/0.18.3-3: amd64: Pass, arm64: Pass, armhf: Ignored failure, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for tifffile/20220504-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tifffile.html
• tmux (3.3-2 to 3.3a-1)
  • Migration status for tmux (3.3-2 to 3.3a-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/t/tmux.html
    • autopkgtest for tmux/3.3a-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• tmuxinator (3.0.4-1 to 3.0.5-1)
  • Migration status for tmuxinator (3.0.4-1 to 3.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmuxinator.html
    • autopkgtest for tmuxinator/3.0.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• trace-cmd (3.0.3-3 to 3.1-1)
  • Migration status for trace-cmd (3.0.3-3 to 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 5 days old
    • Depends: trace-cmd libtracefs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trace-cmd.html
    • autopkgtest for trace-cmd/3.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• trafficserver (9.1.2+ds-1 to 9.1.2+ds-9)
  • Migration status for trafficserver (9.1.2+ds-1 to 9.1.2+ds-9): 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): trafficserver luajit2
    • Depends: trafficserver openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
• ts-node (10.7.0+~cs7.0.20-3 to 10.8.1+~cs7.8.22-2)
  • Migration status for ts-node (10.7.0+~cs7.0.20-3 to 10.8.1+~cs7.8.22-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/t/ts-node.html
    • autopkgtest for ts-node/10.8.1+~cs7.8.22-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• unifont (1:14.0.03-1 to 1:14.0.04-1)
  • Migration status for unifont (1:14.0.03-1 to 1:14.0.04-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/u/unifont.html
• upower (0.99.18-3 to 0.99.19-1)
  • Migration status for upower (0.99.18-3 to 0.99.19-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/u/upower.html
    • autopkgtest for upower/0.99.19-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• vim-youcompleteme (0+20200825+git2afee9d+ds-2 to 0+20220402+git3ededae+ds-1)
  • Migration status for vim-youcompleteme (0+20200825+git2afee9d+ds-2 to 0+20220402+git3ededae+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vim-youcompleteme/0+20220402+git3ededae+ds-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Regression ♻
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): vim-youcompleteme ycmd
    • Depends: vim-youcompleteme ycmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-youcompleteme.html
• wokkel (18.0.0-3.1 to 18.0.0-4)
  • Migration status for wokkel (18.0.0-3.1 to 18.0.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/w/wokkel.html
    • autopkgtest for wokkel/18.0.0-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• wsgiproxy2 (0.4.5-1.1 to 0.5.1-1)
  • Migration status for wsgiproxy2 (0.4.5-1.1 to 0.5.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/w/wsgiproxy2.html
    • autopkgtest for wsgiproxy2/0.5.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• wyrd (1.5.4-1 to 1.5.5-1)
  • Migration status for wyrd (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:
    • autopkgtest for wyrd/1.5.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wyrd.html
• xfsprogs (5.16.0-1 to 5.18.0-1)
  • Migration status for xfsprogs (5.16.0-1 to 5.18.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/x/xfsprogs.html
• ycmd (0+20201028+git1d415c5+ds-1 to 0+20220401+gitdbe806f+ds-1)
  • Migration status for ycmd (0+20201028+git1d415c5+ds-1 to 0+20220401+gitdbe806f+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ycmd/0+20220401+gitdbe806f+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
    • Too young, only 1 of 5 days old
    • Implicit dependency: ycmd vim-youcompleteme
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ycmd.html
• alpine (2.25+dfsg1-1 to 2.26+dfsg-1)
  • Migration status for alpine (2.25+dfsg1-1 to 2.26+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
    • Depends: alpine openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alpine.html
• apache2 (2.4.53-2 to 2.4.54-1)
  • Migration status for apache2 (2.4.53-2 to 2.4.54-1): Will attempt migration (Any information below is purely informational)
    • Depends: apache2 openssl
  • Additional info:
    • Updating apache2 will fix bugs in testing: #1012513
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apache2.html
    • autopkgtest for apache2/2.4.54-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• bats (1.2.1-3 to 1.7.0-0.1)
  • Migration status for bats (1.2.1-3 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bats.html
• bootcd (6.6 to 6.6.1)
  • Migration status for bootcd (6.6 to 6.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/b/bootcd.html
• bzflag (2.4.22-1 to 2.4.24-1)
  • Migration status for bzflag (2.4.22-1 to 2.4.24-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/bzflag.html
• clonezilla (5.1.7-1 to 5.1.10-1)
  • Migration status for clonezilla (5.1.7-1 to 5.1.10-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/clonezilla.html
• cockpit (269-1 to 271-1)
  • Migration status for cockpit (269-1 to 271-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cockpit.html
    • autopkgtest for cockpit/271-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• cockpit-machines (268-1 to 270.1-1)
  • Migration status for cockpit-machines (268-1 to 270.1-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/cockpit-machines.html
• cockpit-podman (46-1 to 49.1-1)
  • Migration status for cockpit-podman (46-1 to 49.1-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/cockpit-podman.html
• cpp-httplib (0.10.6+ds-1 to 0.10.8+ds-1)
  • Migration status for cpp-httplib (0.10.6+ds-1 to 0.10.8+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: cpp-httplib openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpp-httplib.html
    • autopkgtest for cpp-httplib/0.10.8+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• cron (3.0pl1-139 to 3.0pl1-143)
  • Migration status for cron (3.0pl1-139 to 3.0pl1-143): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cron would introduce bugs in testing: #1012596
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cron.html
    • autopkgtest for cron/3.0pl1-143: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• datalad (0.16.3-1 to 0.16.5-1)
  • Migration status for datalad (0.16.3-1 to 0.16.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/d/datalad.html
• dazzdb (1.0+git20201103.8d98c37-1.1 to 1.0+git20220426.8a55f0e-1)
  • Migration status for dazzdb (1.0+git20201103.8d98c37-1.1 to 1.0+git20220426.8a55f0e-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/d/dazzdb.html
    • autopkgtest for dazzdb/1.0+git20220426.8a55f0e-1: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Not a regression, ppc64el: Pass, s390x: Not a regression
• debmutate (0.50 to 0.53)
  • Migration status for debmutate (0.50 to 0.53): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debmutate would introduce bugs in testing: #1012505
    • autopkgtest for debmutate/0.53: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for lintian-brush/0.126: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debmutate.html
• devpi-common (3.2.2-1.1 to 3.2.2-2)
  • Migration status for devpi-common (3.2.2-1.1 to 3.2.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devpi-common.html
    • autopkgtest for devpi-common/3.2.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• django-hvad (1.8.0-1.1 to 1.8.0-2)
  • Migration status for django-hvad (1.8.0-1.1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-hvad.html
• dopewars (1.5.12-19 to 1.6.1-1)
  • Migration status for dopewars (1.5.12-19 to 1.6.1-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/d/dopewars.html
• drumkv1 (0.9.25-1 to 0.9.26-1)
  • Migration status for drumkv1 (0.9.25-1 to 0.9.26-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/d/drumkv1.html
    • autopkgtest for drumkv1/0.9.26-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• erlang (1:24.3.4+dfsg-1 to 1:24.3.4.1+dfsg-1)
  • Migration status for erlang (1:24.3.4+dfsg-1 to 1:24.3.4.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 2 of 5 days old
    • Depends: erlang openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang.html
    • autopkgtest for sonic-pi/3.2.2~repack-7: amd64: Pass, arm64: Pass, armhf: Ignored failure, i386: Pass, ppc64el: Not a regression, s390x: Not a regression
• ettercap (- to 1:0.8.3.1-9)
  • Migration status for ettercap (- to 1:0.8.3.1-9): 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): ettercap luajit
    • Depends: ettercap luajit
    • Depends: ettercap openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ettercap.html
• exabgp (4.2.18-1 to 4.2.19-1)
  • Migration status for exabgp (4.2.18-1 to 4.2.19-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/e/exabgp.html
• flac (1.3.4-1 to 1.3.4-2)
  • Migration status for flac (1.3.4-1 to 1.3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for supysonic/0.7.2+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating flac will fix bugs in testing: #1008424
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flac.html
• flask-api (1.1+dfsg-1.1 to 1.1+dfsg-2)
  • Migration status for flask-api (1.1+dfsg-1.1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-api.html
• flask-ldapconn (0.7.2-1.1 to 0.7.2-2)
  • Migration status for flask-ldapconn (0.7.2-1.1 to 0.7.2-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/f/flask-ldapconn.html
    • autopkgtest for flask-ldapconn/0.7.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• flask-mail (0.9.1+dfsg1-1.1 to 0.9.1+dfsg1-2)
  • Migration status for flask-mail (0.9.1+dfsg1-1.1 to 0.9.1+dfsg1-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/f/flask-mail.html
    • autopkgtest for flask-mail/0.9.1+dfsg1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• gdome2 (0.8.1+debian-7 to 0.8.1+debian-8)
  • Migration status for gdome2 (0.8.1+debian-7 to 0.8.1+debian-8): 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/gdome2.html
• golang-github-containers-buildah (1.23.1+ds1-2 to 1.23.1+ds1-3)
  • Migration status for golang-github-containers-buildah (1.23.1+ds1-2 to 1.23.1+ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: golang-github-containers-buildah golang-github-openshift-imagebuilder (not considered)
    • Invalidated by built-using
    • Built-Using: golang-github-containers-buildah golang-github-opencontainers-runtime-tools
  • Additional info:
    • Updating golang-github-containers-buildah will fix bugs in testing: #1011869
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-buildah.html
    • autopkgtest for golang-github-containers-buildah/1.23.1+ds1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-la5nta-wl2k-go (0.9.2-1 to 0.10.0-1)
  • Migration status for golang-github-la5nta-wl2k-go (0.9.2-1 to 0.10.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-la5nta-wl2k-go.html
    • autopkgtest for golang-github-la5nta-wl2k-go/0.10.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-opencontainers-runtime-tools (0.9.0+git20220423.g0105384-1 to 0.9.0+git20220423.g0105384-2)
  • Migration status for golang-github-opencontainers-runtime-tools (0.9.0+git20220423.g0105384-1 to 0.9.0+git20220423.g0105384-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating golang-github-opencontainers-runtime-tools will fix bugs in testing: #1011875
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-opencontainers-runtime-tools.html
    • autopkgtest for golang-github-opencontainers-runtime-tools/0.9.0+git20220423.g0105384-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-tdewolff-minify (2.11.2-1 to 2.11.5-1)
  • Migration status for golang-github-tdewolff-minify (2.11.2-1 to 2.11.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tdewolff-minify.html
    • autopkgtest for golang-github-tdewolff-minify/2.11.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• guix (1.3.0-4 to 1.3.0-5)
  • Migration status for guix (1.3.0-4 to 1.3.0-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on i386
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating guix will fix bugs in testing: #1011863
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guix.html
• htmldoc (1.9.15-2 to 1.9.16-1)
  • Migration status for htmldoc (1.9.15-2 to 1.9.16-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/htmldoc.html
• hugo (0.96.0-1 to 0.100.1-1)
  • Migration status for hugo (0.96.0-1 to 0.100.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hugo golang-github-bep-overlayfs (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): hugo golang-github-bep-clock
    • Build-Depends(-Arch): hugo golang-github-tdewolff-minify
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hugo.html
    • autopkgtest for hugo/0.100.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• hyperrogue (12.0f-1 to 12.0q-1)
  • Migration status for hyperrogue (12.0f-1 to 12.0q-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/hyperrogue.html
• indi-asi (2.0-3 to 2.2+20220609111143-1)
  • Migration status for indi-asi (2.0-3 to 2.2+20220609111143-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)
• iproute2 (5.17.0-2 to 5.18.0-1)
  • Migration status for iproute2 (5.17.0-2 to 5.18.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/i/iproute2.html
    • autopkgtest for iproute2/5.18.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• jwm (2.4.1-1 to 2.4.2-1)
  • Migration status for jwm (2.4.1-1 to 2.4.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/j/jwm.html
• libapp-control-perl (1.02-3 to 1.02-4)
  • Migration status for libapp-control-perl (1.02-3 to 1.02-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-control-perl.html
    • autopkgtest for libapp-control-perl/1.02-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libapp-cpants-lint-perl (0.05-5.1 to 0.05-6)
  • Migration status for libapp-cpants-lint-perl (0.05-5.1 to 0.05-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-cpants-lint-perl.html
    • autopkgtest for libapp-cpants-lint-perl/0.05-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libapp-options-perl (1.12-2 to 1.12-3)
  • Migration status for libapp-options-perl (1.12-2 to 1.12-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-options-perl.html
    • autopkgtest for libapp-options-perl/1.12-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libapp-perlrdf-command-query-perl (- to 0.004-3)
  • Migration status for libapp-perlrdf-command-query-perl (- to 0.004-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libapp-perlrdf-command-query-perl perlrdf (not considered)
    • Depends: libapp-perlrdf-command-query-perl perlrdf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-perlrdf-command-query-perl.html
    • autopkgtest for libapp-perlrdf-command-query-perl/0.004-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libapp-rad-perl (1.05-2 to 1.05-3)
  • Migration status for libapp-rad-perl (1.05-2 to 1.05-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-rad-perl.html
    • autopkgtest for libapp-rad-perl/1.05-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libapp-stacktrace-perl (0.09-3 to 0.09-4)
  • Migration status for libapp-stacktrace-perl (0.09-3 to 0.09-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-stacktrace-perl.html
    • autopkgtest for libapp-stacktrace-perl/0.09-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libapp-termcast-perl (0.13-3 to 0.13-4)
  • Migration status for libapp-termcast-perl (0.13-3 to 0.13-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapp-termcast-perl.html
    • autopkgtest for libapp-termcast-perl/0.13-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libappconfig-std-perl (1.10-1 to 1.10-2)
  • Migration status for libappconfig-std-perl (1.10-1 to 1.10-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libappconfig-std-perl.html
    • autopkgtest for libappconfig-std-perl/1.10-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarch-perl (0.5.2-2 to 0.5.2-3)
  • Migration status for libarch-perl (0.5.2-2 to 0.5.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarch-perl.html
    • autopkgtest for libarch-perl/0.5.2-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libarchive-any-create-perl (0.3-2 to 0.3-3)
  • Migration status for libarchive-any-create-perl (0.3-2 to 0.3-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarchive-any-create-perl.html
    • autopkgtest for libarchive-any-create-perl/0.3-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarchive-any-lite-perl (0.11-1 to 0.11-2)
  • Migration status for libarchive-any-lite-perl (0.11-1 to 0.11-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarchive-any-lite-perl.html
    • autopkgtest for libarchive-any-lite-perl/0.11-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarchive-ar-perl (2.02-2 to 2.02-3)
  • Migration status for libarchive-ar-perl (2.02-2 to 2.02-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarchive-ar-perl.html
    • autopkgtest for libarchive-ar-perl/2.02-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarchive-cpio-perl (0.10-1.1 to 0.10-2)
  • Migration status for libarchive-cpio-perl (0.10-1.1 to 0.10-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarchive-cpio-perl.html
    • autopkgtest for libarchive-cpio-perl/0.10-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarray-group-perl (4.2-1 to 4.2-2)
  • Migration status for libarray-group-perl (4.2-1 to 4.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarray-group-perl.html
    • autopkgtest for libarray-group-perl/4.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarray-printcols-perl (2.6-2.1 to 2.6-3)
  • Migration status for libarray-printcols-perl (2.6-2.1 to 2.6-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/liba/libarray-printcols-perl.html
    • autopkgtest for libarray-printcols-perl/2.6-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libarray-refelem-perl (1.00+ds-1 to 1.00+ds-2)
  • Migration status for libarray-refelem-perl (1.00+ds-1 to 1.00+ds-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarray-refelem-perl.html
    • autopkgtest for libarray-refelem-perl/1.00+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libarray-unique-perl (0.08-2.1 to 0.08-3)
  • Migration status for libarray-unique-perl (0.08-2.1 to 0.08-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libarray-unique-perl.html
    • autopkgtest for libarray-unique-perl/0.08-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libaspect-perl (1.04-1.1 to 1.04-2)
  • Migration status for libaspect-perl (1.04-1.1 to 1.04-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaspect-perl.html
    • autopkgtest for libaspect-perl/1.04-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libasync-mergepoint-perl (0.04-2.1 to 0.04-3)
  • Migration status for libasync-mergepoint-perl (0.04-2.1 to 0.04-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libasync-mergepoint-perl.html
    • autopkgtest for libasync-mergepoint-perl/0.04-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libatombus-perl (1.0405-5.1 to 1.0405-6)
  • Migration status for libatombus-perl (1.0405-5.1 to 1.0405-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libatombus-perl.html
    • autopkgtest for libatombus-perl/1.0405-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libatompub-perl (0.3.7-3 to 0.3.7-4)
  • Migration status for libatompub-perl (0.3.7-3 to 0.3.7-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libatompub-perl.html
    • autopkgtest for libatompub-perl/0.3.7-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libatteanx-store-ldf-perl (0.04-1.1 to 0.04-2)
  • Migration status for libatteanx-store-ldf-perl (0.04-1.1 to 0.04-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libatteanx-store-ldf-perl/0.04-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libatteanx-store-ldf-perl.html
• libaudio-flac-header-perl (2.4-3 to 2.4-4)
  • Migration status for libaudio-flac-header-perl (2.4-3 to 2.4-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaudio-flac-header-perl.html
    • autopkgtest for libaudio-flac-header-perl/2.4-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libaudio-mpd-perl (2.004-2 to 2.004-3)
  • Migration status for libaudio-mpd-perl (2.004-2 to 2.004-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaudio-mpd-perl.html
    • autopkgtest for libaudio-mpd-perl/2.004-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libaudio-wav-perl (0.14-2.1 to 0.14-3)
  • Migration status for libaudio-wav-perl (0.14-2.1 to 0.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libaudio-wav-perl/0.14-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaudio-wav-perl.html
• libauthen-captcha-perl (1.024-2 to 1.024-3)
  • Migration status for libauthen-captcha-perl (1.024-2 to 1.024-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-captcha-perl.html
    • autopkgtest for libauthen-captcha-perl/1.024-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-cas-client-perl (0.07-2 to 0.08-1)
  • Migration status for libauthen-cas-client-perl (0.07-2 to 0.08-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-cas-client-perl.html
    • autopkgtest for libauthen-cas-client-perl/0.08-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-dechpwd-perl (2.007-1~1 to 2.007-1~2)
  • Migration status for libauthen-dechpwd-perl (2.007-1~1 to 2.007-1~2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-dechpwd-perl.html
    • autopkgtest for libauthen-dechpwd-perl/2.007-1~2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-krb5-admin-perl (0.17-1 to 0.17-2)
  • Migration status for libauthen-krb5-admin-perl (0.17-1 to 0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libauthen-krb5-admin-perl/0.17-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-krb5-admin-perl.html
• libauthen-krb5-perl (1.9-5 to 1.9-6)
  • Migration status for libauthen-krb5-perl (1.9-5 to 1.9-6): 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/liba/libauthen-krb5-perl.html
    • autopkgtest for libauthen-krb5-perl/1.9-6: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libauthen-libwrap-perl (0.23-1 to 0.23-2)
  • Migration status for libauthen-libwrap-perl (0.23-1 to 0.23-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-libwrap-perl.html
    • autopkgtest for libauthen-libwrap-perl/0.23-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-oath-perl (2.0.1-1 to 2.0.1-2)
  • Migration status for libauthen-oath-perl (2.0.1-1 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-oath-perl.html
    • autopkgtest for libauthen-oath-perl/2.0.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-pam-perl (0.16-3 to 0.16-4)
  • Migration status for libauthen-pam-perl (0.16-3 to 0.16-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libauthen-pam-perl/0.16-4: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-pam-perl.html
• libauthen-passphrase-perl (0.008-2.1 to 0.008-3)
  • Migration status for libauthen-passphrase-perl (0.008-2.1 to 0.008-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-passphrase-perl.html
    • autopkgtest for libauthen-passphrase-perl/0.008-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-sasl-perl (2.1600-1.1 to 2.1600-2)
  • Migration status for libauthen-sasl-perl (2.1600-1.1 to 2.1600-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-sasl-perl.html
    • autopkgtest for libauthen-sasl-perl/2.1600-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-sasl-saslprep-perl (1.100-1 to 1.100-2)
  • Migration status for libauthen-sasl-saslprep-perl (1.100-1 to 1.100-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-sasl-saslprep-perl.html
    • autopkgtest for libauthen-sasl-saslprep-perl/1.100-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-cdbi-perl (0.2-3.1 to 0.2-4)
  • Migration status for libauthen-simple-cdbi-perl (0.2-3.1 to 0.2-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-cdbi-perl.html
    • autopkgtest for libauthen-simple-cdbi-perl/0.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-dbi-perl (0.2-3.1 to 0.2-4)
  • Migration status for libauthen-simple-dbi-perl (0.2-3.1 to 0.2-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-dbi-perl.html
    • autopkgtest for libauthen-simple-dbi-perl/0.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-dbm-perl (0.2-4.1 to 0.2-5)
  • Migration status for libauthen-simple-dbm-perl (0.2-4.1 to 0.2-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-dbm-perl.html
    • autopkgtest for libauthen-simple-dbm-perl/0.2-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-http-perl (0.2-5.1 to 0.2-6)
  • Migration status for libauthen-simple-http-perl (0.2-5.1 to 0.2-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-http-perl.html
    • autopkgtest for libauthen-simple-http-perl/0.2-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-kerberos-perl (0.1-5.1 to 0.1-6)
  • Migration status for libauthen-simple-kerberos-perl (0.1-5.1 to 0.1-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-kerberos-perl.html
    • autopkgtest for libauthen-simple-kerberos-perl/0.1-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-net-perl (0.2-5.1 to 0.2-6)
  • Migration status for libauthen-simple-net-perl (0.2-5.1 to 0.2-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-net-perl.html
    • autopkgtest for libauthen-simple-net-perl/0.2-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-pam-perl (0.2-4.1 to 0.2-5)
  • Migration status for libauthen-simple-pam-perl (0.2-4.1 to 0.2-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-pam-perl.html
    • autopkgtest for libauthen-simple-pam-perl/0.2-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-passwd-perl (0.6-4.1 to 0.6-5)
  • Migration status for libauthen-simple-passwd-perl (0.6-4.1 to 0.6-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-passwd-perl.html
    • autopkgtest for libauthen-simple-passwd-perl/0.6-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-radius-perl (0.1-3.1 to 0.1-4)
  • Migration status for libauthen-simple-radius-perl (0.1-3.1 to 0.1-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-radius-perl.html
    • autopkgtest for libauthen-simple-radius-perl/0.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-simple-smb-perl (0.1-4.1 to 0.1-5)
  • Migration status for libauthen-simple-smb-perl (0.1-4.1 to 0.1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-simple-smb-perl.html
    • autopkgtest for libauthen-simple-smb-perl/0.1-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libauthen-smb-perl (0.91-6 to 0.91-7)
  • Migration status for libauthen-smb-perl (0.91-6 to 0.91-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libauthen-smb-perl.html
    • autopkgtest for libauthen-smb-perl/0.91-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libautobox-core-perl (1.33-1 to 1.33-2)
  • Migration status for libautobox-core-perl (1.33-1 to 1.33-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libautobox-core-perl.html
    • autopkgtest for libautobox-core-perl/1.33-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libautobox-dump-perl (20090426.1746-3.1 to 20090426.1746-4)
  • Migration status for libautobox-dump-perl (20090426.1746-3.1 to 20090426.1746-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libautobox-dump-perl.html
    • autopkgtest for libautobox-dump-perl/20090426.1746-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libautobox-junctions-perl (0.002-1 to 0.002-2)
  • Migration status for libautobox-junctions-perl (0.002-1 to 0.002-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libautobox-junctions-perl.html
    • autopkgtest for libautobox-junctions-perl/0.002-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libautobox-list-util-perl (20090629-3.1 to 20090629-4)
  • Migration status for libautobox-list-util-perl (20090629-3.1 to 20090629-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libautobox-list-util-perl.html
    • autopkgtest for libautobox-list-util-perl/20090629-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libautovivification-perl (0.18-1 to 0.18-2)
  • Migration status for libautovivification-perl (0.18-1 to 0.18-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libautovivification-perl.html
    • autopkgtest for libautovivification-perl/0.18-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libaws-signature4-perl (1.02-1.1 to 1.02-2)
  • Migration status for libaws-signature4-perl (1.02-1.1 to 1.02-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaws-signature4-perl.html
    • autopkgtest for libaws-signature4-perl/1.02-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libb-compiling-perl (0.06-1 to 0.06-2)
  • Migration status for libb-compiling-perl (0.06-1 to 0.06-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libb-compiling-perl.html
    • autopkgtest for libb-compiling-perl/0.06-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libb-hooks-op-annotation-perl (0.44-2 to 0.44-3)
  • Migration status for libb-hooks-op-annotation-perl (0.44-2 to 0.44-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libb-hooks-op-annotation-perl.html
    • autopkgtest for libb-hooks-op-annotation-perl/0.44-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libb-hooks-op-check-entersubforcv-perl (0.10-1 to 0.10-2)
  • Migration status for libb-hooks-op-check-entersubforcv-perl (0.10-1 to 0.10-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libb-hooks-op-check-entersubforcv-perl.html
    • autopkgtest for libb-hooks-op-check-entersubforcv-perl/0.10-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libb-hooks-op-check-perl (0.22-1 to 0.22-2)
  • Migration status for libb-hooks-op-check-perl (0.22-1 to 0.22-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libb-hooks-op-check-perl.html
    • autopkgtest for libb-hooks-op-check-perl/0.22-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libb-lint-perl (1.22-1 to 1.22-2)
  • Migration status for libb-lint-perl (1.22-1 to 1.22-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libb-lint-perl.html
    • autopkgtest for libb-lint-perl/1.22-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libb-perlreq-perl (0.82-6 to 0.82-7)
  • Migration status for libb-perlreq-perl (0.82-6 to 0.82-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libb-perlreq-perl.html
    • autopkgtest for libb-perlreq-perl/0.82-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbarcode-datamatrix-perl (0.10-1 to 0.10-2)
  • Migration status for libbarcode-datamatrix-perl (0.10-1 to 0.10-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbarcode-datamatrix-perl.html
    • autopkgtest for libbarcode-datamatrix-perl/0.10-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbenchmark-progressbar-perl (0.00001-2 to 0.00001-3)
  • Migration status for libbenchmark-progressbar-perl (0.00001-2 to 0.00001-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbenchmark-progressbar-perl.html
    • autopkgtest for libbenchmark-progressbar-perl/0.00001-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbencode-perl (1.501-1.1 to 1.501-2)
  • Migration status for libbencode-perl (1.501-1.1 to 1.501-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbencode-perl.html
    • autopkgtest for libbencode-perl/1.501-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbiblio-citation-parser-perl (1.10+dfsg-2.1 to 1.10+dfsg-3)
  • Migration status for libbiblio-citation-parser-perl (1.10+dfsg-2.1 to 1.10+dfsg-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbiblio-citation-parser-perl.html
    • autopkgtest for libbiblio-citation-parser-perl/1.10+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbiblio-endnotestyle-perl (0.06-1 to 0.06-2)
  • Migration status for libbiblio-endnotestyle-perl (0.06-1 to 0.06-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbiblio-endnotestyle-perl.html
    • autopkgtest for libbiblio-endnotestyle-perl/0.06-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbit-vector-perl (7.4-1 to 7.4-2)
  • Migration status for libbit-vector-perl (7.4-1 to 7.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbit-vector-perl.html
    • autopkgtest for libbit-vector-perl/7.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbloom-filter-perl (1.2-2.1 to 1.2-3)
  • Migration status for libbloom-filter-perl (1.2-2.1 to 1.2-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbloom-filter-perl.html
    • autopkgtest for libbloom-filter-perl/1.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libboolean-perl (0.46-1 to 0.46-2)
  • Migration status for libboolean-perl (0.46-1 to 0.46-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libboolean-perl.html
    • autopkgtest for libboolean-perl/0.46-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libboost-geometry-utils-perl (0.15-2 to 0.15-3)
  • Migration status for libboost-geometry-utils-perl (0.15-2 to 0.15-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libboost-geometry-utils-perl.html
    • autopkgtest for libboost-geometry-utils-perl/0.15-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbot-basicbot-pluggable-perl (1.20-1 to 1.20-2)
  • Migration status for libbot-basicbot-pluggable-perl (1.20-1 to 1.20-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbot-basicbot-pluggable-perl.html
    • autopkgtest for libbot-basicbot-pluggable-perl/1.20-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libboulder-perl (1.30-5.1 to 1.30-6)
  • Migration status for libboulder-perl (1.30-5.1 to 1.30-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libboulder-perl.html
    • autopkgtest for libboulder-perl/1.30-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libbsd-arc4random-perl (1.50-6 to 1.50-7)
  • Migration status for libbsd-arc4random-perl (1.50-6 to 1.50-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libbsd-arc4random-perl/1.50-7: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbsd-arc4random-perl.html
• libdevel-cover-perl (1.37-1 to 1.38-1)
  • Migration status for libdevel-cover-perl (1.37-1 to 1.38-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdevel-cover-perl.html
    • autopkgtest for libdevel-cover-perl/1.38-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libdevice-cdio-perl (2.0.0-1 to 2.0.0-2)
  • Migration status for libdevice-cdio-perl (2.0.0-1 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdevice-cdio-perl.html
    • autopkgtest for libdevice-cdio-perl/2.0.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libdvdread (6.1.2-1 to 6.1.3-1)
  • Migration status for libdvdread (6.1.2-1 to 6.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdvdread.html
• libplayerone (2.0.5-2 to 2.0.6+20220608012829-1)
  • Migration status for libplayerone (2.0.5-2 to 2.0.6+20220608012829-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)
• libredis-fast-perl (0.33+dfsg-1 to 0.34+dfsg-1)
  • Migration status for libredis-fast-perl (0.33+dfsg-1 to 0.34+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libredis-fast-perl.html
    • autopkgtest for libredis-fast-perl/0.34+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libtemplates-parser (22.0.0-2 to 22.0.0-3)
  • Migration status for libtemplates-parser (22.0.0-2 to 22.0.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtemplates-parser.html
    • autopkgtest for libtemplates-parser/22.0.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libtime-warp-perl (0.54-1 to 0.54-2)
  • Migration status for libtime-warp-perl (0.54-1 to 0.54-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtime-warp-perl.html
    • autopkgtest for libtime-warp-perl/0.54-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• lighttpd (1.4.64-1 to 1.4.65-1)
  • Migration status for lighttpd (1.4.64-1 to 1.4.65-1): Will attempt migration (Any information below is purely informational)
    • Depends: lighttpd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lighttpd.html
    • autopkgtest for lighttpd/1.4.65-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• localslackirc (1.14-1 to 1.15-4)
  • Migration status for localslackirc (1.14-1 to 1.15-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/localslackirc.html
    • autopkgtest for localslackirc/1.15-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• love (11.3-1 to 11.4-1)
  • Migration status for love (11.3-1 to 11.4-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:
    • Updating love will fix bugs in testing: #1011300
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/love.html
• luajit2 (- to 2.1-20220411-5)
  • Migration status for luajit2 (- to 2.1-20220411-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/luajit2.html
    • autopkgtest for luajit2/2.1-20220411-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• mercurial (6.1.2-1 to 6.1.3-1)
  • Migration status for mercurial (6.1.2-1 to 6.1.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mercurial.html
    • autopkgtest for mercurial/6.1.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
• monero (0.17.3.0+~0+20200826-1 to 0.17.3.0+~0+20200826-2)
  • Migration status for monero (0.17.3.0+~0+20200826-1 to 0.17.3.0+~0+20200826-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 mipsel
    • 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: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
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monero.html
• netdata (1.34.1-1 to 1.35.0-1)
  • Migration status for netdata (1.34.1-1 to 1.35.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Not built on buildd: upload info for arch mipsel binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
    • Too young, only 2 of 5 days old
    • Depends: netdata openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdata.html
• nheko (0.9.1-1 to 0.9.3-2)
  • Migration status for nheko (0.9.1-1 to 0.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 2 of 5 days old
    • Depends: nheko openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nheko.html
• node-caniuse-db (1.0.30001340-1 to 1.0.30001352-1)
  • Migration status for node-caniuse-db (1.0.30001340-1 to 1.0.30001352-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-caniuse-db.html
    • autopkgtest for node-caniuse-db/1.0.30001352-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-electron-to-chromium (1.4.137-1 to 1.4.150-1)
  • Migration status for node-electron-to-chromium (1.4.137-1 to 1.4.150-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-electron-to-chromium.html
    • autopkgtest for node-electron-to-chromium/1.4.150-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-jest (28.1.0~ds+~cs69.52.23-1 to 28.1.1~ds+~cs70.48.23-1)
  • Migration status for node-jest (28.1.0~ds+~cs69.52.23-1 to 28.1.1~ds+~cs70.48.23-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-jest.html
    • autopkgtest for node-jest/28.1.1~ds+~cs70.48.23-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-ldapjs (2.3.2+~cs4.5.6-1 to 2.3.3+~cs4.5.6-1)
  • Migration status for node-ldapjs (2.3.2+~cs4.5.6-1 to 2.3.3+~cs4.5.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-ldapjs.html
    • autopkgtest for node-ldapjs/2.3.3+~cs4.5.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-log4js (6.4.7+~cs8.3.19-1 to 6.5.2+~cs8.4.12-1)
  • Migration status for node-log4js (6.4.7+~cs8.3.19-1 to 6.5.2+~cs8.4.12-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-log4js.html
    • autopkgtest for node-log4js/6.5.2+~cs8.4.12-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-node-rsa (1.1.1-1 to 1.1.1-3)
  • Migration status for node-node-rsa (1.1.1-1 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating node-node-rsa will fix bugs in testing: #1011796
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-rsa.html
    • autopkgtest for node-node-rsa/1.1.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-rollup (2.75.5-1 to 2.75.6-1)
  • Migration status for node-rollup (2.75.5-1 to 2.75.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-rollup.html
    • autopkgtest for node-rollup/2.75.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• octave-symbolic (- to 2.9.1~git.2022.06.09-1)
  • Migration status for octave-symbolic (- to 2.9.1~git.2022.06.09-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-symbolic.html
    • autopkgtest for octave-symbolic/2.9.1~git.2022.06.09-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• openssl (1.1.1o-1 to 3.0.3-7)
  • Migration status for openssl (1.1.1o-1 to 3.0.3-7): Will attempt migration due to a hint (Any information below is purely informational)
    • Implicit dependency: openssl bind9-libs/amd64
    • Implicit dependency: openssl bind9-libs/arm64
    • Implicit dependency: openssl bind9-libs/armel
    • Implicit dependency: openssl bind9-libs/armhf
    • Implicit dependency: openssl bind9-libs/i386
    • Implicit dependency: openssl bind9-libs/mips64el
    • Implicit dependency: openssl bind9-libs/mipsel
    • Implicit dependency: openssl bind9-libs/ppc64el
    • Implicit dependency: openssl bind9-libs/s390x
    • Implicit dependency: openssl cryptsetup/amd64
    • Implicit dependency: openssl cryptsetup/arm64
    • Implicit dependency: openssl cryptsetup/armel
    • Implicit dependency: openssl cryptsetup/armhf
    • Implicit dependency: openssl cryptsetup/i386
    • Implicit dependency: openssl cryptsetup/mips64el
    • Implicit dependency: openssl cryptsetup/mipsel
    • Implicit dependency: openssl cryptsetup/ppc64el
    • Implicit dependency: openssl cryptsetup/s390x
    • Implicit dependency: openssl hfsprogs/amd64
    • Implicit dependency: openssl hfsprogs/arm64
    • Implicit dependency: openssl hfsprogs/armel
    • Implicit dependency: openssl hfsprogs/armhf
    • Implicit dependency: openssl hfsprogs/i386
    • Implicit dependency: openssl hfsprogs/mips64el
    • Implicit dependency: openssl hfsprogs/mipsel
    • Implicit dependency: openssl hfsprogs/ppc64el
    • Implicit dependency: openssl hfsprogs/s390x
    • Implicit dependency: openssl open-iscsi/amd64
    • Implicit dependency: openssl open-iscsi/arm64
    • Implicit dependency: openssl open-iscsi/armhf
    • Implicit dependency: openssl open-iscsi/i386
    • Implicit dependency: openssl open-iscsi/mipsel
    • Implicit dependency: openssl open-iscsi/ppc64el
    • Implicit dependency: openssl open-iscsi/s390x
    • Implicit dependency: openssl open-isns
    • Implicit dependency: openssl openssh/amd64
    • Implicit dependency: openssl openssh/arm64
    • Implicit dependency: openssl openssh/armel
    • Implicit dependency: openssl openssh/armhf
    • Implicit dependency: openssl openssh/i386
    • Implicit dependency: openssl openssh/mips64el
    • Implicit dependency: openssl openssh/mipsel
    • Implicit dependency: openssl openssh/ppc64el
    • Implicit dependency: openssl openssh/s390x
    • Implicit dependency: openssl ppp/amd64
    • Implicit dependency: openssl ppp/arm64
    • Implicit dependency: openssl ppp/armel
    • Implicit dependency: openssl ppp/armhf
    • Implicit dependency: openssl ppp/i386
    • Implicit dependency: openssl ppp/mips64el
    • Implicit dependency: openssl ppp/mipsel
    • Implicit dependency: openssl ppp/ppc64el
    • Implicit dependency: openssl wget/amd64
    • Implicit dependency: openssl wget/arm64
    • Implicit dependency: openssl wget/armel
    • Implicit dependency: openssl wget/armhf
    • Implicit dependency: openssl wget/i386
    • Implicit dependency: openssl wget/mips64el
    • Implicit dependency: openssl wget/mipsel
    • Implicit dependency: openssl wget/ppc64el
    • Implicit dependency: openssl wget/s390x
    • Implicit dependency: openssl wpa/amd64
    • Implicit dependency: openssl wpa/arm64
    • Implicit dependency: openssl wpa/armel
    • Implicit dependency: openssl wpa/armhf
    • Implicit dependency: openssl wpa/i386
    • Implicit dependency: openssl wpa/mips64el
    • Implicit dependency: openssl wpa/mipsel
    • Implicit dependency: openssl wpa/ppc64el
    • Implicit dependency: openssl wpa/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openssl.html
    • Should wait for tests relating to openssl 3.0.3-7, but forced by sramacher
    • autopkgtest for burp/2.4.0-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
    • autopkgtest for debian-edu-config/2.12.20: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for golang-github-mendersoftware-openssl/1.1.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for m2crypto/0.38.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for mender-client/3.0.0+ds1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for openssl/3.0.3-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ruby3.0/3.0.3-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for scapy/2.4.4-4: amd64: Pass, arm64: Not a regression, armhf: Not a regression, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
    • autopkgtest for serf/1.3.9-10: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Overriding age needed from 2 days to 2 by sramacher
    • 2 days old (needed 2 days)
• padthv1 (0.9.25-1 to 0.9.26-1)
  • Migration status for padthv1 (0.9.25-1 to 0.9.26-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/padthv1.html
    • autopkgtest for padthv1/0.9.26-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: Not a regression, s390x: No test results
• pagmo (- to 2.18.0-1)
  • Migration status for pagmo (- to 2.18.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pagmo.html
• pkg-js-tools (0.14.26 to 0.14.28)
  • Migration status for pkg-js-tools (0.14.26 to 0.14.28): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pkg-js-tools.html
    • autopkgtest for pkg-js-tools/0.14.28: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-base58 (1.0.3-1.1 to 1.0.3-2)
  • Migration status for python-base58 (1.0.3-1.1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-base58.html
    • autopkgtest for python-base58/1.0.3-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-consul (0.7.1-1.1 to 0.7.1-2)
  • Migration status for python-consul (0.7.1-1.1 to 0.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for patroni/2.1.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-consul.html
• python-django-simple-history (2.7.0-1.1 to 2.7.0-2)
  • Migration status for python-django-simple-history (2.7.0-1.1 to 2.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/p/python-django-simple-history.html
• python-easysnmp (- to 0.2.5+git20220424-1)
  • Migration status for python-easysnmp (- to 0.2.5+git20220424-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by berni@birkenwald.de
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-easysnmp.html
• python-envs (1.2.6-1.1 to 1.2.6-2)
  • Migration status for python-envs (1.2.6-1.1 to 1.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/p/python-envs.html
• python-freesasa (- to 2.1.0-2)
  • Migration status for python-freesasa (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-freesasa/2.1.0-2: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-freesasa.html
• python-iniparse (0.4-3 to 0.5-1)
  • Migration status for python-iniparse (0.4-3 to 0.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-iniparse.html
    • autopkgtest for python-iniparse/0.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-mongomock (- to 4.0.0-2)
  • Migration status for python-mongomock (- to 4.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-mongomock.html
    • autopkgtest for python-mongomock/4.0.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-prodigy (- to 2.0.0-2)
  • Migration status for python-prodigy (- to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prodigy/arm64 has unsatisfiable dependency
    • autopkgtest for python-prodigy/2.0.0-2: amd64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): python-prodigy python-freesasa
    • Depends: python-prodigy python-freesasa
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-prodigy.html
    • uninstallable on arch arm64, not running autopkgtest there
• python-qpageview (- to 0.6.2-1)
  • Migration status for python-qpageview (- to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by debian@jbfavre.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/p/python-qpageview.html
• python-wikkid (- to 0+git20211221.1.b129e3b-1)
  • Migration status for python-wikkid (- to 0+git20211221.1.b129e3b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jelmer, a new source-only upload is needed to allow migration
    • Too young, only 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-wikkid.html
    • autopkgtest for python-wikkid/0+git20211221.1.b129e3b-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python3-stdlib-extensions (3.9.12-1 to 3.10.5-1)
  • Migration status for python3-stdlib-extensions (3.9.12-1 to 3.10.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for glib2.0/2.72.1-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for skimage/0.18.3-3: amd64: Pass, arm64: Pass, armhf: Ignored failure, ppc64el: Pass, s390x: Pass
    • python3-stdlib-extensions unsatisfiable Build-Depends(-Arch) on i386: libpython3.11-dev
    • python3-stdlib-extensions unsatisfiable Build-Depends(-Arch) on i386: libpython3.11-dbg
    • python3-stdlib-extensions unsatisfiable Build-Depends(-Arch) on i386: python3.11-dev:any
    • python3-stdlib-extensions unsatisfiable Build-Depends(-Arch) on i386: python3.11-dbg:any
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): python3-stdlib-extensions python3.11
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-stdlib-extensions.html
• r-cran-flextable (0.7.0-2 to 0.7.1-1)
  • Migration status for r-cran-flextable (0.7.0-2 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-flextable.html
    • autopkgtest for r-cran-flextable/0.7.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-geepack (1.3.3-1 to 1.3.4-1)
  • Migration status for r-cran-geepack (1.3.3-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-geepack.html
    • autopkgtest for r-cran-geepack/1.3.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-mi (1.0-8 to 1.1-1)
  • Migration status for r-cran-mi (1.0-8 to 1.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mi.html
    • autopkgtest for r-cran-mi/1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-prevalence (0.4.0-2 to 0.4.1-1)
  • Migration status for r-cran-prevalence (0.4.0-2 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-prevalence.html
    • autopkgtest for r-cran-prevalence/0.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-progressr (0.10.0-1 to 0.10.1-1)
  • Migration status for r-cran-progressr (0.10.0-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-progressr.html
    • autopkgtest for r-cran-progressr/0.10.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-rmpfr (0.8-7-0.1 to 0.8-9-0.1)
  • Migration status for r-cran-rmpfr (0.8-7-0.1 to 0.8-9-0.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rmpfr.html
    • autopkgtest for r-cran-rmpfr/0.8-9-0.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-rsconnect (0.8.25-1 to 0.8.26-1)
  • Migration status for r-cran-rsconnect (0.8.25-1 to 0.8.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rsconnect/0.8.26-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rsconnect.html
• r-cran-segmented (1.5-0-1 to 1.6-0-1)
  • Migration status for r-cran-segmented (1.5-0-1 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/r/r-cran-segmented.html
    • autopkgtest for r-cran-segmented/1.6-0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-sna (2.6-1 to 2.7-1)
  • Migration status for r-cran-sna (2.6-1 to 2.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sna.html
    • autopkgtest for r-cran-sna/2.7-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-sp (1:1.4-7+dfsg-1 to 1:1.5-0+dfsg-1)
  • Migration status for r-cran-sp (1:1.4-7+dfsg-1 to 1:1.5-0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sp.html
    • autopkgtest for r-cran-sp/1:1.5-0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• r-cran-spacetime (1.2-6+dfsg-1 to 1.2-7+dfsg-1)
  • Migration status for r-cran-spacetime (1.2-6+dfsg-1 to 1.2-7+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spacetime.html
    • autopkgtest for r-cran-spacetime/1.2-7+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• racket (8.4-1 to 8.5-1)
  • Migration status for racket (8.4-1 to 8.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/r/racket.html
• rsass (- to 0.25.2-4)
  • Migration status for rsass (- to 0.25.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rsass rustc (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rsass rust-nom-locate
    • Built-Using: rsass rust-nom-locate
    • Depends: rsass rust-nom-locate
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsass.html
    • autopkgtest for rsass/0.25.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rsibreak (4:0.12.14-1 to 4:0.12.15-1)
  • Migration status for rsibreak (4:0.12.14-1 to 4:0.12.15-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/rsibreak.html
• ruby-image-processing (1.10.3-1 to 1.10.3-2)
  • Migration status for ruby-image-processing (1.10.3-1 to 1.10.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating ruby-image-processing will fix bugs in testing: #1007225
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-image-processing.html
    • autopkgtest for ruby-image-processing/1.10.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-alacritty-terminal (0.16.1-1 to 0.16.1-2)
  • Migration status for rust-alacritty-terminal (0.16.1-1 to 0.16.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-alacritty-terminal.html
    • autopkgtest for rust-alacritty-terminal/0.16.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-calloop (- to 0.9.3-2)
  • Migration status for rust-calloop (- to 0.9.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-calloop.html
    • autopkgtest for rust-calloop/0.9.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-glutin-glx-sys (- to 0.1.7-2)
  • Migration status for rust-glutin-glx-sys (- to 0.1.7-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-glutin-glx-sys.html
    • autopkgtest for rust-glutin-glx-sys/0.1.7-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• samplv1 (0.9.25-1 to 0.9.26-1)
  • Migration status for samplv1 (0.9.25-1 to 0.9.26-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/samplv1.html
    • autopkgtest for samplv1/0.9.26-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• sssd (2.6.3-3 to 2.7.1-2)
  • Migration status for sssd (2.6.3-3 to 2.7.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sssd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sssd.html
    • autopkgtest for sssd/2.7.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• streamlink (4.0.1-1 to 4.1.0-1)
  • Migration status for streamlink (4.0.1-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/streamlink.html
    • autopkgtest for streamlink/4.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• synthv1 (0.9.25-2 to 0.9.26-1)
  • Migration status for synthv1 (0.9.25-2 to 0.9.26-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/synthv1.html
    • autopkgtest for synthv1/0.9.26-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• sysbench (1.0.20+ds-2 to 1.0.20+ds-4)
  • Migration status for sysbench (1.0.20+ds-2 to 1.0.20+ds-4): 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 sysbench/1.0.20+ds-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): sysbench luajit2
    • Depends: sysbench luajit
  • Additional info:
    • Updating sysbench will fix bugs in testing: #1011307
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysbench.html
• tryton-modules-country (6.0.2-1 to 6.0.2-2)
  • Migration status for tryton-modules-country (6.0.2-1 to 6.0.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tryton-modules-country.html
    • autopkgtest for tryton-modules-country/6.0.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• borgbackup (1.2.0-1 to 1.2.1-1)
  • Migration status for borgbackup (1.2.0-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: borgbackup openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/borgbackup.html
    • autopkgtest for borgbackup/1.2.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• cherrytree (0.99.43+dfsg-1 to 0.99.47+dfsg-1)
  • Migration status for cherrytree (0.99.43+dfsg-1 to 0.99.47+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/c/cherrytree.html
• csvjdbc (1.0.36+ds-1 to 1.0.37-1)
  • Migration status for csvjdbc (1.0.36+ds-1 to 1.0.37-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/c/csvjdbc.html
• debiancontributors (0.7.8-2 to 0.7.8-3)
  • Migration status for debiancontributors (0.7.8-2 to 0.7.8-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/d/debiancontributors.html
• doublecmd (1.0.5-1 to 1.0.6-1)
  • Migration status for doublecmd (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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doublecmd.html
• dtkcommon (5.5.21-1 to 5.5.23-1)
  • Migration status for dtkcommon (5.5.21-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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dtkcommon.html
• emacs-fossil (2022.05.28-1 to 2022.07.07-1)
  • Migration status for emacs-fossil (2022.05.28-1 to 2022.07.07-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/e/emacs-fossil.html
• emacs-pod-mode (1.03-3 to 1.03-4)
  • Migration status for emacs-pod-mode (1.03-3 to 1.03-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/emacs-pod-mode.html
• eog (42.1-1 to 42.2-1)
  • Migration status for eog (42.1-1 to 42.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/e/eog.html
• evolution-ews (3.44.1-2 to 3.44.2-1)
  • Migration status for evolution-ews (3.44.1-2 to 3.44.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/e/evolution-ews.html
• fdb (5.10.2-1 to 5.10.8-1)
  • Migration status for fdb (5.10.2-1 to 5.10.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: fdb eckit
    • Depends: fdb metkit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdb.html
• ffcall (2.4-1 to 2.4-2)
  • Migration status for ffcall (2.4-1 to 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 3 of 5 days old
  • Additional info:
    • Updating ffcall will fix bugs in testing: #1011808
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ffcall.html
• fmit (1.2.6-0.2 to 1.2.14-0.1)
  • Migration status for fmit (1.2.6-0.2 to 1.2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fmit.html
• fprintd (1.94.2-1 to 1.94.2-2)
  • Migration status for fprintd (1.94.2-1 to 1.94.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:
    • Updating fprintd will fix bugs in testing: #1009395
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fprintd.html
• gfal2-bindings (- to 1.11.1-2)
  • Migration status for gfal2-bindings (- to 1.11.1-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/gfal2-bindings.html
• gfal2-util (- to 1.7.1-2)
  • Migration status for gfal2-util (- to 1.7.1-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
    • Depends: gfal2-util gfal2-bindings
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfal2-util.html
• glib2.0 (2.72.1-1 to 2.72.2-2)
  • Migration status for glib2.0 (2.72.1-1 to 2.72.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for glib2.0/2.72.2-2: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libadwaita-1/1.1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for slurm-wlm/21.08.8.2-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for thunderbird/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for tracker/3.1.2-4: amd64: Ignored failure, arm64: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glib2.0.html
• gnome-maps (42.1-1 to 42.2-1)
  • Migration status for gnome-maps (42.1-1 to 42.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/gnome-maps.html
• gnome-shell-extension-kimpanel (0.0~git20220523.15e928b-1 to 0.0~git20220602.3318bdf-1)
  • Migration status for gnome-shell-extension-kimpanel (0.0~git20220523.15e928b-1 to 0.0~git20220602.3318bdf-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/gnome-shell-extension-kimpanel.html
• golang-github-bep-clock (- to 0.3.0-1)
  • Migration status for golang-github-bep-clock (- 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 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-bep-clock.html
    • autopkgtest for golang-github-bep-clock/0.3.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• golang-github-bep-overlayfs (- to 0.6.0-1)
  • Migration status for golang-github-bep-overlayfs (- 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 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-bep-overlayfs.html
    • autopkgtest for golang-github-bep-overlayfs/0.6.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• golang-github-gomagedon-expectate (- to 1.1.0-1)
  • Migration status for golang-github-gomagedon-expectate (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by linuxmaniac@torreviejawireless.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-gomagedon-expectate.html
    • autopkgtest for golang-github-gomagedon-expectate/1.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• goldendict (1.5.0~rc2+git20220219+ds-1 to 1.5.0~rc2+git20220602+ds-1)
  • Migration status for goldendict (1.5.0~rc2+git20220219+ds-1 to 1.5.0~rc2+git20220602+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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goldendict.html
• granite (6.2.0-1 to 6.2.0-2)
  • Migration status for granite (6.2.0-1 to 6.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/granite.html
• grpc-proto (0.0~git20220429.154a1b2-1 to 0.0~git20220524.8efd488-1)
  • Migration status for grpc-proto (0.0~git20220429.154a1b2-1 to 0.0~git20220524.8efd488-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/grpc-proto.html
• iminuit (- to 2.11.2-2)
  • Migration status for iminuit (- to 2.11.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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iminuit.html
    • autopkgtest for iminuit/2.11.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• libcommons-jexl-java (1.1-3.1 to 1.1-4)
  • Migration status for libcommons-jexl-java (1.1-3.1 to 1.1-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/libc/libcommons-jexl-java.html
• libmicam (1.0-2 to 1.0-3)
  • Migration status for libmicam (1.0-2 to 1.0-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libnftnl (1.2.1-1 to 1.2.2-1)
  • Migration status for libnftnl (1.2.1-1 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnftnl.html
• librtas (2.0.0-3 to 2.0.3-1)
  • Migration status for librtas (2.0.0-3 to 2.0.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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libsbig (4.9.9-1 to 4.9.9-2)
  • Migration status for libsbig (4.9.9-1 to 4.9.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsbig-dev/armel has unsatisfiable dependency
    • libsbig-dev/mips64el has unsatisfiable dependency
    • libsbig-dev/ppc64el has unsatisfiable dependency
    • libsbig-dev/s390x has unsatisfiable dependency
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
• libsdl2 (2.0.22+dfsg-4 to 2.0.22+dfsg-5)
  • Migration status for libsdl2 (2.0.22+dfsg-4 to 2.0.22+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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2.html
    • autopkgtest for libsdl2/2.0.22+dfsg-5: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• linux-signed-amd64 (5.17.3+1 to 5.18.2+1)
  • Migration status for linux-signed-amd64 (5.17.3+1 to 5.18.2+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for zfs-linux/2.1.4-1: amd64: Regression ♻ (reference ♻), arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): linux-signed-amd64 linux
    • Built-Using: linux-signed-amd64 linux
    • Depends: linux-signed-amd64 linux
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
• linux-signed-arm64 (5.17.3+1 to 5.18.2+1)
  • Migration status for linux-signed-arm64 (5.17.3+1 to 5.18.2+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for zfs-linux/2.1.4-1: amd64: Pass, arm64: Regression ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): linux-signed-arm64 linux
    • Built-Using: linux-signed-arm64 linux
    • Depends: linux-signed-arm64 linux
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• linux-signed-i386 (5.17.3+1 to 5.18.2+1)
  • Migration status for linux-signed-i386 (5.17.3+1 to 5.18.2+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for zfs-linux/2.1.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): linux-signed-i386 linux
    • Built-Using: linux-signed-i386 linux
    • Depends: linux-signed-i386 linux
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• luajit (2.1.0~beta3+dfsg-6 to 2.1.0~beta3+git20220320+dfsg-4)
  • Migration status for luajit (2.1.0~beta3+dfsg-6 to 2.1.0~beta3+git20220320+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lua-moses/2.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for luajit/2.1.0~beta3+git20220320+dfsg-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
    • autopkgtest for sysbench/1.0.20+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻)
    • Too young, only 3 of 5 days old
    • Depends: luajit luajit2
  • Additional info:
    • Updating luajit will fix bugs in testing: #1008069
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/luajit.html
• materia-kde (20220510-1 to 20220607-1)
  • Migration status for materia-kde (20220510-1 to 20220607-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/materia-kde.html
• mongo-c-driver (1.21.1-1 to 1.21.2-1)
  • Migration status for mongo-c-driver (1.21.1-1 to 1.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 3 of 5 days old
    • Depends: mongo-c-driver openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-c-driver.html
• mrpt (1:2.4.4+ds-1 to 1:2.4.9+ds-1)
  • Migration status for mrpt (1:2.4.4+ds-1 to 1:2.4.9+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrpt.html
• music123 (16.6-3 to 16.6-4)
  • Migration status for music123 (16.6-3 to 16.6-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/m/music123.html
    • autopkgtest for music123/16.6-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• network-manager-applet (1.26.0-1 to 1.28.0-1)
  • Migration status for network-manager-applet (1.26.0-1 to 1.28.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/n/network-manager-applet.html
• nftables (1.0.2-1 to 1.0.4-1)
  • Migration status for nftables (1.0.2-1 to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nftables would introduce bugs in testing: #1012613
    • Build-Depends(-Arch): nftables libnftnl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nftables.html
    • autopkgtest for nftables/1.0.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• node-prosemirror-view (- to 1.23.13-2)
  • Migration status for node-prosemirror-view (- to 1.23.13-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/n/node-prosemirror-view.html
    • autopkgtest for node-prosemirror-view/1.23.13-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• nsca (2.10.1-1 to 2.10.2-1)
  • Migration status for nsca (2.10.1-1 to 2.10.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/n/nsca.html
• papirus-icon-theme (20220508-1 to 20220606-1)
  • Migration status for papirus-icon-theme (20220508-1 to 20220606-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/papirus-icon-theme.html
• paramcoq (1.1.3-3 to 1.1.3-6)
  • Migration status for paramcoq (1.1.3-3 to 1.1.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: paramcoq coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paramcoq.html
    • autopkgtest for paramcoq/1.1.3-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• python-poppler-qt5 (0.75.0-3 to 21.3.0-1)
  • Migration status for python-poppler-qt5 (0.75.0-3 to 21.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:
    • Updating python-poppler-qt5 will fix bugs in testing: #1012188
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-poppler-qt5.html
    • autopkgtest for python-poppler-qt5/21.3.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python3.10 (3.10.4-1 to 3.10.5-1)
  • Migration status for python3.10 (3.10.4-1 to 3.10.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: python3.10 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.10.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for llvm-toolchain-11/1:11.1.0-6: amd64: Pass, arm64: Pass, i386: Not a regression, ppc64el: Ignored failure, s390x: Not a regression
    • autopkgtest for llvm-toolchain-11/blocked-on-ci-infra: armhf: Ignored failure
    • autopkgtest for llvm-toolchain-12/1:12.0.1-20: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Ignored failure, s390x: Not a regression
    • autopkgtest for llvm-toolchain-12/blocked-on-ci-infra: armhf: Ignored failure
    • autopkgtest for llvm-toolchain-13/1:13.0.1-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Ignored failure, s390x: Not a regression
    • autopkgtest for llvm-toolchain-13/blocked-on-ci-infra: armhf: Ignored failure
    • autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for python3.10/3.10.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• python3.9 (3.9.12-1 to 3.9.13-1)
  • Migration status for python3.9 (3.9.12-1 to 3.9.13-1): Will attempt migration (Any information below is purely informational)
    • Depends: python3.9 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.9.html
    • autopkgtest for llvm-toolchain-12/1:12.0.1-20: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Ignored failure, s390x: Not a regression
    • autopkgtest for llvm-toolchain-12/blocked-on-ci-infra: armhf: Ignored failure
    • autopkgtest for python3.9/3.9.13-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-argmax (- to 0.3.0-1)
  • Migration status for rust-argmax (- 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 sylvestre
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-argmax.html
    • autopkgtest for rust-argmax/0.3.0-1: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-ctrlc (3.2.1-1 to 3.2.2-3)
  • Migration status for rust-ctrlc (3.2.1-1 to 3.2.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ctrlc rust-nix (not considered)
    • Depends: rust-ctrlc rust-nix (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ctrlc.html
    • autopkgtest for rust-ctrlc/3.2.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-lalrpop (0.17.2-8 to 0.19.8-2)
  • Migration status for rust-lalrpop (0.17.2-8 to 0.19.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-lalrpop rustc (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-lalrpop rust-lalrpop-util
    • Depends: rust-lalrpop rust-lalrpop-util
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lalrpop.html
    • autopkgtest for rust-lalrpop/0.19.8-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-libmount (0.1.15-3 to 0.1.15-4)
  • Migration status for rust-libmount (0.1.15-3 to 0.1.15-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-libmount rust-quick-error (not considered)
    • Depends: rust-libmount rust-quick-error (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libmount.html
    • autopkgtest for rust-libmount/0.1.15-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-nom-locate (- to 4.0.0-2)
  • Migration status for rust-nom-locate (- to 4.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-nom-locate+generic-simd-dev/amd64 has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/arm64 has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/armel has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/armhf has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/i386 has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/mips64el has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/mipsel has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/ppc64el has unsatisfiable dependency
    • librust-nom-locate+generic-simd-dev/s390x has unsatisfiable dependency
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-nom-locate.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
• rust-num-threads (- to 0.1.6-1)
  • Migration status for rust-num-threads (- to 0.1.6-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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-threads.html
    • autopkgtest for rust-num-threads/0.1.6-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rust-rust-argon2 (- to 1.0.0-1)
  • Migration status for rust-rust-argon2 (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-rust-argon2/1.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rust-argon2.html
• rust-rusty-fork (0.2.1-1 to 0.2.1-2)
  • Migration status for rust-rusty-fork (0.2.1-1 to 0.2.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rusty-fork rust-quick-error (not considered)
    • Depends: rust-rusty-fork rust-quick-error (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating rust-rusty-fork will fix bugs in testing: #1012338
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rusty-fork.html
    • autopkgtest for rust-rusty-fork/0.2.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-sequoia-wot (- to 0.2.0-1)
  • Migration status for rust-sequoia-wot (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by dkg
    • Too young, only 3 of 5 days old
    • Built-Using: rust-sequoia-wot rustc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-wot.html
    • autopkgtest for rust-sequoia-wot/0.2.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rust-time (0.3.5-4 to 0.3.9-1)
  • Migration status for rust-time (0.3.5-4 to 0.3.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-time rust-num-threads (not considered)
    • Depends: rust-time rust-num-threads (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-time.html
    • autopkgtest for rust-time/0.3.9-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-unicode-ident (- to 1.0.0-1)
  • Migration status for rust-unicode-ident (- to 1.0.0-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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-unicode-ident.html
    • autopkgtest for rust-unicode-ident/1.0.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rust-zeroize (- to 1.5.5-1)
  • Migration status for rust-zeroize (- to 1.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-zeroize/1.5.5-1: amd64: Pass, arm64: Regression ♻ , armhf: Pass, i386: Regression ♻ , ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zeroize.html
• tiledb-py (0.14.0-1 to 0.15.3-1)
  • Migration status for tiledb-py (0.14.0-1 to 0.15.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
    • Depends: tiledb-py tiledb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledb-py.html
    • autopkgtest for tiledb-py/0.15.3-1: amd64: Pass, arm64: Pass, armhf: No test results, i386: No test results, ppc64el: Pass, s390x: No test results
• translation-finder (1.0-1 to 1.0-2)
  • Migration status for translation-finder (1.0-1 to 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/translation-finder.html
• tryton-client (6.0.14-1 to 6.0.16-1)
  • Migration status for tryton-client (6.0.14-1 to 6.0.16-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/t/tryton-client.html
    • autopkgtest for tryton-client/6.0.16-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• android-platform-external-boringssl (13~preview2-1~exp1 to 13~preview2-2)
  • Migration status for android-platform-external-boringssl (13~preview2-1~exp1 to 13~preview2-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/a/android-platform-external-boringssl.html
    • autopkgtest for android-platform-external-boringssl/13~preview2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: No test results
• bambootracker (0.4.6-1 to 0.5.0-1)
  • Migration status for bambootracker (0.4.6-1 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bambootracker.html
• biosig (2.3.3-1 to 2.4.0-2)
  • Migration status for biosig (2.3.3-1 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
    • Depends: biosig dcmtk
  • Additional info:
    • Updating biosig will fix bugs in testing: #1010545
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biosig.html
    • autopkgtest for biosig/2.4.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• brise (0.38.20210909-2 to 0.38.20210909-3)
  • Migration status for brise (0.38.20210909-2 to 0.38.20210909-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/b/brise.html
• busybox (1:1.30.1-7 to 1:1.35.0-1)
  • Migration status for busybox (1:1.30.1-7 to 1:1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/busybox.html
• colorclass (2.2.0-2.2 to 2.2.0-3)
  • Migration status for colorclass (2.2.0-2.2 to 2.2.0-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/c/colorclass.html
    • autopkgtest for colorclass/2.2.0-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• dcmtk (3.6.6-5 to 3.6.7-4)
  • Migration status for dcmtk (3.6.6-5 to 3.6.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dcmtk would introduce bugs in testing: #1010536
    • autopkgtest for biosig/2.3.3-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for odil/0.12.2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Depends: dcmtk openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcmtk.html
• directfb (1.7.7-9 to 1.7.7-11)
  • Migration status for directfb (1.7.7-9 to 1.7.7-11): 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/directfb.html
• dulwich (0.20.35-1 to 0.20.43-1)
  • Migration status for dulwich (0.20.35-1 to 0.20.43-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/d/dulwich.html
    • autopkgtest for dulwich/0.20.43-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• ebook2cwgui (0.1.2-5 to 0.1.2-6)
  • Migration status for ebook2cwgui (0.1.2-5 to 0.1.2-6): 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/ebook2cwgui.html
• fcitx5-solarized (- to 0.1-2)
  • Migration status for fcitx5-solarized (- to 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/f/fcitx5-solarized.html
• fonts-ibm-plex (6.0.0-1 to 6.0.2-1)
  • Migration status for fonts-ibm-plex (6.0.0-1 to 6.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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gammapy (- to 0.20-1)
  • Migration status for gammapy (- to 0.20-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): gammapy iminuit (not considered)
    • Depends: gammapy iminuit (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gammapy.html
    • autopkgtest for gammapy/0.20-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• gmp-ecm (7.0.4+ds-6 to 7.0.5+ds-1)
  • Migration status for gmp-ecm (7.0.4+ds-6 to 7.0.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gmp-ecm/7.0.5+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for sagemath/9.5-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmp-ecm.html
• gnome-initial-setup (42.1.1-1 to 42.2-1)
  • Migration status for gnome-initial-setup (42.1.1-1 to 42.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/g/gnome-initial-setup.html
• gnome-shell (42.1-1 to 42.2-1)
  • Migration status for gnome-shell (42.1-1 to 42.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/g/gnome-shell.html
• i3status (2.13-3 to 2.14-1)
  • Migration status for i3status (2.13-3 to 2.14-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/i/i3status.html
• kiwi (9.24.36-1 to 9.24.39-1)
  • Migration status for kiwi (9.24.36-1 to 9.24.39-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/kiwi.html
• ksmbd-tools (3.4.4-1 to 3.4.5-1)
  • Migration status for ksmbd-tools (3.4.4-1 to 3.4.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/k/ksmbd-tools.html
• lcov (1.15-2 to 1.16-1)
  • Migration status for lcov (1.15-2 to 1.16-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/lcov.html
• libapogee3 (3.2+20220127213450-1 to 3.2+20220606235519-1)
  • Migration status for libapogee3 (3.2+20220127213450-1 to 3.2+20220606235519-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/liba/libapogee3.html
• libasi (1.21.0-1 to 1.22+20220607002509-1)
  • Migration status for libasi (1.21.0-1 to 1.22+20220607002509-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libfishcamp (1.1-2 to 1.2+20220607003151-1)
  • Migration status for libfishcamp (1.1-2 to 1.2+20220607003151-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libfli (2.0-2 to 2.0+20220607003743-1)
  • Migration status for libfli (2.0-2 to 2.0+20220607003743-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/libf/libfli.html
• libopencsd (1.2.0-1 to 1.3.1-1)
  • Migration status for libopencsd (1.2.0-1 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libopencsd.html
• libpktriggercord (0.85.1-2 to 0.85.1+20220607004112-1)
  • Migration status for libpktriggercord (0.85.1-2 to 0.85.1+20220607004112-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/libp/libpktriggercord.html
• libtracefs (1.3.1-1 to 1.4.0-1)
  • Migration status for libtracefs (1.3.1-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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtracefs.html
• linux (5.17.3-1 to 5.18.2-1)
  • Migration status for linux (5.17.3-1 to 5.18.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for linux/5.18.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • autopkgtest for zfs-linux/2.1.4-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Depends: linux openssl
    • Implicit dependency: linux linux-signed-amd64
    • Implicit dependency: linux linux-signed-arm64
    • Implicit dependency: linux linux-signed-i386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
• maim (5.7.4-1 to 5.7.4-2)
  • Migration status for maim (5.7.4-1 to 5.7.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • maim/amd64 has unsatisfiable dependency
    • maim unsatisfiable Build-Depends(-Arch) on amd64: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on amd64: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on arm64: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on arm64: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on armel: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on armel: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on armhf: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on armhf: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on i386: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on i386: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on mips64el: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on mips64el: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on mipsel: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on mipsel: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on ppc64el: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on ppc64el: libslopy-dev
    • maim unsatisfiable Build-Depends(-Arch) on s390x: libslopy7.6
    • maim unsatisfiable Build-Depends(-Arch) on s390x: libslopy-dev
    • Not built on buildd: arch amd64 binaries uploaded by anarcat@koumbit.org
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on mipsel
    • missing build on ppc64el
    • 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:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/maim.html
    • uninstallable on arch amd64, not running autopkgtest there
• mathcomp-analysis (0.5.0-5 to 0.5.1-1)
  • Migration status for mathcomp-analysis (0.5.0-5 to 0.5.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/m/mathcomp-analysis.html
• merecat (- to 2.31+git20220513+ds-2)
  • Migration status for merecat (- to 2.31+git20220513+ds-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
    • Depends: merecat openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/merecat.html
• network-manager-sstp (- to 1.3.0-2)
  • Migration status for network-manager-sstp (- to 1.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 4 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/network-manager-sstp.html
• node-babel7 (7.17.11+~cs214.263.190-2 to 7.18.4+~cs214.249.185-2)
  • Migration status for node-babel7 (7.17.11+~cs214.263.190-2 to 7.18.4+~cs214.249.185-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-babel7.html
    • autopkgtest for node-babel7/7.18.4+~cs214.249.185-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• node-webpack (5.65.0+dfsg+~cs9.20.9-12 to 5.65.0+dfsg+~cs9.20.9-13)
  • Migration status for node-webpack (5.65.0+dfsg+~cs9.20.9-12 to 5.65.0+dfsg+~cs9.20.9-13): 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-webpack.html
• onedrive (2.4.13-1 to 2.4.18-0.1)
  • Migration status for onedrive (2.4.13-1 to 2.4.18-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 onedrive will fix bugs in testing: #988630
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onedrive.html
• owslib (0.25.0-1 to 0.26.0-1)
  • Migration status for owslib (0.25.0-1 to 0.26.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/o/owslib.html
• polymake (4.4-5 to 4.6-3)
  • Migration status for polymake (4.4-5 to 4.6-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/polymake.html
• projectm (3.1.12-1 to 3.1.12-2)
  • Migration status for projectm (3.1.12-1 to 3.1.12-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/projectm.html
• pt2-clone (1.46+ds-1 to 1.49+ds-1)
  • Migration status for pt2-clone (1.46+ds-1 to 1.49+ds-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/p/pt2-clone.html
• pyment (- to 0.3.4+ds-2)
  • Migration status for pyment (- to 0.3.4+ds-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/pyment.html
• python-django-contact-form (1.9-1 to 2.0.1-1)
  • Migration status for python-django-contact-form (1.9-1 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-contact-form.html
• python-etcd (0.4.5-2 to 0.4.5-3)
  • Migration status for python-etcd (0.4.5-2 to 0.4.5-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/python-etcd.html
• python-flask-jwt-extended (4.3.1-2 to 4.4.1-1)
  • Migration status for python-flask-jwt-extended (4.3.1-2 to 4.4.1-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flask-jwt-extended.html
    • autopkgtest for python-flask-jwt-extended/4.4.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• python-hpilo (4.3-3 to 4.4.3-1)
  • Migration status for python-hpilo (4.3-3 to 4.4.3-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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hpilo.html
• python-internetarchive (3.0.0-1 to 3.0.1-1)
  • Migration status for python-internetarchive (3.0.0-1 to 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-internetarchive.html
    • autopkgtest for python-internetarchive/3.0.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-moderngl (- to 5.6.4-2)
  • Migration status for python-moderngl (- to 5.6.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-moderngl.html
• python-pgpdump (1.5-2 to 1.5-3)
  • Migration status for python-pgpdump (1.5-2 to 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pgpdump.html
• python-releases (1.6.3-1 to 1.6.3-2)
  • Migration status for python-releases (1.6.3-1 to 1.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 4 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-releases.html
    • autopkgtest for python-releases/1.6.3-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• r-bioc-genomicfeatures (1.48.1+dfsg-1 to 1.48.3+dfsg-1)
  • Migration status for r-bioc-genomicfeatures (1.48.1+dfsg-1 to 1.48.3+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/r/r-bioc-genomicfeatures.html
    • autopkgtest for r-bioc-genomicfeatures/1.48.3+dfsg-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rime-cantonese (0.0~git20220505.6c1c5f1-1 to 0.0~git20220602.d98ab28-1)
  • Migration status for rime-cantonese (0.0~git20220505.6c1c5f1-1 to 0.0~git20220602.d98ab28-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/r/rime-cantonese.html
• rime-soutzoe (- to 0.0~git20190120.beeaeca-3)
  • Migration status for rime-soutzoe (- to 0.0~git20190120.beeaeca-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/r/rime-soutzoe.html
• rocksdb (6.11.4-3 to 7.2.2-3)
  • Migration status for rocksdb (6.11.4-3 to 7.2.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 rocksdb will fix bugs in testing: #984325
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocksdb.html
• ruby-gitlab-markup (- to 1.8.0-2)
  • Migration status for ruby-gitlab-markup (- to 1.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-markup would introduce bugs in testing: #1011444
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-markup.html
    • autopkgtest for ruby-gitlab-markup/1.8.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• rust-bindgen (0.59.2-2 to 0.60.1-1)
  • Migration status for rust-bindgen (0.59.2-2 to 0.60.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-bindgen+default-dev/0.60.1-1/amd64 to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/amd64 uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/arm64 to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/arm64 uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/armel to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/armel uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/armhf to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/armhf uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/i386 to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/i386 uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/mips64el to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/mips64el uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/mipsel to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/mipsel uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/ppc64el to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/ppc64el uninstallable
    • migrating librust-bindgen+default-dev/0.60.1-1/s390x to testing makes librust-xkbcommon-sys-dev/0.7.5-1+b1/s390x uninstallable
    • Too young, only 4 of 5 days old
    • Built-Using: rust-bindgen rustc
    • Implicit dependency: rust-bindgen rust-exacl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bindgen.html
    • autopkgtest for rust-bindgen/0.60.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• rygel (0.40.3-1 to 0.40.4-1)
  • Migration status for rygel (0.40.3-1 to 0.40.4-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/r/rygel.html
• sgmllib3k (1.0.0-3 to 1.0.0-4)
  • Migration status for sgmllib3k (1.0.0-3 to 1.0.0-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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sgmllib3k.html
    • autopkgtest for sgmllib3k/1.0.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• snd (22.3-1 to 22.4-1)
  • Migration status for snd (22.3-1 to 22.4-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
    • Build-Depends(-Arch): snd notcurses
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snd.html
• sphinxcontrib-log-cabinet (1.0.1-2 to 1.0.1-3)
  • Migration status for sphinxcontrib-log-cabinet (1.0.1-2 to 1.0.1-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/s/sphinxcontrib-log-cabinet.html
• sphinxtesters (0.2.3-1 to 0.2.3-2)
  • Migration status for sphinxtesters (0.2.3-1 to 0.2.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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxtesters.html
• tclxml (1:3.2.7-6 to 1:3.2.7-7)
  • Migration status for tclxml (1:3.2.7-6 to 1:3.2.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/t/tclxml.html
• terminus (1.16.0-1 to 1.17.0-1)
  • Migration status for terminus (1.16.0-1 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terminus.html
• tio (1.37-1 to 1.38-1)
  • Migration status for tio (1.37-1 to 1.38-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/tio.html
• traitlets (5.2.1-1 to 5.2.2-1)
  • Migration status for traitlets (5.2.1-1 to 5.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/traitlets.html
• uftrace (- to 0.11-6)
  • Migration status for uftrace (- to 0.11-6): 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uftrace.html
• vimix (- to 0.7.0+git20220523+ds-2)
  • Migration status for vimix (- to 0.7.0+git20220523+ds-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/v/vimix.html
• virtualbox (- to 6.1.34-dfsg-3)
  • Migration status for virtualbox (- to 6.1.34-dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #794466
    • Too young, only 4 of 5 days old
    • Depends: virtualbox openssl
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• x42-plugins (20220327-1 to 20220605-1)
  • Migration status for x42-plugins (20220327-1 to 20220605-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/x/x42-plugins.html
    • autopkgtest for x42-plugins/20220605-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• zbackup (1.5-1 to 1.5-2)
  • Migration status for zbackup (1.5-1 to 1.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
    • Depends: zbackup openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zbackup.html
• amphp-amp (- to 2.6.2-1)
  • Migration status for amphp-amp (- to 2.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amphp-amp.html
    • 5 days old (needed 5 days)
• apt-listdifferences (1.20190206 to 1.20220605)
  • Migration status for apt-listdifferences (1.20190206 to 1.20220605): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating apt-listdifferences will fix bugs in testing: #1011763
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-listdifferences.html
    • 5 days old (needed 5 days)
• avahi (0.8-5 to 0.8-6)
  • Migration status for avahi (0.8-5 to 0.8-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avahi.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • 5 days old (needed 5 days)
• cdlabelgen (4.3.0-1.1 to 4.3.0-2)
  • Migration status for cdlabelgen (4.3.0-1.1 to 4.3.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdlabelgen.html
    • 5 days old (needed 5 days)
• chafa (1.10.3-1 to 1.12.0-1)
  • Migration status for chafa (1.10.3-1 to 1.12.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chafa.html
    • autopkgtest for chafa/1.12.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 5 days old (needed 5 days)
• christianriesen-otp (- to 1.4.3-1)
  • Migration status for christianriesen-otp (- to 1.4.3-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/christianriesen-otp.html
    • autopkgtest for christianriesen-otp/1.4.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• courier-filter-perl (0.200+ds-4 to 0.200+ds-5)
  • Migration status for courier-filter-perl (0.200+ds-4 to 0.200+ds-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-filter-perl.html
    • autopkgtest for courier-filter-perl/0.200+ds-5: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 5 days old (needed 5 days)
• ddcci-driver-linux (0.4.2-1 to 0.4.2-2)
  • Migration status for ddcci-driver-linux (0.4.2-1 to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ddcci-driver-linux/0.4.2-2: amd64: No test results, arm64: Regression ♻ , armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddcci-driver-linux.html
    • 5 days old (needed 5 days)
• dizzy (0.3-3.1 to 0.3-4)
  • Migration status for dizzy (0.3-3.1 to 0.3-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dizzy.html
    • autopkgtest for dizzy/0.3-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 5 days old (needed 5 days)
• dovecot (1:2.3.18+dfsg1-1 to 1:2.3.19+dfsg1-1)
  • Migration status for dovecot (1:2.3.18+dfsg1-1 to 1:2.3.19+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating dovecot-core/1:2.3.19+dfsg1-1/amd64 to testing makes dovecot-antispam/2.0+20171229-1+b10/amd64 uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/amd64 to testing makes dovecot-fts-xapian/1.5.5-1/amd64 uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/arm64 to testing makes dovecot-antispam/2.0+20171229-1+b10/arm64 uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/arm64 to testing makes dovecot-fts-xapian/1.5.5-1/arm64 uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/armel to testing makes dovecot-antispam/2.0+20171229-1+b10/armel uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/armel to testing makes dovecot-fts-xapian/1.5.5-1/armel uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/armhf to testing makes dovecot-antispam/2.0+20171229-1+b10/armhf uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/armhf to testing makes dovecot-fts-xapian/1.5.5-1/armhf uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/i386 to testing makes dovecot-antispam/2.0+20171229-1+b10/i386 uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/i386 to testing makes dovecot-fts-xapian/1.5.5-1/i386 uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/mips64el to testing makes dovecot-antispam/2.0+20171229-1+b10/mips64el uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/mips64el to testing makes dovecot-fts-xapian/1.5.5-1/mips64el uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/mipsel to testing makes dovecot-antispam/2.0+20171229-1+b10/mipsel uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/mipsel to testing makes dovecot-fts-xapian/1.5.5-1/mipsel uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/ppc64el to testing makes dovecot-antispam/2.0+20171229-1+b10/ppc64el uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/ppc64el to testing makes dovecot-fts-xapian/1.5.5-1/ppc64el uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/s390x to testing makes dovecot-antispam/2.0+20171229-1+b10/s390x uninstallable
    • migrating dovecot-core/1:2.3.19+dfsg1-1/s390x to testing makes dovecot-fts-xapian/1.5.5-1/s390x uninstallable
    • Depends: dovecot openssl
  • Additional info:
    • Updating dovecot will fix bugs in testing: #1009872, #996273
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dovecot.html
    • autopkgtest for dovecot/1:2.3.19+dfsg1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 5 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:
    • 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:
    • 5 days old (needed 5 days)
• ebook2cw (0.8.3-2 to 0.8.4-1)
  • Migration status for ebook2cw (0.8.3-2 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ebook2cw.html
    • 5 days old (needed 5 days)
• ell (0.50-1 to 0.51-1)
  • Migration status for ell (0.50-1 to 0.51-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ell.html
    • 5 days old (needed 5 days)
• fcitx5-nord (- to 0.0~git20210727.bdaa8fb-2)
  • Migration status for fcitx5-nord (- to 0.0~git20210727.bdaa8fb-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fcitx5-nord.html
    • 5 days old (needed 5 days)
• flask-jwt-extended (- to 4.4.0-1)
  • Migration status for flask-jwt-extended (- to 4.4.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/f/flask-jwt-extended.html
    • autopkgtest for flask-jwt-extended/4.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• fonts-navilu (1.2-3 to 1.2-4)
  • Migration status for fonts-navilu (1.2-3 to 1.2-4): 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/f/fonts-navilu.html
• gajim (1.4.0-1 to 1.4.3-1)
  • Migration status for gajim (1.4.0-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gajim.html
    • 5 days old (needed 5 days)
• gajim-antispam (1.6.4-1 to 1.6.5-1)
  • Migration status for gajim-antispam (1.6.4-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gajim-antispam.html
    • 5 days old (needed 5 days)
• gajim-lengthnotifier (1.4.4-1 to 1.4.5-1)
  • Migration status for gajim-lengthnotifier (1.4.4-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gajim-lengthnotifier.html
    • 5 days old (needed 5 days)
• gajim-omemo (2.8.14-1 to 2.8.15-1)
  • Migration status for gajim-omemo (2.8.14-1 to 2.8.15-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gajim-omemo.html
    • 5 days old (needed 5 days)
• gajim-pgp (1.4.5-1 to 1.4.6-1)
  • Migration status for gajim-pgp (1.4.5-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gajim-pgp.html
    • 5 days old (needed 5 days)
• gemmi (0.5.4+ds-1 to 0.5.5+ds-1)
  • Migration status for gemmi (0.5.4+ds-1 to 0.5.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for finalcif/104+dfsg-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: No test results, s390x: Not a regression
    • autopkgtest for gemmi/0.5.5+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gemmi.html
    • 5 days old (needed 5 days)
• geos (3.10.2-1 to 3.10.3-1)
  • Migration status for geos (3.10.2-1 to 3.10.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geos.html
    • 5 days old (needed 5 days)
• golang-raven-go (0.0~git20150721.0.74c334d-5 to 0.2.0+ds1-2)
  • Migration status for golang-raven-go (0.0~git20150721.0.74c334d-5 to 0.2.0+ds1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-raven-go.html
    • 5 days old (needed 5 days)
• guidata (2.0.4-1 to 2.2.1-1)
  • Migration status for guidata (2.0.4-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guidata.html
    • 5 days old (needed 5 days)
• guiqwt (- to 4.2.0-1)
  • Migration status for guiqwt (- to 4.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on ppc64el
    • missing build on s390x
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): guiqwt guidata
    • Depends: guiqwt guidata
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guiqwt.html
    • 5 days old (needed 5 days)
• i7z (0.27.2+git2013.10.12-g5023138-7 to 0.27.2+git2013.10.12-g5023138-8)
  • Migration status for i7z (0.27.2+git2013.10.12-g5023138-7 to 0.27.2+git2013.10.12-g5023138-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i7z.html
    • 5 days old (needed 5 days)
• ibus-sunpinyin (2.0.3+git20181120-5 to 2.0.3+git20210228-1)
  • Migration status for ibus-sunpinyin (2.0.3+git20181120-5 to 2.0.3+git20210228-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-sunpinyin.html
    • 5 days old (needed 5 days)
• iwd (1.27-1 to 1.28-1)
  • Migration status for iwd (1.27-1 to 1.28-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): iwd ell
    • Depends: iwd ell
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iwd.html
    • autopkgtest for iwd/1.28-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• jabberd2 (2.7.0-2 to 2.7.0-4)
  • Migration status for jabberd2 (2.7.0-2 to 2.7.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: jabberd2 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jabberd2.html
    • 5 days old (needed 5 days)
• kephra (0.4.3.34+dfsg-2.1 to 0.4.3.34+dfsg-3)
  • Migration status for kephra (0.4.3.34+dfsg-2.1 to 0.4.3.34+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for kephra/0.4.3.34+dfsg-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kephra.html
    • 5 days old (needed 5 days)
• kwalletmanager (4:21.12.3-1 to 4:22.04.1-1)
  • Migration status for kwalletmanager (4:21.12.3-1 to 4:22.04.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwalletmanager.html
    • 5 days old (needed 5 days)
• leafnode (1.11.11-5 to 1.12.0-1)
  • Migration status for leafnode (1.11.11-5 to 1.12.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leafnode.html
    • 5 days old (needed 5 days)
• libacme-constant-perl (0.1.3-1.1 to 0.1.3-2)
  • Migration status for libacme-constant-perl (0.1.3-1.1 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libacme-constant-perl/0.1.3-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libacme-constant-perl.html
    • 5 days old (needed 5 days)
• libafs-pag-perl (1.02-2 to 1.02-3)
  • Migration status for libafs-pag-perl (1.02-2 to 1.02-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libafs-pag-perl/1.02-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libafs-pag-perl.html
    • 5 days old (needed 5 days)
• libalzabo-perl (0.92-4.1 to 0.92-5)
  • Migration status for libalzabo-perl (0.92-4.1 to 0.92-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libalzabo-perl/0.92-5: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libalzabo-perl.html
    • 5 days old (needed 5 days)
• libanyevent-cachedns-perl (0.08-2.1 to 0.08-3)
  • Migration status for libanyevent-cachedns-perl (0.08-2.1 to 0.08-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libanyevent-cachedns-perl.html
    • autopkgtest for libanyevent-cachedns-perl/0.08-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 5 days old (needed 5 days)
• libanyevent-i3-perl (0.17-1 to 0.17-2)
  • Migration status for libanyevent-i3-perl (0.17-1 to 0.17-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libanyevent-i3-perl.html
    • autopkgtest for libanyevent-i3-perl/0.17-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 5 days old (needed 5 days)
• libblockdev (2.26-1 to 2.27-1)
  • Migration status for libblockdev (2.26-1 to 2.27-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libblockdev.html
    • 5 days old (needed 5 days)
• libbpf (0.7.0-2 to 0.8.0-1)
  • Migration status for libbpf (0.7.0-2 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbpf.html
    • 5 days old (needed 5 days)
• libica (3.2.0-4 to 3.9.0-1)
  • Migration status for libica (3.2.0-4 to 3.9.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libica openssl
  • Additional info:
    • Updating libica will fix bugs in testing: #1011042
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 5 days old (needed 5 days)
• libmodule-build-using-pkgconfig-perl (0.03-1 to 0.03-2)
  • Migration status for libmodule-build-using-pkgconfig-perl (0.03-1 to 0.03-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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmodule-build-using-pkgconfig-perl.html
    • autopkgtest for libmodule-build-using-pkgconfig-perl/0.03-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libsys-info-perl (0.7811-2 to 0.7811-3)
  • Migration status for libsys-info-perl (0.7811-2 to 0.7811-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsys-info-perl.html
    • autopkgtest for libsys-info-perl/0.7811-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• libthrust (1.15.0-4 to 1.15.0-6)
  • Migration status for libthrust (1.15.0-4 to 1.15.0-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libthrust.html
    • autopkgtest for libthrust/1.15.0-6: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Ignored failure
    • 5 days old (needed 5 days)
• libtraceevent (1:1.5.3-1 to 1:1.6.0-1)
  • Migration status for libtraceevent (1:1.5.3-1 to 1:1.6.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtraceevent.html
    • 5 days old (needed 5 days)
• lttoolbox (3.6.4-1 to 3.6.6-1)
  • Migration status for lttoolbox (3.6.4-1 to 3.6.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lttoolbox.html
    • 5 days old (needed 5 days)
• obs-downstream-keyer (0.2.2-1 to 0.2.3-1)
  • Migration status for obs-downstream-keyer (0.2.2-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): obs-downstream-keyer obs-studio/s390x
    • Depends: obs-downstream-keyer obs-studio/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-downstream-keyer.html
    • autopkgtest for obs-downstream-keyer/0.2.3-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 5 days old (needed 5 days)
• opencl-clang-14 (- to 14.0.0-1)
  • Migration status for opencl-clang-14 (- to 14.0.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencl-clang-14.html
    • 5 days old (needed 5 days)
• opencu (3-2 to 3-3)
  • Migration status for opencu (3-2 to 3-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating opencu will fix bugs in testing: #1011420
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencu.html
    • 5 days old (needed 5 days)
• pampi (1.1+dfsg1-4 to 1.1+dfsg1-5)
  • Migration status for pampi (1.1+dfsg1-4 to 1.1+dfsg1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pampi.html
    • 5 days old (needed 5 days)
• php-symfony-polyfill (1.25.0-3 to 1.26.0-1)
  • Migration status for php-symfony-polyfill (1.25.0-3 to 1.26.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-symfony-polyfill/1.26.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating php-symfony-polyfill will fix bugs in testing: #1012307
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-symfony-polyfill.html
    • 5 days old (needed 5 days)
• proftpd-mod-kafka (- to 0.1-1)
  • Migration status for proftpd-mod-kafka (- to 0.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proftpd-mod-kafka.html
    • 5 days old (needed 5 days)
• python-django (2:3.2.13-1 to 2:4.0.5-1)
  • Migration status for python-django (2:3.2.13-1 to 2:4.0.5-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django.html
    • 5 days old (needed 5 days)
• python-nbxmpp (3.0.1-1 to 3.1.0-1)
  • Migration status for python-nbxmpp (3.0.1-1 to 3.1.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nbxmpp.html
    • 5 days old (needed 5 days)
• rpmlint (2.2.0+ds1-0.2 to 2.3.0+ds1-0.1)
  • Migration status for rpmlint (2.2.0+ds1-0.2 to 2.3.0+ds1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rpmlint/2.3.0+ds1-0.1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpmlint.html
    • 5 days old (needed 5 days)
• rtl8723bt-firmware (- to 20181104-1)
  • Migration status for rtl8723bt-firmware (- to 20181104-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 5 days old (needed 5 days)
• rust-atomic (- to 0.5.1-1)
  • Migration status for rust-atomic (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-atomic/0.5.1-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-atomic.html
    • 5 days old (needed 5 days)
• rust-dfrs (0.0.7-2 to 0.0.7-4)
  • Migration status for rust-dfrs (0.0.7-2 to 0.0.7-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-dfrs rustc (not considered)
    • Invalidated by built-using
    • Built-Using: rust-dfrs rust-nix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dfrs.html
    • 5 days old (needed 5 days)
• rust-lalrpop-util (0.17.2-1 to 0.19.8-1)
  • Migration status for rust-lalrpop-util (0.17.2-1 to 0.19.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-lalrpop-util rust-lalrpop (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lalrpop-util.html
    • autopkgtest for rust-lalrpop-util/0.19.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• selinux-python (3.3-1 to 3.4-1)
  • Migration status for selinux-python (3.3-1 to 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): selinux-python libselinux (not considered)
    • Depends: selinux-python libselinux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): selinux-python libsepol
    • Built-Using: selinux-python libsepol
    • Depends: selinux-python checkpolicy
    • Depends: selinux-python libsemanage
    • Depends: selinux-python policycoreutils
    • Depends: selinux-python selinux-dbus
    • Depends: selinux-python semodule-utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/selinux-python.html
    • 5 days old (needed 5 days)
• spectra (- to 1.0.1-2)
  • Migration status for spectra (- to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spectra.html
    • 5 days old (needed 5 days)
• sphinx-paramlinks (0.5.2-1 to 0.5.4-1)
  • Migration status for sphinx-paramlinks (0.5.2-1 to 0.5.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-paramlinks.html
    • 5 days old (needed 5 days)
• valijson (- to 0.6+repack-1)
  • Migration status for valijson (- to 0.6+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by dkogan, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valijson.html
    • 5 days old (needed 5 days)
• vkd3d (1.1-5 to 1.2-12)
  • Migration status for vkd3d (1.1-5 to 1.2-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vkd3d unsatisfiable Build-Depends(-Arch) on s390x: libvkd3d-headers (= 1.2-12) [!i386 !amd64]
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating vkd3d will fix bugs in testing: #1010331
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vkd3d.html
    • 5 days old (needed 5 days)
• wine (6.0.3~repack-1 to 7.0~repack-1)
  • Migration status for wine (6.0.3~repack-1 to 7.0~repack-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): wine vkd3d
    • Depends: wine vkd3d
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine.html
    • 5 days old (needed 5 days)
• xmltooling (3.2.1-1 to 3.2.1-2)
  • Migration status for xmltooling (3.2.1-1 to 3.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for opensaml/3.2.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for xmltooling/3.2.1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Not built on buildd: upload info for arch mipsel binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
    • Depends: xmltooling openssl
  • Additional info:
    • Updating xmltooling will fix bugs in testing: #1006581
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmltooling.html
    • 5 days old (needed 5 days)
• zint (2.10.0-1 to 2.11.0-1)
  • Migration status for zint (2.10.0-1 to 2.11.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zint.html
    • 5 days old (needed 5 days)
• encore-clojure (- to 3.22.0-1)
  • Migration status for encore-clojure (- to 3.22.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jerome@riseup.net, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): encore-clojure truss-clojure
    • Depends: encore-clojure truss-clojure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/encore-clojure.html
    • autopkgtest for encore-clojure/3.22.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 6 days old (needed 5 days)
• frescobaldi (3.1.3+ds1-1 to 3.2+ds1-1)
  • Migration status for frescobaldi (3.1.3+ds1-1 to 3.2+ds1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: frescobaldi python-qpageview (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating frescobaldi will fix bugs in testing: #1009369
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frescobaldi.html
    • 6 days old (needed 5 days)
• libdecaf (- to 1.0.1-1)
  • Migration status for libdecaf (- 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 berni@birkenwald.de
    • Not built on buildd: arch all binaries uploaded by berni@birkenwald.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdecaf.html
    • 6 days old (needed 5 days)
• libsemanage (3.3-1 to 3.4-1)
  • Migration status for libsemanage (3.3-1 to 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): libsemanage libselinux (not considered)
    • Depends: libsemanage libselinux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): libsemanage libsepol
    • Build-Depends(-Arch): libsemanage secilc
    • Depends: libsemanage libsepol
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsemanage.html
    • 6 days old (needed 5 days)
• murphy-clojure (- to 0.5.2-1)
  • Migration status for murphy-clojure (- to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jerome@riseup.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/murphy-clojure.html
    • autopkgtest for murphy-clojure/0.5.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• obs-scene-collection-manager (0.0.4-2 to 0.0.6-1)
  • Migration status for obs-scene-collection-manager (0.0.4-2 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): obs-scene-collection-manager obs-studio/s390x
    • Depends: obs-scene-collection-manager obs-studio/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-scene-collection-manager.html
    • autopkgtest for obs-scene-collection-manager/0.0.6-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 6 days old (needed 5 days)
• odr-padenc (- to 3.0.0-1)
  • Migration status for odr-padenc (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kilobyte
    • Too young, only 6 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odr-padenc.html
• php-horde-turba (- to 4.2.25-6)
  • Migration status for php-horde-turba (- to 4.2.25-6): 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-data (not considered)
    • Invalidated by dependency
    • Depends: php-horde-turba php-horde
    • Depends: php-horde-turba php-horde-auth
    • Depends: php-horde-turba php-horde-content
    • Depends: php-horde-turba php-horde-core
    • Depends: php-horde-turba php-horde-dav
    • Depends: php-horde-turba php-horde-form
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
    • autopkgtest for php-horde-turba/4.2.25-6: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 6 days old (needed 5 days)
• policycoreutils (3.3-1 to 3.4-1)
  • Migration status for policycoreutils (3.3-1 to 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): policycoreutils libselinux (not considered)
    • Depends: policycoreutils libselinux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): policycoreutils libsemanage
    • Build-Depends(-Arch): policycoreutils libsepol
    • Depends: policycoreutils libsemanage
    • Depends: policycoreutils libsepol
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/policycoreutils.html
    • 6 days old (needed 5 days)
• python-junit-xml (1.9-1 to 1.9-2)
  • Migration status for python-junit-xml (1.9-1 to 1.9-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-junit-xml.html
    • autopkgtest for python-junit-xml/1.9-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• python-simpy (- to 2.3.1+dfsg-3)
  • Migration status for python-simpy (- to 2.3.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-simpy would introduce bugs in testing: #955055
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-simpy.html
    • 6 days old (needed 5 days)
• python-testing.mysqld (- to 1.4.0-5)
  • Migration status for python-testing.mysqld (- to 1.4.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-testing.mysqld would introduce bugs in testing: #978259
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-testing.mysqld.html
    • 6 days old (needed 5 days)
• python-testing.postgresql (- to 1.3.0-3)
  • Migration status for python-testing.postgresql (- to 1.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-testing.postgresql would introduce bugs in testing: #1002361
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-testing.postgresql.html
    • 6 days old (needed 5 days)
• python-whoosh (2.7.4+git6-g9134ad92-5 to 2.7.4+git6-g9134ad92-6)
  • Migration status for python-whoosh (2.7.4+git6-g9134ad92-5 to 2.7.4+git6-g9134ad92-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-whoosh.html
• routes (2.5.1-1 to 2.5.1-2)
  • Migration status for routes (2.5.1-1 to 2.5.1-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routes.html
    • 6 days old (needed 5 days)
• rspamd (3.2-1 to 3.2-3)
  • Migration status for rspamd (3.2-1 to 3.2-3): Will attempt migration (Any information below is purely informational)
    • Depends: rspamd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rspamd.html
    • autopkgtest for rspamd/3.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• rust-condure (1.3.1-1 to 1.6.0-2)
  • Migration status for rust-condure (1.3.1-1 to 1.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-condure rustc (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-condure rust-sha1
    • Depends: rust-condure openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-condure.html
    • autopkgtest for rust-condure/1.6.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 6 days old (needed 5 days)
• rust-dns-parser (0.8.0-1 to 0.8.0-2)
  • Migration status for rust-dns-parser (0.8.0-1 to 0.8.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-dns-parser rust-quick-error (not considered)
    • Depends: rust-dns-parser rust-quick-error (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dns-parser.html
    • autopkgtest for rust-dns-parser/0.8.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• rust-hyperfine (1.13.0-1 to 1.14.0-2)
  • Migration status for rust-hyperfine (1.13.0-1 to 1.14.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-hyperfine rustc (not considered)
    • Invalidated by built-using
    • Built-Using: rust-hyperfine rust-nix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyperfine.html
    • 6 days old (needed 5 days)
• rust-sniffglue (0.15.0-1 to 0.15.0-2)
  • Migration status for rust-sniffglue (0.15.0-1 to 0.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-sniffglue rustc (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-sniffglue rust-nix
    • Build-Depends(-Arch): rust-sniffglue rust-sha2
    • Built-Using: rust-sniffglue rust-nix
    • Depends: rust-sniffglue rust-nix
    • Depends: rust-sniffglue rust-sha2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sniffglue.html
    • autopkgtest for rust-sniffglue/0.15.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• singledispatch (3.4.0.3-3 to 3.4.0.3-4)
  • Migration status for singledispatch (3.4.0.3-3 to 3.4.0.3-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singledispatch.html
• sleekxmpp (- to 1.3.3-7)
  • Migration status for sleekxmpp (- to 1.3.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sleekxmpp would introduce bugs in testing: #1009476
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sleekxmpp.html
    • 6 days old (needed 5 days)
• sphinxcontrib-rubydomain (- to 0.1~dev-20100804-3)
  • Migration status for sphinxcontrib-rubydomain (- to 0.1~dev-20100804-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sphinxcontrib-rubydomain would introduce bugs in testing: #896395
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-rubydomain.html
    • 6 days old (needed 5 days)
• tiledb (2.8.2-1 to 2.9.3-1)
  • Migration status for tiledb (2.8.2-1 to 2.9.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: tiledb openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledb.html
    • 6 days old (needed 5 days)
• tinydb (- to 3.15.2-3)
  • Migration status for tinydb (- to 3.15.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinydb would introduce bugs in testing: #1002394
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinydb.html
    • 6 days old (needed 5 days)
• truss-clojure (- to 1.6.0.8.g3eed445-1)
  • Migration status for truss-clojure (- to 1.6.0.8.g3eed445-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jerome@riseup.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/truss-clojure.html
    • autopkgtest for truss-clojure/1.6.0.8.g3eed445-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 6 days old (needed 5 days)
• trustedqsl (2.5.9-2 to 2.6.3-1)
  • Migration status for trustedqsl (2.5.9-2 to 2.6.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: trustedqsl openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trustedqsl.html
    • 6 days old (needed 5 days)
• u-boot-menu (4.0.4 to 4.0.5)
  • Migration status for u-boot-menu (4.0.4 to 4.0.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/u-boot-menu.html
    • 6 days old (needed 5 days)
• vsts-cd-manager (1.0.2-3 to 1.0.2-4)
  • Migration status for vsts-cd-manager (1.0.2-3 to 1.0.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vsts-cd-manager.html
    • autopkgtest for vsts-cd-manager/1.0.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
• checkpolicy (3.3-1 to 3.4-1)
  • Migration status for checkpolicy (3.3-1 to 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): checkpolicy libsepol (not considered)
    • Built-Using: checkpolicy libsepol (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/checkpolicy.html
    • 7 days old (needed 5 days)
• gifticlib (1.0.9-4 to 1.0.9-5)
  • Migration status for gifticlib (1.0.9-4 to 1.0.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gifticlib/1.0.9-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gifticlib.html
    • 7 days old (needed 5 days)
• libselinux (3.3-1 to 3.4-1)
  • Migration status for libselinux (3.3-1 to 3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for glib2.0/2.72.1-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libselinux/3.4-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • Build-Depends(-Arch): libselinux libsepol
    • Built-Using: libselinux libsepol
    • Depends: libselinux libsepol
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libselinux.html
    • 7 days old (needed 5 days)
• libsepol (3.3-1 to 3.4-1)
  • Migration status for libsepol (3.3-1 to 3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsepol would introduce bugs in testing: #1012503
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsepol.html
    • 7 days old (needed 5 days)
• mcstrans (3.3-1 to 3.4-1)
  • Migration status for mcstrans (3.3-1 to 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): mcstrans libselinux (not considered)
    • Depends: mcstrans libselinux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): mcstrans libsepol
    • Built-Using: mcstrans libsepol
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mcstrans.html
    • 7 days old (needed 5 days)
• mkdocstrings-python-handlers (- to 0.7.0-2)
  • Migration status for mkdocstrings-python-handlers (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mkdocstrings-python-handlers unsatisfiable Build-Depends-Indep on amd64: mkdocstrings (>> 0.19.0-1)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends-Indep: mkdocstrings-python-handlers mkdocs-material
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocstrings-python-handlers.html
    • 7 days old (needed 5 days)
• mkdocstrings-python-legacy (- to 0.2.3-1)
  • Migration status for mkdocstrings-python-legacy (- to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mkdocstrings-python-legacy unsatisfiable Build-Depends-Indep on amd64: mkdocstrings (>> 0.19.0-1)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends-Indep: mkdocstrings-python-legacy mkdocs-material
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocstrings-python-legacy.html
    • 7 days old (needed 5 days)
• plasma-gmailfeed (1.1-2 to 1.2-1)
  • Migration status for plasma-gmailfeed (1.1-2 to 1.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-gmailfeed.html
• python-cassandra-driver (- to 3.25.0-1)
  • Migration status for python-cassandra-driver (- to 3.25.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cassandra-driver.html
    • 7 days old (needed 5 days)
• python-gflags (1.5.1-7 to 1.5.1-8)
  • Migration status for python-gflags (1.5.1-7 to 1.5.1-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 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gflags.html
• python-httptools (0.1.1-1 to 0.1.1-2)
  • Migration status for python-httptools (0.1.1-1 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 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-httptools.html
    • autopkgtest for python-httptools/0.1.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-ldapdomaindump (0.9.3-1 to 0.9.3-2)
  • Migration status for python-ldapdomaindump (0.9.3-1 to 0.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 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ldapdomaindump.html
    • autopkgtest for python-ldapdomaindump/0.9.3-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-noise (1.2.3-3 to 1.2.3-4)
  • Migration status for python-noise (1.2.3-3 to 1.2.3-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-noise.html
• python-notify2 (0.3-4 to 0.3-5)
  • Migration status for python-notify2 (0.3-4 to 0.3-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-notify2.html
• python-peakutils (1.3.3+ds-2 to 1.3.3+ds-3)
  • Migration status for python-peakutils (1.3.3+ds-2 to 1.3.3+ds-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-peakutils.html
    • autopkgtest for python-peakutils/1.3.3+ds-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 7 days)
• python-repoze.tm2 (2.0-2 to 2.0-3)
  • Migration status for python-repoze.tm2 (2.0-2 to 2.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-repoze.tm2.html
• python-requirements-detector (- to 0.6-3)
  • Migration status for python-requirements-detector (- to 0.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-requirements-detector would introduce bugs in testing: #997298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-requirements-detector.html
    • autopkgtest for python-requirements-detector/0.6-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• restorecond (3.3-1 to 3.4-1)
  • Migration status for restorecond (3.3-1 to 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): restorecond libselinux (not considered)
    • Depends: restorecond libselinux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restorecond.html
    • 7 days old (needed 5 days)
• rust-bs58 (0.4.0-1 to 0.4.0-2)
  • Migration status for rust-bs58 (0.4.0-1 to 0.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-bs58 rust-sha2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bs58.html
    • autopkgtest for rust-bs58/0.4.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• rust-ouroboros (- to 0.15.0-1)
  • Migration status for rust-ouroboros (- to 0.15.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-ouroboros rust-aliasable (not considered)
    • Depends: rust-ouroboros rust-aliasable (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ouroboros.html
    • autopkgtest for rust-ouroboros/0.15.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• rust-sha2-asm (0.5.1-3 to 0.6.2-2)
  • Migration status for rust-sha2-asm (0.5.1-3 to 0.6.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-sha2-asm rust-sha2 (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha2-asm.html
    • autopkgtest for rust-sha2-asm/0.6.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• rust-syn (1.0.76-1 to 1.0.94-1)
  • Migration status for rust-syn (1.0.76-1 to 1.0.94-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-serde-derive/1.0.136-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-syn/1.0.94-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-syn.html
    • 7 days old (needed 5 days)
• rust-uuid (0.8.1-4 to 0.8.1-5)
  • Migration status for rust-uuid (0.8.1-4 to 0.8.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-uuid rust-sha1 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-uuid.html
    • autopkgtest for rust-uuid/0.8.1-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• secilc (3.3-1 to 3.4-1)
  • Migration status for secilc (3.3-1 to 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): secilc libsepol (not considered)
    • Depends: secilc libsepol (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): secilc checkpolicy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/secilc.html
    • 7 days old (needed 5 days)
• selinux-dbus (3.3-1 to 3.4-1)
  • Migration status for selinux-dbus (3.3-1 to 3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: selinux-dbus libselinux (not considered)
    • Invalidated by dependency
    • Depends: selinux-dbus policycoreutils
    • Depends: selinux-dbus selinux-python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/selinux-dbus.html
    • 7 days old (needed 5 days)
• semodule-utils (3.3-1 to 3.4-1)
  • Migration status for semodule-utils (3.3-1 to 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): semodule-utils libsepol (not considered)
    • Depends: semodule-utils libsepol (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/semodule-utils.html
    • 7 days old (needed 5 days)
• unicode (2.8-1.1 to 2.9-1)
  • Migration status for unicode (2.8-1.1 to 2.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 7 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicode.html
• coturn (4.5.2-3 to 4.5.2-3.1)
  • Migration status for coturn (4.5.2-3 to 4.5.2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coturn/4.5.2-3.1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Depends: coturn openssl
  • Additional info:
    • Updating coturn will fix bugs in testing: #995659
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coturn.html
    • 8 days old (needed 5 days)
• libvirt (8.3.0-1 to 8.4.0-1)
  • Migration status for libvirt (8.3.0-1 to 8.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libvirt glusterfs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvirt.html
    • autopkgtest for libvirt/8.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• pyasn1 (0.4.8-1 to 0.4.8-2)
  • Migration status for pyasn1 (0.4.8-1 to 0.4.8-2): 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/pyasn1.html
    • autopkgtest for pyasn1/0.4.8-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• pynliner (0.8.0-2 to 0.8.0-3)
  • Migration status for pynliner (0.8.0-2 to 0.8.0-3): 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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 8 days old (needed 5 days)
• pyrad (2.1-2 to 2.1-3)
  • Migration status for pyrad (2.1-2 to 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 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrad.html
• pytest-bdd (- to 3.2.1-2)
  • Migration status for pytest-bdd (- to 3.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-bdd would introduce bugs in testing: #977079
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-bdd.html
• pytest-vcr (1.0.2-2 to 1.0.2-3)
  • Migration status for pytest-vcr (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 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-vcr.html
    • autopkgtest for pytest-vcr/1.0.2-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
• python-aioinflux (- to 0.9.0-3)
  • Migration status for python-aioinflux (- to 0.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioinflux would introduce bugs in testing: #996579
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioinflux.html
    • 8 days old (needed 5 days)
• rapid-photo-downloader (- to 0.9.33-1)
  • Migration status for rapid-photo-downloader (- to 0.9.33-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rapid-photo-downloader would introduce bugs in testing: #1001652
    • Depends: rapid-photo-downloader show-in-file-manager
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rapid-photo-downloader.html
    • 8 days old (needed 5 days)
• rust-block-cipher-trait (0.6.2-3 to 0.6.2-4)
  • Migration status for rust-block-cipher-trait (0.6.2-3 to 0.6.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-block-cipher-trait rust-blobby (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-block-cipher-trait.html
    • autopkgtest for rust-block-cipher-trait/0.6.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-cbindgen (0.21.0-1 to 0.23.0-1)
  • Migration status for rust-cbindgen (0.21.0-1 to 0.23.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-cbindgen rustc (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-cbindgen rust-syn
    • Depends: rust-cbindgen rust-syn
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cbindgen.html
    • autopkgtest for rust-cbindgen/0.23.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-hkdf (0.10.0-1 to 0.12.3-1)
  • Migration status for rust-hkdf (0.10.0-1 to 0.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-hkdf rust-secret-service (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-hkdf rust-hmac
    • Depends: rust-hkdf rust-hmac
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hkdf.html
    • autopkgtest for rust-hkdf/0.12.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-hmac (0.10.1-2 to 0.12.1-1)
  • Migration status for rust-hmac (0.10.1-2 to 0.12.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-hmac rust-libsystemd (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-hmac rust-digest
    • Depends: rust-hmac rust-digest
    • Implicit dependency: rust-hmac rust-hkdf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hmac.html
    • autopkgtest for rust-hmac/0.12.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-libsystemd (0.2.1-2 to 0.2.1-3)
  • Migration status for rust-libsystemd (0.2.1-2 to 0.2.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-libsystemd rust-sha2 (not considered)
    • Depends: rust-libsystemd rust-sha2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-libsystemd rust-hmac
    • Depends: rust-libsystemd rust-hmac
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libsystemd.html
    • autopkgtest for rust-libsystemd/0.2.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-md-5 (- to 0.10.1-1)
  • Migration status for rust-md-5 (- to 0.10.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-md-5 rust-md5-asm (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-md-5 rust-digest
    • Depends: rust-md-5 rust-digest
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-md-5.html
    • autopkgtest for rust-md-5/0.10.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 8 days old (needed 5 days)
• rust-md5-asm (- to 0.5.0-1)
  • Migration status for rust-md5-asm (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-md5-asm/0.5.0-1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-md5-asm.html
    • 8 days old (needed 5 days)
• rust-onig (6.1.0-1 to 6.3.1-1)
  • Migration status for rust-onig (6.1.0-1 to 6.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-onig/6.3.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-onig.html
    • 8 days old (needed 5 days)
• rust-secret-service (2.0.1-1 to 2.0.1-2)
  • Migration status for rust-secret-service (2.0.1-1 to 2.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): rust-secret-service rust-sha2 (not considered)
    • Depends: rust-secret-service rust-sha2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-secret-service rust-hkdf
    • Depends: rust-secret-service rust-hkdf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-secret-service.html
    • autopkgtest for rust-secret-service/2.0.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 8 days old (needed 5 days)
• rust-stream-cipher (0.3.2-2 to 0.3.2-3)
  • Migration status for rust-stream-cipher (0.3.2-2 to 0.3.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-stream-cipher rust-blobby (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-stream-cipher.html
    • autopkgtest for rust-stream-cipher/0.3.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• squid (5.5-1 to 5.5-1.1)
  • Migration status for squid (5.5-1 to 5.5-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: squid openssl
  • Additional info:
    • Updating squid will fix bugs in testing: #1005650
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squid.html
    • autopkgtest for squid/5.5-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• unbound (1.15.0-8 to 1.16.0-2)
  • Migration status for unbound (1.15.0-8 to 1.16.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: unbound openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unbound.html
    • autopkgtest for unbound/1.16.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• astroquery (0.4.1+dfsg-7 to 0.4.6+dfsg-3)
  • Migration status for astroquery (0.4.1+dfsg-7 to 0.4.6+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for astroquery/0.4.6+dfsg-3: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating astroquery will fix bugs in testing: #1012554
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astroquery.html
    • 9 days old (needed 5 days)
• coq-hierarchy-builder (1.2.1-9 to 1.2.1-10)
  • Migration status for coq-hierarchy-builder (1.2.1-9 to 1.2.1-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-hierarchy-builder coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-hierarchy-builder.html
    • 9 days old (needed 5 days)
• coquelicot (3.2.0-2 to 3.2.0-4)
  • Migration status for coquelicot (3.2.0-2 to 3.2.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coquelicot coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coquelicot.html
    • autopkgtest for coquelicot/3.2.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• ejabberd (21.12-1 to 22.05-1)
  • Migration status for ejabberd (21.12-1 to 22.05-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): ejabberd erlang-p1-pgsql
    • Build-Depends(-Arch): ejabberd erlang-p1-sip
    • Build-Depends(-Arch): ejabberd erlang-p1-stun
    • Build-Depends(-Arch): ejabberd erlang-p1-tls
    • Build-Depends(-Arch): ejabberd erlang-p1-xmpp
    • Depends: ejabberd erlang-p1-stun
    • Depends: ejabberd erlang-p1-tls
    • Depends: ejabberd erlang-p1-xmpp
    • Implicit dependency: ejabberd ejabberd-contrib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ejabberd.html
    • autopkgtest for ejabberd/22.05-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• ejabberd-contrib (0.2021.11.25~dfsg0-1 to 0.2022.04.12~dfsg0-1)
  • Migration status for ejabberd-contrib (0.2021.11.25~dfsg0-1 to 0.2022.04.12~dfsg0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): ejabberd-contrib ejabberd
    • Depends: ejabberd-contrib ejabberd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ejabberd-contrib.html
    • 9 days old (needed 5 days)
• erlang-p1-pgsql (1.1.16-1 to 1.1.18-1)
  • Migration status for erlang-p1-pgsql (1.1.16-1 to 1.1.18-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): erlang-p1-pgsql erlang-p1-tls
    • Build-Depends(-Arch): erlang-p1-pgsql erlang-p1-xmpp
    • Depends: erlang-p1-pgsql erlang-p1-tls
    • Depends: erlang-p1-pgsql erlang-p1-xmpp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-pgsql.html
    • 9 days old (needed 5 days)
• erlang-p1-sip (1.0.45-1 to 1.0.47-1)
  • Migration status for erlang-p1-sip (1.0.45-1 to 1.0.47-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): erlang-p1-sip erlang-p1-stun
    • Build-Depends(-Arch): erlang-p1-sip erlang-p1-tls
    • Depends: erlang-p1-sip erlang-p1-stun
    • Depends: erlang-p1-sip erlang-p1-tls
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-sip.html
    • 9 days old (needed 5 days)
• erlang-p1-stun (1.1.0-1 to 1.2.2-1)
  • Migration status for erlang-p1-stun (1.1.0-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): erlang-p1-stun erlang-p1-tls
    • Depends: erlang-p1-stun erlang-p1-tls
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-stun.html
    • 9 days old (needed 5 days)
• erlang-p1-tls (1.1.13-2 to 1.1.15-1)
  • Migration status for erlang-p1-tls (1.1.13-2 to 1.1.15-1): Will attempt migration (Any information below is purely informational)
    • Depends: erlang-p1-tls openssl
  • Additional info:
    • Updating erlang-p1-tls will fix bugs in testing: #1006343
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-tls.html
    • 9 days old (needed 5 days)
• erlang-p1-xmpp (1.5.6-1 to 1.5.8-1)
  • Migration status for erlang-p1-xmpp (1.5.6-1 to 1.5.8-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): erlang-p1-xmpp erlang-p1-tls
    • Depends: erlang-p1-xmpp erlang-p1-tls
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-xmpp.html
    • 9 days old (needed 5 days)
• kronosnet (1.23-2 to 1.24-1)
  • Migration status for kronosnet (1.23-2 to 1.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: kronosnet openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kronosnet.html
    • autopkgtest for kronosnet/1.24-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• mathcomp-algebra-tactics (1.0.0-2 to 1.0.0-3)
  • Migration status for mathcomp-algebra-tactics (1.0.0-2 to 1.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-algebra-tactics coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-algebra-tactics.html
    • 9 days old (needed 5 days)
• mathcomp-bigenough (1.0.1-5 to 1.0.1-6)
  • Migration status for mathcomp-bigenough (1.0.1-5 to 1.0.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-bigenough coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-bigenough.html
    • 9 days old (needed 5 days)
• mathcomp-finmap (1.5.1-5 to 1.5.1-6)
  • Migration status for mathcomp-finmap (1.5.1-5 to 1.5.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-finmap coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-finmap.html
    • 9 days old (needed 5 days)
• mathcomp-multinomials (1.5.5-4 to 1.5.5-5)
  • Migration status for mathcomp-multinomials (1.5.5-4 to 1.5.5-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-multinomials coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-multinomials.html
    • 9 days old (needed 5 days)
• mathcomp-real-closed (1.1.2-2 to 1.1.2-3)
  • Migration status for mathcomp-real-closed (1.1.2-2 to 1.1.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-real-closed coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-real-closed.html
    • 9 days old (needed 5 days)
• mathcomp-zify (1.2.0+1.12+8.13-3 to 1.2.0+1.12+8.13-4)
  • Migration status for mathcomp-zify (1.2.0+1.12+8.13-3 to 1.2.0+1.12+8.13-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mathcomp-zify coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathcomp-zify.html
    • 9 days old (needed 5 days)
• mkdocstrings (- to 0.19.0-2)
  • Migration status for mkdocstrings (- to 0.19.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
    • Build-Depends-Indep: mkdocstrings mkdocs-material
    • Build-Depends-Indep: mkdocstrings mkdocstrings-python-handlers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocstrings.html
    • 9 days old (needed 5 days)
• passenger (6.0.10-3 to 6.0.13+ds-1)
  • Migration status for passenger (6.0.10-3 to 6.0.13+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: passenger openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/passenger.html
    • autopkgtest for passenger/6.0.13+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• pypdf2 (1.26.0-4 to 2.0.0-1)
  • Migration status for pypdf2 (1.26.0-4 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pypdf2 would introduce bugs in testing: #1010820, #1010821
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypdf2.html
    • 9 days old (needed 5 days)
• rust-blake3 (1.2.0-3 to 1.3.1-1)
  • Migration status for rust-blake3 (1.2.0-3 to 1.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-blake3 rust-digest (not considered)
    • Depends: rust-blake3 rust-digest (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-blake3.html
    • autopkgtest for rust-blake3/1.3.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 9 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, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ioctl-sys.html
    • 9 days old (needed 5 days)
• rust-lscolors (0.8.1-2 to 0.10.0-1)
  • Migration status for rust-lscolors (0.8.1-2 to 0.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-lscolors rustc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lscolors.html
    • autopkgtest for rust-lscolors/0.10.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• rust-quick-error (1.2.3-1 to 2.0.1-1)
  • Migration status for rust-quick-error (1.2.3-1 to 2.0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Implicit dependency: rust-quick-error rust-proptest (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-quick-error rust-dns-parser
    • Implicit dependency: rust-quick-error rust-libmount
    • Implicit dependency: rust-quick-error rust-rusty-fork
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-quick-error.html
    • autopkgtest for rust-quick-error/2.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• squeekboard (1.17.1-1 to 1.18.0-1)
  • Migration status for squeekboard (1.17.1-1 to 1.18.0-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/s/squeekboard.html
    • 9 days old (needed 5 days)
• ssreflect (1.14.0-9 to 1.14.0-11)
  • Migration status for ssreflect (1.14.0-9 to 1.14.0-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ssreflect coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssreflect.html
    • autopkgtest for ssreflect/1.14.0-11: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• aac-tactics (8.15.1-4 to 8.15.1-5)
  • Migration status for aac-tactics (8.15.1-4 to 8.15.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aac-tactics coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aac-tactics.html
    • 10 days old (needed 5 days)
• coq (8.15.1+dfsg-1 to 8.15.2+dfsg-1)
  • Migration status for coq (8.15.1+dfsg-1 to 8.15.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: coq coq-elpi (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: coq aac-tactics
    • Implicit dependency: coq coq-bignums
    • Implicit dependency: coq coq-hierarchy-builder
    • Implicit dependency: coq coquelicot
    • Implicit dependency: coq mathcomp-algebra-tactics
    • Implicit dependency: coq mathcomp-bigenough
    • Implicit dependency: coq mathcomp-finmap
    • Implicit dependency: coq mathcomp-multinomials
    • Implicit dependency: coq mathcomp-real-closed
    • Implicit dependency: coq mathcomp-zify
    • Implicit dependency: coq paramcoq
    • Implicit dependency: coq ssreflect
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq.html
    • autopkgtest for coq/8.15.2+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• coq-bignums (8.15.0-1 to 8.15.0-3)
  • Migration status for coq-bignums (8.15.0-1 to 8.15.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-bignums coq (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-bignums.html
    • autopkgtest for coq-bignums/8.15.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• coq-elpi (1.13.0-7 to 1.14.0-3)
  • Migration status for coq-elpi (1.13.0-7 to 1.14.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: coq-elpi menhir (not considered)
    • Invalidated by dependency
    • Depends: coq-elpi coq
    • Depends: coq-elpi elpi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coq-elpi.html
    • 10 days old (needed 5 days)
• dotenv-cli (2.2.0-1 to 3.0.0-1)
  • Migration status for dotenv-cli (2.2.0-1 to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by venthur, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dotenv-cli.html
    • autopkgtest for dotenv-cli/3.0.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 10 days old (needed 5 days)
• falkon (3.2.0+dfsg1-1 to 3.2.0+dfsg1-2)
  • Migration status for falkon (3.2.0+dfsg1-1 to 3.2.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Depends: falkon openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/falkon.html
    • 10 days old (needed 5 days)
• gradle (4.4.1-13 to 4.4.1-14)
  • Migration status for gradle (4.4.1-13 to 4.4.1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gradle would introduce bugs in testing: #1012214
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gradle.html
    • 10 days old (needed 5 days)
• libstrophe (0.11.0-1 to 0.12.0-4)
  • Migration status for libstrophe (0.11.0-1 to 0.12.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: libstrophe openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libstrophe.html
    • 10 days old (needed 5 days)
• mktorrent (1.1-2 to 1.1-3)
  • Migration status for mktorrent (1.1-2 to 1.1-3): Will attempt migration (Any information below is purely informational)
    • Depends: mktorrent openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mktorrent.html
    • 10 days old (needed 5 days)
• node-mimic-response (3.1.0-7 to 3.1.0-8)
  • Migration status for node-mimic-response (3.1.0-7 to 3.1.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-mimic-response/3.1.0-8: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating node-mimic-response will fix bugs in testing: #1011912
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mimic-response.html
    • 10 days old (needed 5 days)
• orthanc-postgresql (4.0-5 to 4.0-6)
  • Migration status for orthanc-postgresql (4.0-5 to 4.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-postgresql orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-postgresql.html
    • 10 days old (needed 5 days)
• orthanc-webviewer (2.8-1 to 2.8-2)
  • Migration status for orthanc-webviewer (2.8-1 to 2.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-webviewer orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-webviewer.html
    • 10 days old (needed 5 days)
• ovn (21.06.0+ds1-3 to 21.06.0+ds1-14)
  • Migration status for ovn (21.06.0+ds1-3 to 21.06.0+ds1-14): Will attempt migration (Any information below is purely informational)
    • Depends: ovn openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ovn.html
    • 10 days old (needed 5 days)
• r-cran-tmb (1.8.1-1 to 1.9.0-1)
  • Migration status for r-cran-tmb (1.8.1-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-glmmtmb/1.1.3-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for r-cran-tmb/1.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tmb.html
    • 10 days old (needed 5 days)
• rust-blobby (0.1.1-1 to 0.3.1-1)
  • Migration status for rust-blobby (0.1.1-1 to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-blobby rust-digest (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-blobby rust-block-cipher-trait
    • Implicit dependency: rust-blobby rust-stream-cipher
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-blobby.html
    • autopkgtest for rust-blobby/0.3.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-block-buffer (0.9.0-4 to 0.10.2-1)
  • Migration status for rust-block-buffer (0.9.0-4 to 0.10.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-block-buffer rust-sha2 (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-block-buffer rust-sha3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-block-buffer.html
    • autopkgtest for rust-block-buffer/0.10.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-digest (0.9.0-1 to 0.10.3-1)
  • Migration status for rust-digest (0.9.0-1 to 0.10.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-digest rust-sha2 (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-digest rust-block-buffer
    • Depends: rust-digest rust-blobby
    • Depends: rust-digest rust-block-buffer
    • Implicit dependency: rust-digest rust-blake3
    • Implicit dependency: rust-digest rust-hkdf
    • Implicit dependency: rust-digest rust-hmac
    • Implicit dependency: rust-digest rust-sha3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-digest.html
    • autopkgtest for rust-digest/0.10.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-sha1 (0.6.0-1 to 0.10.1-1)
  • Migration status for rust-sha1 (0.6.0-1 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-sha1-dev/0.10.1-1/amd64 to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/amd64 uninstallable
    • migrating librust-sha1-dev/0.10.1-1/arm64 to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/arm64 uninstallable
    • migrating librust-sha1-dev/0.10.1-1/armel to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/armel uninstallable
    • migrating librust-sha1-dev/0.10.1-1/armhf to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/armhf uninstallable
    • migrating librust-sha1-dev/0.10.1-1/i386 to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/i386 uninstallable
    • migrating librust-sha1-dev/0.10.1-1/mips64el to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/mips64el uninstallable
    • migrating librust-sha1-dev/0.10.1-1/mipsel to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/mipsel uninstallable
    • migrating librust-sha1-dev/0.10.1-1/ppc64el to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/ppc64el uninstallable
    • migrating librust-sha1-dev/0.10.1-1/s390x to testing makes librust-stdweb-internal-macros-dev/0.2.9-1/s390x uninstallable
    • Build-Depends(-Arch): rust-sha1 rust-digest
    • Depends: rust-sha1 rust-digest
    • Implicit dependency: rust-sha1 rust-uuid
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha1.html
    • autopkgtest for rust-sha1/0.10.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 10 days old (needed 5 days)
• rust-sha2 (0.9.2-2 to 0.10.2-1)
  • Migration status for rust-sha2 (0.9.2-2 to 0.10.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-sha2 rust-lalrpop (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-sha2 rust-digest
    • Depends: rust-sha2 rust-digest
    • Depends: rust-sha2 rust-sha2-asm
    • Implicit dependency: rust-sha2 rust-bs58
    • Implicit dependency: rust-sha2 rust-libsystemd
    • Implicit dependency: rust-sha2 rust-secret-service
    • Implicit dependency: rust-sha2 rust-sniffglue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha2.html
    • autopkgtest for rust-sha2/0.10.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 10 days old (needed 5 days)
• rust-sha3 (0.9.1-1 to 0.10.1-1)
  • Migration status for rust-sha3 (0.9.1-1 to 0.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): rust-sha3 rust-digest (not considered)
    • Depends: rust-sha3 rust-digest (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha3.html
    • autopkgtest for rust-sha3/0.10.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 10 days old (needed 5 days)
• xilinx-bootgen (2021.2-1 to 2022.1-1)
  • Migration status for xilinx-bootgen (2021.2-1 to 2022.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: xilinx-bootgen openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xilinx-bootgen.html
    • 10 days old (needed 5 days)
• bacula (9.6.7-4 to 9.6.7-5)
  • Migration status for bacula (9.6.7-4 to 9.6.7-5): Will attempt migration (Any information below is purely informational)
    • Depends: bacula openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bacula.html
    • autopkgtest for bacula/9.6.7-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• fplll (5.4.1-1 to 5.4.2-1)
  • Migration status for fplll (5.4.1-1 to 5.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fpylll/0.5.2+ds1-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fplll.html
    • 11 days old (needed 5 days)
• jruby-openssl (- to 0.9.21-4)
  • Migration status for jruby-openssl (- to 0.9.21-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): jruby-openssl jruby (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby-openssl.html
    • 11 days old (needed 5 days)
• llvm-toolchain-12 (1:12.0.1-20 to 1:12.0.1-21)
  • Migration status for llvm-toolchain-12 (1:12.0.1-20 to 1:12.0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-12.html
    • autopkgtest for llvm-toolchain-12/1:12.0.1-21: amd64: Pass, arm64: Pass, armhf: Test in progress (will not be considered a regression), i386: Pass, ppc64el: Ignored failure, s390x: Not a regression
    • 11 days old (needed 5 days)
• openvpn (2.5.6-1 to 2.6.0~git20220518+dco-2)
  • Migration status for openvpn (2.5.6-1 to 2.6.0~git20220518+dco-2): Will attempt migration (Any information below is purely informational)
    • Depends: openvpn openssl
  • Additional info:
    • Updating openvpn will fix bugs in testing: #1006519
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvpn.html
    • autopkgtest for openvpn/2.6.0~git20220518+dco-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 11 days old (needed 5 days)
• opusfile (0.9+20170913-1.1 to 0.12-2)
  • Migration status for opusfile (0.9+20170913-1.1 to 0.12-2): Will attempt migration (Any information below is purely informational)
    • Depends: opusfile openssl
  • Additional info:
    • Updating opusfile will fix bugs in testing: #965762
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opusfile.html
    • autopkgtest for opusfile/0.12-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• python-popcon (2.0.4 to 3.0.1)
  • Migration status for python-popcon (2.0.4 to 3.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by venthur, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-popcon.html
    • 11 days old (needed 5 days)
• r-cran-packrat (0.7.0-1 to 0.8.0-1)
  • Migration status for r-cran-packrat (0.7.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-packrat/0.8.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-packrat.html
    • 11 days old (needed 5 days)
• rust-resource-proof (- to 1.0.38-2)
  • Migration status for rust-resource-proof (- to 1.0.38-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-resource-proof rustc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-resource-proof.html
    • autopkgtest for rust-resource-proof/1.0.38-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• solvespace (3.0.rc2+repack1-3 to 3.1~rc1+ds1-1)
  • Migration status for solvespace (3.0.rc2+repack1-3 to 3.1~rc1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for solvespace/3.1~rc1+ds1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/solvespace.html
    • 11 days old (needed 5 days)
• wesnoth-1.16 (1:1.16.2-2 to 1:1.16.3-1)
  • Migration status for wesnoth-1.16 (1:1.16.2-2 to 1:1.16.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: wesnoth-1.16 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wesnoth-1.16.html
    • 11 days old (needed 5 days)
• creddump7 (- to 0.1+git20190429-1)
  • Migration status for creddump7 (- to 0.1+git20190429-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mika, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/creddump7.html
    • 12 days old (needed 5 days)
• dicomnifti (2.33.1-3 to 2.33.1-4)
  • Migration status for dicomnifti (2.33.1-3 to 2.33.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dicomnifti/2.33.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ , ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dicomnifti.html
    • 12 days old (needed 5 days)
• golang-github-google-goterm (- to 0.0~git20200907.555d40f-2)
  • Migration status for golang-github-google-goterm (- to 0.0~git20200907.555d40f-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-google-goterm/0.0~git20200907.555d40f-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-goterm.html
    • 12 days old (needed 5 days)
• groonga (12.0.2-1 to 12.0.3-2)
  • Migration status for groonga (12.0.2-1 to 12.0.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: groonga openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/groonga.html
    • autopkgtest for groonga/12.0.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• kappanhang (- to 1.3-2)
  • Migration status for kappanhang (- to 1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kappanhang golang-github-google-goterm (not considered)
    • Built-Using: kappanhang golang-github-google-goterm (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kappanhang.html
    • autopkgtest for kappanhang/1.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• fontmath (0.9.1-1 to 0.9.2-1)
  • Migration status for fontmath (0.9.1-1 to 0.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): fontmath fonttools (not considered)
    • Depends: fontmath fonttools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fontmath.html
    • autopkgtest for fontmath/0.9.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• fontparts (0.10.4-1 to 0.10.5-1)
  • Migration status for fontparts (0.10.4-1 to 0.10.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): fontparts fonttools (not considered)
    • Depends: fontparts fonttools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fontparts.html
    • autopkgtest for fontparts/0.10.5-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 13 days old (needed 5 days)
• fonttools (4.32.0-1 to 4.33.3-1)
  • Migration status for fonttools (4.32.0-1 to 4.33.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fonttools/4.33.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for glyphslib/5.3.2+ds1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonttools.html
    • 13 days old (needed 5 days)
• freeradius (3.0.25+dfsg-1.1 to 3.2.0+dfsg-1)
  • Migration status for freeradius (3.0.25+dfsg-1.1 to 3.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: freeradius openssl
  • Additional info:
    • Updating freeradius will fix bugs in testing: #1011041
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeradius.html
    • autopkgtest for freeradius/3.2.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• gcc-9-cross-ports (- to 25)
  • Migration status for gcc-9-cross-ports (- to 25): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross-ports would introduce bugs in testing: #994135
    • 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
    • 13 days old (needed 5 days)
• globus-ftp-client (9.6-1 to 9.8-1)
  • Migration status for globus-ftp-client (9.6-1 to 9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-ftp-client openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-ftp-client.html
    • 13 days old (needed 5 days)
• globus-gass-copy (10.10-1 to 10.12-1)
  • Migration status for globus-gass-copy (10.10-1 to 10.12-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gass-copy openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gass-copy.html
    • 13 days old (needed 5 days)
• globus-gatekeeper (11.3-2 to 11.4-1)
  • Migration status for globus-gatekeeper (11.3-2 to 11.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gatekeeper openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gatekeeper.html
    • 13 days old (needed 5 days)
• globus-gram-job-manager (15.6-1 to 15.8-1)
  • Migration status for globus-gram-job-manager (15.6-1 to 15.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gram-job-manager openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gram-job-manager.html
    • 13 days old (needed 5 days)
• globus-gridftp-server (13.22-1 to 13.24-1)
  • Migration status for globus-gridftp-server (13.22-1 to 13.24-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gridftp-server openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gridftp-server.html
    • 13 days old (needed 5 days)
• globus-gsi-cert-utils (10.8-1 to 10.10-1)
  • Migration status for globus-gsi-cert-utils (10.8-1 to 10.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-cert-utils openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gsi-cert-utils.html
    • 13 days old (needed 5 days)
• globus-gsi-openssl-error (4.3-2 to 4.4-1)
  • Migration status for globus-gsi-openssl-error (4.3-2 to 4.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-openssl-error openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gsi-openssl-error.html
    • 13 days old (needed 5 days)
• globus-gsi-proxy-core (9.6-1 to 9.8-1)
  • Migration status for globus-gsi-proxy-core (9.6-1 to 9.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-proxy-core openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gsi-proxy-core.html
    • 13 days old (needed 5 days)
• globus-gsi-sysconfig (9.4-1 to 9.5-1)
  • Migration status for globus-gsi-sysconfig (9.4-1 to 9.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gsi-sysconfig openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gsi-sysconfig.html
    • 13 days old (needed 5 days)
• globus-gssapi-gsi (14.17-1 to 14.20-1)
  • Migration status for globus-gssapi-gsi (14.17-1 to 14.20-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-gssapi-gsi openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gssapi-gsi.html
    • 13 days old (needed 5 days)
• globus-proxy-utils (7.2-1 to 7.3-1)
  • Migration status for globus-proxy-utils (7.2-1 to 7.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: globus-proxy-utils openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-proxy-utils.html
    • 13 days old (needed 5 days)
• glusterfs (10.1-3 to 10.2-1)
  • Migration status for glusterfs (10.1-3 to 10.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: glusterfs openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glusterfs.html
    • autopkgtest for glusterfs/10.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 13 days old (needed 5 days)
• golang-github-gorilla-schema (- to 1.2.0-1)
  • Migration status for golang-github-gorilla-schema (- to 1.2.0-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gorilla-schema.html
    • autopkgtest for golang-github-gorilla-schema/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• golang-github-muka-go-bluetooth (- to 5.60-1)
  • Migration status for golang-github-muka-go-bluetooth (- to 5.60-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by alteholz
    • 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/g/golang-github-muka-go-bluetooth.html
    • autopkgtest for golang-github-muka-go-bluetooth/5.60-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• golang-github-stefanberger-go-pkcs11uri (- to 0.0~git20201008.78d3cae-1)
  • Migration status for golang-github-stefanberger-go-pkcs11uri (- to 0.0~git20201008.78d3cae-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-stefanberger-go-pkcs11uri.html
    • autopkgtest for golang-github-stefanberger-go-pkcs11uri/0.0~git20201008.78d3cae-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• liquidsoap (2.0.2-1 to 2.0.5-1)
  • Migration status for liquidsoap (2.0.2-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: liquidsoap openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/liquidsoap.html
    • autopkgtest for liquidsoap/2.0.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• mosh (1.3.2-2.1 to 1.3.2-2.2)
  • Migration status for mosh (1.3.2-2.1 to 1.3.2-2.2): Will attempt migration (Any information below is purely informational)
    • Depends: mosh openssl
  • Additional info:
    • Updating mosh will fix bugs in testing: #1005718
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mosh.html
    • 13 days old (needed 5 days)
• myproxy (6.2.9-2 to 6.2.14-1)
  • Migration status for myproxy (6.2.9-2 to 6.2.14-1): Will attempt migration (Any information below is purely informational)
    • Depends: myproxy openssl
  • Additional info:
    • Updating myproxy will fix bugs in testing: #1006510
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/myproxy.html
    • 13 days old (needed 5 days)
• php-brick-math (- to 0.9.3-1)
  • Migration status for php-brick-math (- to 0.9.3-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-brick-math.html
    • autopkgtest for php-brick-math/0.9.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 7 days)
• php-graham-campbell-result-type (- to 1.0.4-1)
  • Migration status for php-graham-campbell-result-type (- 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 taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-graham-campbell-result-type.html
    • autopkgtest for php-graham-campbell-result-type/1.0.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 7 days)
• php-laravel-serializable-closure (- to 1.0.5-1)
  • Migration status for php-laravel-serializable-closure (- to 1.0.5-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-laravel-serializable-closure.html
    • 13 days old (needed 10 days)
• php-ramsey-collection (- to 1.2.2-1)
  • Migration status for php-ramsey-collection (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-ramsey-collection/1.2.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • php-ramsey-collection unsatisfiable Build-Depends(-Arch) on amd64: php-faker
    • 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-ramsey-collection.html
    • 13 days old (needed 10 days)
• php-voku-portable-ascii (- to 1.5.6-1)
  • Migration status for php-voku-portable-ascii (- to 1.5.6-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-voku-portable-ascii.html
    • autopkgtest for php-voku-portable-ascii/1.5.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 7 days)
• r-cran-openssl (2.0.0+dfsg-1 to 2.0.2+dfsg-1)
  • Migration status for r-cran-openssl (2.0.0+dfsg-1 to 2.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: r-cran-openssl openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-openssl.html
    • autopkgtest for r-cran-openssl/2.0.2+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• tb-goodies (- to 1.0.0)
  • Migration status for tb-goodies (- to 1.0.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • webext-tb-goodies/amd64 has unsatisfiable dependency
    • webext-tb-goodies/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tb-goodies.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 13 days old (needed 5 days)
• yaru-theme (- to 22.04.4+dfsg-1)
  • Migration status for yaru-theme (- to 22.04.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaru-theme.html
    • 13 days old (needed 5 days)
• alt-ergo (2.0.0-8 to 2.4.1-2)
  • Migration status for alt-ergo (2.0.0-8 to 2.4.1-2): 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 mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alt-ergo.html
    • autopkgtest for alt-ergo/2.4.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• astropy (5.0.4-1 to 5.1-1)
  • Migration status for astropy (5.0.4-1 to 5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for astroplan/0.7-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for astropy/5.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for astroquery/0.4.1+dfsg-7: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for hipspy/0.2-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for pydl/1.0.0~rc2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
    • autopkgtest for pyregion/2.1.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astropy.html
    • 14 days old (needed 5 days)
• ausweisapp2 (1.22.5-1 to 1.22.7-1)
  • Migration status for ausweisapp2 (1.22.5-1 to 1.22.7-1): Will attempt migration (Any information below is purely informational)
    • Depends: ausweisapp2 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ausweisapp2.html
    • 14 days old (needed 5 days)
• binaryen (105-1 to 108-1)
  • Migration status for binaryen (105-1 to 108-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating binaryen/108-1/amd64 to testing makes emscripten/3.1.5~dfsg-3/amd64 uninstallable
    • migrating binaryen/108-1/arm64 to testing makes emscripten/3.1.5~dfsg-3/arm64 uninstallable
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binaryen.html
    • 14 days old (needed 5 days)
• gcc-9-cross (- to 27)
  • Migration status for gcc-9-cross (- to 27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross would introduce bugs in testing: #994134
    • 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
    • 14 days old (needed 5 days)
• haskell-hsyaml (0.2.1.0-2 to 0.2.1.1-1)
  • Migration status for haskell-hsyaml (0.2.1.0-2 to 0.2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-hsyaml-dev/0.2.1.1-1/amd64 to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/amd64 uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/amd64 to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/amd64 uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/amd64 to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/amd64 uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/amd64 to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/amd64 uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/arm64 to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/arm64 uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/arm64 to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/arm64 uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/arm64 to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/arm64 uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/arm64 to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/arm64 uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/armel to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/armel uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/armel to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/armel uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/armel to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/armel uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/armel to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/armel uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/armhf to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/armhf uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/armhf to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/armhf uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/armhf to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/armhf uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/armhf to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/armhf uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/i386 to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/i386 uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/i386 to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/i386 uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/i386 to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/i386 uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/i386 to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/i386 uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/mips64el to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/mips64el uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/mips64el to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/mips64el uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/mips64el to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/mips64el uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/mips64el to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/mips64el uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/mipsel to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b7/mipsel uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/mipsel to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/mipsel uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/mipsel to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b7/mipsel uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/mipsel to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/mipsel uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/ppc64el to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/ppc64el uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/ppc64el to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/ppc64el uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/ppc64el to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/ppc64el uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/ppc64el to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/ppc64el uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/s390x to testing makes libghc-pandoc-citeproc-dev/0.17.0.1-1+b8/s390x uninstallable
    • migrating libghc-hsyaml-dev/0.2.1.1-1/s390x to testing makes libghc-pandoc-dev/2.9.2.1-3+b2/s390x uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/s390x to testing makes libghc-pandoc-citeproc-prof/0.17.0.1-1+b8/s390x uninstallable
    • migrating libghc-hsyaml-prof/0.2.1.1-1/s390x to testing makes libghc-pandoc-prof/2.9.2.1-3+b2/s390x uninstallable
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/amd64
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/arm64
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/armel
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/armhf
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/i386
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/mips64el
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/mipsel
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/ppc64el
    • Implicit dependency: haskell-hsyaml haskell-doctemplates/s390x
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/amd64
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/arm64
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/armel
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/armhf
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/i386
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/mips64el
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/mipsel
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/ppc64el
    • Implicit dependency: haskell-hsyaml haskell-hsyaml-aeson/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hsyaml.html
    • 14 days old (needed 5 days)
• kitinerary (21.12.3-2 to 21.12.3-3)
  • Migration status for kitinerary (21.12.3-2 to 21.12.3-3): Will attempt migration (Any information below is purely informational)
    • Depends: kitinerary openssl
  • Additional info:
    • Updating kitinerary will fix bugs in testing: #1011009
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitinerary.html
    • 14 days old (needed 5 days)
• nodejs (16.14.2+dfsg1-1 to 16.15.0+dfsg-1)
  • Migration status for nodejs (16.14.2+dfsg1-1 to 16.15.0+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mipsel
    • Depends: nodejs openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    • autopkgtest for nodejs/16.15.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• php-symfony-mercure (0.5.3-2 to 0.6.1-2)
  • Migration status for php-symfony-mercure (0.5.3-2 to 0.6.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: php-symfony-mercure symfony (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-symfony-mercure.html
    • autopkgtest for php-symfony-mercure/0.6.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• ploop (- to 1.15-10)
  • Migration status for ploop (- to 1.15-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ploop would introduce bugs in testing: #977279
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mipsel
    • 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/p/ploop.html
    • 14 days old (needed 5 days)
• rust-alloc-stdlib (- to 0.2.1-1)
  • Migration status for rust-alloc-stdlib (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-alloc-stdlib/0.2.1-1: amd64: Pass, arm64: Regression ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-alloc-stdlib.html
    • 14 days old (needed 5 days)
• rust-binascii (- to 0.1.4-1)
  • Migration status for rust-binascii (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-binascii/0.1.4-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-binascii.html
    • 14 days old (needed 5 days)
• rust-bkt (- to 0.5.4-1)
  • Migration status for rust-bkt (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-bkt/0.5.4-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
    • Built-Using: rust-bkt rustc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bkt.html
    • 14 days old (needed 5 days)
• symfony (5.4.6+dfsg-1 to 5.4.9+dfsg-1)
  • Migration status for symfony (5.4.6+dfsg-1 to 5.4.9+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/symfony.html
    • autopkgtest for php-symfony-polyfill/1.25.0-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for symfony/5.4.9+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
  • Additional info:
    • Updating symfony will fix bugs in testing: #1011737
    • 14 days old (needed 5 days)
• anosql (- to 1.0.1-3)
  • Migration status for anosql (- to 1.0.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): anosql python-testing.postgresql (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anosql.html
    • autopkgtest for anosql/1.0.1-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 15 days old (needed 5 days)
• eggdrop (- to 1.8.4+repack1-0.1)
  • Migration status for eggdrop (- to 1.8.4+repack1-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: eggdrop openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eggdrop.html
    • 15 days old (needed 5 days)
• gcc-9 (- to 9.5.0-1)
  • Migration status for gcc-9 (- to 9.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9 would introduce bugs in testing: #994108
    • missing build on mips64el
    • missing build on mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9.html
    • autopkgtest for gcc-9/9.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Ignored failure
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• guestfs-tools (1.48.1-1 to 1.48.2-1)
  • Migration status for guestfs-tools (1.48.1-1 to 1.48.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • missing build on ppc64el
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guestfs-tools.html
    • 15 days old (needed 5 days)
• herbstluftwm (0.9.3-2 to 0.9.4-5)
  • Migration status for herbstluftwm (0.9.3-2 to 0.9.4-5): 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
    • missing build on mipsel
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Updating herbstluftwm will fix bugs in testing: #1011092
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/herbstluftwm.html
    • 15 days old (needed 5 days)
• kdevelop-python (- to 22.04.1-1)
  • Migration status for kdevelop-python (- to 22.04.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kdevelop-python would introduce bugs in testing: #1008694
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdevelop-python.html
    • 15 days old (needed 5 days)
• libmojolicious-perl (9.24+dfsg-1 to 9.26+dfsg-1)
  • Migration status for libmojolicious-perl (9.24+dfsg-1 to 9.26+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libmojolicious-perl/9.26+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libmojolicious-plugin-authentication-perl/1.37-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmojolicious-perl.html
    • 15 days old (needed 5 days)
• nuitka (- to 0.8.2+ds-1)
  • Migration status for nuitka (- to 0.8.2+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nuitka would introduce bugs in testing: #1006051
    • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nuitka.html
    • 15 days old (needed 5 days)
• orthanc-dicomweb (1.7+dfsg-2 to 1.7+dfsg-5)
  • Migration status for orthanc-dicomweb (1.7+dfsg-2 to 1.7+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-dicomweb dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-dicomweb orthanc
  • Additional info:
    • Updating orthanc-dicomweb will fix bugs in testing: #1011886
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-dicomweb.html
    • 15 days old (needed 5 days)
• redis (5:6.0.16-2 to 5:6.0.16-4)
  • Migration status for redis (5:6.0.16-2 to 5:6.0.16-4): Will attempt migration (Any information below is purely informational)
    • Depends: redis openssl
  • Additional info:
    • Updating redis will fix bugs in testing: #1011187
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redis.html
    • autopkgtest for redis/5:6.0.16-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• ruby-omniauth-ultraauth (- to 0.0.2-2)
  • Migration status for ruby-omniauth-ultraauth (- to 0.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-omniauth-ultraauth ruby-omniauth-openid-connect (not considered)
    • Depends: ruby-omniauth-ultraauth ruby-omniauth-openid-connect (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-ultraauth.html
    • autopkgtest for ruby-omniauth-ultraauth/0.0.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 15 days old (needed 5 days)
• beancounter (- to 0.8.11.1)
  • Migration status for beancounter (- to 0.8.11.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: beancounter finance-yahooquote (not considered)
    • Depends: beancounter finance-yahooquote (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beancounter.html
    • 16 days old (needed 5 days)
• cfingerd (- to 1.4.3-6)
  • Migration status for cfingerd (- to 1.4.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cfingerd would introduce bugs in testing: #999167
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cfingerd.html
    • 16 days old (needed 5 days)
• libopkele (2.0.4+git20140305.9651b55-5 to 2.0.4+git20140305.9651b55-6)
  • Migration status for libopkele (2.0.4+git20140305.9651b55-5 to 2.0.4+git20140305.9651b55-6): Will attempt migration (Any information below is purely informational)
    • Depends: libopkele openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libopkele.html
    • 16 days old (needed 5 days)
• magics++ (4.11.0-1 to 4.12.1-1)
  • Migration status for magics++ (4.11.0-1 to 4.12.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: magics++ eckit
    • Depends: magics++ odc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magics++.html
    • 16 days old (needed 5 days)
• net-snmp (5.9.1+dfsg-1 to 5.9.1+dfsg-2)
  • Migration status for net-snmp (5.9.1+dfsg-1 to 5.9.1+dfsg-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 mipsel
    • 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/n/net-snmp.html
    • 16 days old (needed 5 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: #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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 16 days old (needed 5 days)
• qbittorrent (4.4.2-1 to 4.4.3.1-1)
  • Migration status for qbittorrent (4.4.2-1 to 4.4.3.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: qbittorrent openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qbittorrent.html
    • 16 days old (needed 5 days)
• qtmir (- to 0.7.0-2)
  • Migration status for qtmir (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • qtmir-tests/mips64el has unsatisfiable dependency
    • qtmir-tests/mipsel has unsatisfiable dependency
    • Build-Depends(-Arch): qtmir lomiri-app-launch
    • Build-Depends(-Arch): qtmir lomiri-url-dispatcher
    • Depends: qtmir lomiri-app-launch
    • Depends: qtmir lomiri-ui-toolkit
    • Depends: qtmir lomiri-url-dispatcher
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtmir.html
    • 16 days old (needed 5 days)
• yadifa (2.4.2-1 to 2.5.4-1)
  • Migration status for yadifa (2.4.2-1 to 2.5.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: yadifa openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yadifa.html
    • 16 days old (needed 5 days)
• chromium (101.0.4951.64-1 to 102.0.5005.61-1)
  • Migration status for chromium (101.0.4951.64-1 to 102.0.5005.61-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromium.html
    • 17 days old (needed 2 days)
• dpatch (- to 2.0.42)
  • Migration status for dpatch (- to 2.0.42): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dpatch would introduce bugs in testing: #1005988
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dpatch.html
    • autopkgtest for dpatch/2.0.42: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 17 days old (needed 5 days)
• efitools (1.9.2-1 to 1.9.2-2)
  • Migration status for efitools (1.9.2-1 to 1.9.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: efitools openssl
  • Additional info:
    • Updating efitools will fix bugs in testing: #1010996
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/efitools.html
    • 17 days old (needed 5 days)
• hitch (- to 1.7.1-2.1)
  • Migration status for hitch (- to 1.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: hitch openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hitch.html
    • autopkgtest for hitch/1.7.1-2.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• open-isns (0.100-3 to 0.101-0.2)
  • Migration status for open-isns (0.100-3 to 0.101-0.2): Will attempt migration (Any information below is purely informational)
    • Depends: open-isns openssl
  • Additional info:
    • Updating open-isns will fix bugs in testing: #994672
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-isns.html
    • autopkgtest for open-isns/0.101-0.2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• openqa (- to 4.6.1653336570.10bff0d-1)
  • Migration status for openqa (- to 4.6.1653336570.10bff0d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openqa-worker/arm64 has unsatisfiable dependency
    • Updating openqa would introduce bugs in testing: #1009711
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openqa.html
    • uninstallable on arch arm64, not running autopkgtest there
    • 17 days old (needed 5 days)
• pgpool2 (4.3.1-1 to 4.3.2-1)
  • Migration status for pgpool2 (4.3.1-1 to 4.3.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: pgpool2 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgpool2.html
    • autopkgtest for pgpool2/4.3.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• pmdk (1.11.1-4 to 1.12.0-1)
  • Migration status for pmdk (1.11.1-4 to 1.12.0-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
    • autopkgtest for pmdk/1.12.0-1: amd64: Pass, arm64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmdk.html
    • 17 days old (needed 5 days)
• proftpd-dfsg (1.3.7d+dfsg-1 to 1.3.7d+dfsg-2)
  • Migration status for proftpd-dfsg (1.3.7d+dfsg-1 to 1.3.7d+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: proftpd-dfsg openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proftpd-dfsg.html
    • 17 days old (needed 5 days)
• rust-gettext-rs (0.4.1-1 to 0.7.0-2)
  • Migration status for rust-gettext-rs (0.4.1-1 to 0.7.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-gettext-rs rust-gettext-sys (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gettext-rs.html
    • autopkgtest for rust-gettext-rs/0.7.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• rust-gettext-sys (0.19.8-2 to 0.21.3-2)
  • Migration status for rust-gettext-sys (0.19.8-2 to 0.21.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gettext-sys/0.21.3-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Implicit dependency: rust-gettext-sys rust-gettext-rs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gettext-sys.html
    • 17 days old (needed 5 days)
• dcm2niix (1.0.20211006-2 to 1.0.20211006-4)
  • Migration status for dcm2niix (1.0.20211006-2 to 1.0.20211006-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dcm2niix would introduce bugs in testing: #1012336
    • autopkgtest for dcm2niix/1.0.20211006-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcm2niix.html
    • 18 days old (needed 5 days)
• inkscape (1.1.2-3 to 1.2-1)
  • Migration status for inkscape (1.1.2-3 to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating inkscape would introduce bugs in testing: #1012496
    • missing build on arm64
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 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/i/inkscape.html
    • 18 days old (needed 5 days)
• jekyll (- to 3.9.0+dfsg-5)
  • Migration status for jekyll (- to 3.9.0+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jekyll would introduce bugs in testing: #998499
    • Build-Depends(-Arch): jekyll ruby-jekyll-sass-converter
    • Build-Depends(-Arch): jekyll ruby-pathutil
    • Depends: jekyll ruby-jekyll-sass-converter
    • Depends: jekyll ruby-pathutil
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jekyll.html
    • autopkgtest for jekyll/3.9.0+dfsg-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 18 days old (needed 2 days)
• megatools (1.10.3-1 to 1.11.0-1)
  • Migration status for megatools (1.10.3-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: megatools openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/megatools.html
    • 18 days old (needed 5 days)
• openiked (7.0-1 to 7.1-1)
  • Migration status for openiked (7.0-1 to 7.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: openiked openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openiked.html
    • 18 days old (needed 5 days)
• scikit-learn (1.0.1-1.1 to 1.1.1-1)
  • Migration status for scikit-learn (1.0.1-1.1 to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scikit-learn would introduce bugs in testing: #1008369
    • autopkgtest for imbalanced-learn/0.9.0-1: amd64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
    • autopkgtest for scikit-learn/1.1.1-1: amd64: Pass, i386: Not a regression
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 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:
    • Updating scikit-learn will fix bugs in testing: #1009784
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scikit-learn.html
    • 18 days old (needed 5 days)
• wine-development (- to 6.23~repack-4)
  • Migration status for wine-development (- to 6.23~repack-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wine-development would introduce bugs in testing: #988246
    • Build-Depends(-Arch): wine-development vkd3d
    • Depends: wine-development vkd3d
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
    • 18 days old (needed 5 days)
• yubico-piv-tool (2.2.0-1 to 2.2.0-1.1)
  • Migration status for yubico-piv-tool (2.2.0-1 to 2.2.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: yubico-piv-tool openssl
  • Additional info:
    • Updating yubico-piv-tool will fix bugs in testing: #1006241
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yubico-piv-tool.html
    • 18 days old (needed 5 days)
• libewf (20140807-2 to 20140807-2.1)
  • Migration status for libewf (20140807-2 to 20140807-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: libewf openssl
  • Additional info:
    • Updating libewf will fix bugs in testing: #1006393
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libewf.html
    • 19 days old (needed 5 days)
• mariadb-10.6 (1:10.6.7-3 to 1:10.6.8-1)
  • Migration status for mariadb-10.6 (1:10.6.7-3 to 1:10.6.8-1): Will attempt migration (Any information below is purely informational)
    • Depends: mariadb-10.6 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mariadb-10.6.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for mariadb-10.6/1:10.6.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 19 days old (needed 2 days)
• moonshot-trust-router (- to 3.5.4+1+nmu1)
  • Migration status for moonshot-trust-router (- to 3.5.4+1+nmu1): Will attempt migration (Any information below is purely informational)
    • Depends: moonshot-trust-router openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moonshot-trust-router.html
    • 19 days old (needed 5 days)
• qt6-base (6.2.4+dfsg-5 to 6.2.4+dfsg-8)
  • Migration status for qt6-base (6.2.4+dfsg-5 to 6.2.4+dfsg-8): Will attempt migration (Any information below is purely informational)
    • Depends: qt6-base openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt6-base.html
    • 19 days old (needed 5 days)
• transmission (- to 3.00-2.1)
  • Migration status for transmission (- to 3.00-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: transmission openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transmission.html
    • 19 days old (needed 10 days)
• votca (- to 2022-3)
  • Migration status for votca (- to 2022-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): votca gromacs (not considered)
    • Depends: votca gromacs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/votca.html
    • 19 days old (needed 5 days)
• xir (- to 1.4.1-5.1)
  • Migration status for xir (- to 1.4.1-5.1): Will attempt migration (Any information below is purely informational)
    • Depends: xir openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xir.html
    • 19 days old (needed 5 days)
• bobcat (5.10.01-1 to 5.11.00-1)
  • Migration status for bobcat (5.10.01-1 to 5.11.00-1): Will attempt migration (Any information below is purely informational)
    • Depends: bobcat openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bobcat.html
    • 20 days old (needed 5 days)
• cfengine3 (3.15.2-3 to 3.15.2-3.1)
  • Migration status for cfengine3 (3.15.2-3 to 3.15.2-3.1): Will attempt migration (Any information below is purely informational)
    • Depends: cfengine3 openssl
  • Additional info:
    • Updating cfengine3 will fix bugs in testing: #852674, #995642
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cfengine3.html
    • 20 days old (needed 5 days)
• gromacs (2021.4-2 to 2022.1-2)
  • Migration status for gromacs (2021.4-2 to 2022.1-2): 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
    • missing build on mipsel
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for gromacs/2022.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating gromacs will fix bugs in testing: #1009383
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gromacs.html
    • 20 days old (needed 5 days)
• metview (5.15.2-1 to 5.16.0-1)
  • Migration status for metview (5.15.2-1 to 5.16.0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): metview atlas-ecmwf
    • Depends: metview eckit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metview.html
    • 20 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-5)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-5): 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, #1011143
  • 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
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-5: i386: No test results
    • 20 days old (needed 5 days)
• rust-aliasable (- to 0.1.3-2)
  • Migration status for rust-aliasable (- to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-aliasable+aliasable-deref-trait-dev/amd64 has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/amd64 has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/arm64 has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/arm64 has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/armel has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/armel has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/armhf has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/armhf has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/i386 has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/i386 has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/mips64el has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/mips64el has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/mipsel has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/mipsel has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/ppc64el has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/ppc64el has unsatisfiable dependency
    • librust-aliasable+aliasable-deref-trait-dev/s390x has unsatisfiable dependency
    • librust-aliasable+stable-deref-trait-dev/s390x has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rust-aliasable.html
  • Additional info:
    • 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
    • 20 days old (needed 5 days)
• rust-average (- to 0.13.1-2)
  • Migration status for rust-average (- to 0.13.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-average-dev/amd64 has unsatisfiable dependency
    • librust-average-dev/arm64 has unsatisfiable dependency
    • librust-average-dev/armel has unsatisfiable dependency
    • librust-average-dev/armhf has unsatisfiable dependency
    • librust-average-dev/i386 has unsatisfiable dependency
    • librust-average-dev/mips64el has unsatisfiable dependency
    • librust-average-dev/mipsel has unsatisfiable dependency
    • librust-average-dev/ppc64el has unsatisfiable dependency
    • librust-average-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-average.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
    • 20 days old (needed 5 days)
• rust-configparser (- to 2.0.0-2)
  • Migration status for rust-configparser (- to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-configparser/2.0.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-configparser.html
    • 20 days old (needed 5 days)
• rust-copypasta (- to 0.7.1-2)
  • Migration status for rust-copypasta (- to 0.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-copypasta-dev/amd64 has unsatisfiable dependency
    • librust-copypasta-dev/arm64 has unsatisfiable dependency
    • librust-copypasta-dev/armel has unsatisfiable dependency
    • librust-copypasta-dev/armhf has unsatisfiable dependency
    • librust-copypasta-dev/i386 has unsatisfiable dependency
    • librust-copypasta-dev/mips64el has unsatisfiable dependency
    • librust-copypasta-dev/mipsel has unsatisfiable dependency
    • librust-copypasta-dev/ppc64el has unsatisfiable dependency
    • librust-copypasta-dev/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): rust-copypasta rust-x11-clipboard
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-copypasta.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
    • 20 days old (needed 5 days)
• rust-cxxbridge-macro (- to 1.0.62-2)
  • Migration status for rust-cxxbridge-macro (- to 1.0.62-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cxxbridge-macro-dev/amd64 has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/arm64 has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/armel has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/armhf has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/i386 has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/mips64el has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/mipsel has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/ppc64el has unsatisfiable dependency
    • librust-cxxbridge-macro-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cxxbridge-macro.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
    • 20 days old (needed 5 days)
• rust-dns-lookup (- to 1.0.8-2)
  • Migration status for rust-dns-lookup (- to 1.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-dns-lookup+clippy-dev/amd64 has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/arm64 has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/armel has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/armhf has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/i386 has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/mips64el has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/mipsel has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/ppc64el has unsatisfiable dependency
    • librust-dns-lookup+clippy-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-dns-lookup.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
    • 20 days old (needed 5 days)
• rust-fasteval (- to 0.2.4-2)
  • Migration status for rust-fasteval (- to 0.2.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-fasteval would introduce bugs in testing: #1011628
    • missing build on amd64
    • missing build on arm64
    • missing build on ppc64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fasteval.html
    • 20 days old (needed 5 days)
• rust-gdk4-wayland (- to 0.3.1-2)
  • Migration status for rust-gdk4-wayland (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gdk4-wayland-dev/amd64 has unsatisfiable dependency
    • librust-gdk4-wayland-dev/arm64 has unsatisfiable dependency
    • librust-gdk4-wayland-dev/armel has unsatisfiable dependency
    • librust-gdk4-wayland-dev/armhf has unsatisfiable dependency
    • librust-gdk4-wayland-dev/i386 has unsatisfiable dependency
    • librust-gdk4-wayland-dev/mips64el has unsatisfiable dependency
    • librust-gdk4-wayland-dev/mipsel has unsatisfiable dependency
    • librust-gdk4-wayland-dev/ppc64el has unsatisfiable dependency
    • librust-gdk4-wayland-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gdk4-wayland.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
    • 20 days old (needed 5 days)
• rust-gdk4-x11 (- to 0.3.1-2)
  • Migration status for rust-gdk4-x11 (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gdk4-x11-dev/amd64 has unsatisfiable dependency
    • librust-gdk4-x11-dev/arm64 has unsatisfiable dependency
    • librust-gdk4-x11-dev/armel has unsatisfiable dependency
    • librust-gdk4-x11-dev/armhf has unsatisfiable dependency
    • librust-gdk4-x11-dev/i386 has unsatisfiable dependency
    • librust-gdk4-x11-dev/mips64el has unsatisfiable dependency
    • librust-gdk4-x11-dev/mipsel has unsatisfiable dependency
    • librust-gdk4-x11-dev/ppc64el has unsatisfiable dependency
    • librust-gdk4-x11-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gdk4-x11.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
    • 20 days old (needed 5 days)
• rust-gpgme (- to 0.10.0-2)
  • Migration status for rust-gpgme (- to 0.10.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gpgme/0.10.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gpgme.html
    • 20 days old (needed 5 days)
• rust-hdrhistogram (- to 7.5.0-1)
  • Migration status for rust-hdrhistogram (- to 7.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-hdrhistogram/7.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hdrhistogram.html
    • 20 days old (needed 5 days)
• rust-is-executable (- to 1.0.1-2)
  • Migration status for rust-is-executable (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-is-executable/1.0.1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-is-executable.html
    • 20 days old (needed 5 days)
• rust-link-cplusplus (- to 1.0.6-2)
  • Migration status for rust-link-cplusplus (- to 1.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-link-cplusplus/1.0.6-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-link-cplusplus.html
    • 20 days old (needed 5 days)
• rust-notify (- to 4.0.17-2)
  • Migration status for rust-notify (- to 4.0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-notify/4.0.17-2: amd64: Regression ♻ , arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-notify.html
    • 20 days old (needed 5 days)
• rust-prometheus (- to 0.13.0-2)
  • Migration status for rust-prometheus (- to 0.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-prometheus+procfs-dev/amd64 has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/amd64 has unsatisfiable dependency
    • librust-prometheus+procfs-dev/arm64 has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/arm64 has unsatisfiable dependency
    • librust-prometheus+procfs-dev/armhf has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/armhf has unsatisfiable dependency
    • librust-prometheus+procfs-dev/i386 has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/i386 has unsatisfiable dependency
    • librust-prometheus+procfs-dev/mips64el has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/mips64el has unsatisfiable dependency
    • librust-prometheus+procfs-dev/ppc64el has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/ppc64el has unsatisfiable dependency
    • librust-prometheus+procfs-dev/s390x has unsatisfiable dependency
    • librust-prometheus+reqwest-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-prometheus.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
    • 20 days old (needed 5 days)
• rust-pyo3-build-config (- to 0.16.4-2)
  • Migration status for rust-pyo3-build-config (- to 0.16.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-pyo3-build-config+python3-dll-a-dev/amd64 has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/arm64 has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/armel has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/armhf has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/i386 has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/mips64el has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/mipsel has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/ppc64el has unsatisfiable dependency
    • librust-pyo3-build-config+python3-dll-a-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-pyo3-build-config.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
    • 20 days old (needed 5 days)
• rust-simplelog (- to 0.11.2-1)
  • Migration status for rust-simplelog (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-simplelog/0.11.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-simplelog.html
    • 20 days old (needed 5 days)
• rust-test-dir (- to 0.2.0-2)
  • Migration status for rust-test-dir (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-test-dir/0.2.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-test-dir.html
    • 20 days old (needed 5 days)
• rust-uucore (- to 0.0.12-2)
  • Migration status for rust-uucore (- to 0.0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-uucore-dev/amd64 has unsatisfiable dependency
    • librust-uucore-dev/arm64 has unsatisfiable dependency
    • librust-uucore-dev/armel has unsatisfiable dependency
    • librust-uucore-dev/armhf has unsatisfiable dependency
    • librust-uucore-dev/i386 has unsatisfiable dependency
    • librust-uucore-dev/mips64el has unsatisfiable dependency
    • librust-uucore-dev/mipsel has unsatisfiable dependency
    • librust-uucore-dev/ppc64el has unsatisfiable dependency
    • librust-uucore-dev/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): rust-uucore rust-os-display
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-uucore.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
    • 20 days old (needed 5 days)
• rust-vm-memory (- to 0.7.0-2)
  • Migration status for rust-vm-memory (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-vm-memory-dev/amd64 has unsatisfiable dependency
    • librust-vm-memory-dev/arm64 has unsatisfiable dependency
    • librust-vm-memory-dev/armel has unsatisfiable dependency
    • librust-vm-memory-dev/armhf has unsatisfiable dependency
    • librust-vm-memory-dev/i386 has unsatisfiable dependency
    • librust-vm-memory-dev/mips64el has unsatisfiable dependency
    • librust-vm-memory-dev/mipsel has unsatisfiable dependency
    • librust-vm-memory-dev/ppc64el has unsatisfiable dependency
    • librust-vm-memory-dev/s390x has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rust-vm-memory.html
  • Additional info:
    • 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
    • 20 days old (needed 5 days)
• rust-vmm-sys-util (- to 0.9.0-2)
  • Migration status for rust-vmm-sys-util (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-vmm-sys-util/0.9.0-2: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-vmm-sys-util.html
    • 20 days old (needed 5 days)
• atlas-ecmwf (0.29.0-1 to 0.29.0-2)
  • Migration status for atlas-ecmwf (0.29.0-1 to 0.29.0-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): atlas-ecmwf eckit
    • Depends: atlas-ecmwf eckit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atlas-ecmwf.html
    • 21 days old (needed 5 days)
• gcc-sh-elf (2 to 4)
  • Migration status for gcc-sh-elf (2 to 4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: gcc-sh-elf gdb (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-sh-elf.html
    • autopkgtest for gcc-sh-elf/4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 21 days old (needed 2 days)
• libengine-gost-openssl1.1 (- to 1.1.0.3-1.1)
  • Migration status for libengine-gost-openssl1.1 (- to 1.1.0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libengine-gost-openssl1.1 would introduce bugs in testing: #1012512
    • Depends: libengine-gost-openssl1.1 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl1.1.html
    • 21 days old (needed 5 days)
• libretls (3.5.0-2 to 3.5.2-2)
  • Migration status for libretls (3.5.0-2 to 3.5.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libretls openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretls.html
    • 21 days old (needed 5 days)
• litecoin (0.18.1-1.1 to 0.21.2-1)
  • Migration status for litecoin (0.18.1-1.1 to 0.21.2-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
    • Depends: litecoin openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litecoin.html
    • 21 days old (needed 5 days)
• pam-p11 (- to 0.3.1-1.1)
  • Migration status for pam-p11 (- to 0.3.1-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: pam-p11 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-p11.html
    • 21 days old (needed 10 days)
• python-clevercsv (0.7.1+ds-2 to 0.7.4+ds-1)
  • Migration status for python-clevercsv (0.7.1+ds-2 to 0.7.4+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-clevercsv would introduce bugs in testing: #1011421
    • autopkgtest for python-clevercsv/0.7.4+ds-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-clevercsv.html
    • 21 days old (needed 5 days)
• softhsm2 (2.6.1-2 to 2.6.1-2.1)
  • Migration status for softhsm2 (2.6.1-2 to 2.6.1-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: softhsm2 openssl
  • Additional info:
    • Updating softhsm2 will fix bugs in testing: #997511
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/softhsm2.html
    • 21 days old (needed 5 days)
• tpm2-pkcs11 (- to 1.7.0-1.1)
  • Migration status for tpm2-pkcs11 (- to 1.7.0-1.1): Will attempt migration (Any information below is purely informational)
    • Depends: tpm2-pkcs11 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-pkcs11.html
    • autopkgtest for tpm2-pkcs11/1.7.0-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 21 days old (needed 2 days)
• bfh-metapackages (- to 20211009-11)
  • Migration status for bfh-metapackages (- to 20211009-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bfh-metapackages knot-resolver (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bfh-metapackages.html
    • 22 days old (needed 5 days)
• cyrus-sasl2 (2.1.28+dfsg-4 to 2.1.28+dfsg-6)
  • Migration status for cyrus-sasl2 (2.1.28+dfsg-4 to 2.1.28+dfsg-6): Will attempt migration (Any information below is purely informational)
    • Depends: cyrus-sasl2 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyrus-sasl2.html
    • autopkgtest for cyrus-sasl2/2.1.28+dfsg-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • Required age is not allowed to drop below 2 days
    • 22 days old (needed 2 days)
• git-crypt (0.6.0-1 to 0.7.0-0.1)
  • Migration status for git-crypt (0.6.0-1 to 0.7.0-0.1): Will attempt migration (Any information below is purely informational)
    • Depends: git-crypt openssl
  • Additional info:
    • Updating git-crypt will fix bugs in testing: #996287
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-crypt.html
    • 22 days old (needed 2 days)
• metkit (1.9.0-1 to 1.9.1-1)
  • Migration status for metkit (1.9.0-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: metkit eckit
    • Depends: metkit odc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metkit.html
    • 22 days old (needed 5 days)
• odc (1.4.4-1 to 1.4.5-1)
  • Migration status for odc (1.4.4-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: odc eckit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odc.html
    • 22 days old (needed 5 days)
• progress-linux-metapackages (- to 20211008-11)
  • Migration status for progress-linux-metapackages (- to 20211008-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: progress-linux-metapackages knot-resolver (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
    • 22 days old (needed 5 days)
• bind9 (1:9.18.1-1 to 1:9.18.3-1)
  • Migration status for bind9 (1:9.18.1-1 to 1:9.18.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bind9 would introduce bugs in testing: #1012059
    • autopkgtest for bind9/1:9.18.3-1: amd64: Regression ♻ (reference ♻), arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • Depends: bind9 openssl
    • Implicit dependency: bind9 bind-dyndb-ldap/amd64
    • Implicit dependency: bind9 bind-dyndb-ldap/arm64
    • Implicit dependency: bind9 bind-dyndb-ldap/armel
    • Implicit dependency: bind9 bind-dyndb-ldap/armhf
    • Implicit dependency: bind9 bind-dyndb-ldap/i386
    • Implicit dependency: bind9 bind-dyndb-ldap/mips64el
    • Implicit dependency: bind9 bind-dyndb-ldap/mipsel
    • Implicit dependency: bind9 bind-dyndb-ldap/ppc64el
    • Implicit dependency: bind9 bind-dyndb-ldap/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bind9.html
    • 23 days old (needed 5 days)
• cl-plus-ssl (20220328.git8b91648-3 to 20220328.git8b91648-4)
  • Migration status for cl-plus-ssl (20220328.git8b91648-3 to 20220328.git8b91648-4): Will attempt migration (Any information below is purely informational)
    • Depends: cl-plus-ssl openssl
  • Additional info:
    • Updating cl-plus-ssl will fix bugs in testing: #1010999
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-plus-ssl.html
    • autopkgtest for cl-plus-ssl/20220328.git8b91648-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 23 days old (needed 5 days)
• eckit (1.19.0-1 to 1.20.0-1)
  • Migration status for eckit (1.19.0-1 to 1.20.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: eckit openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eckit.html
    • autopkgtest for eckit/1.20.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• golang-github-openshift-imagebuilder (1.2.1+ds1-3 to 1.2.3+ds1-1)
  • Migration status for golang-github-openshift-imagebuilder (1.2.1+ds1-3 to 1.2.3+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-containers-buildah/1.23.1+ds1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for golang-github-openshift-imagebuilder/1.2.3+ds1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libpod/3.4.7+ds1-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-openshift-imagebuilder.html
    • 23 days old (needed 5 days)
• haskell-hsopenssl (0.11.4.18-1 to 0.11.7.2-1)
  • Migration status for haskell-hsopenssl (0.11.4.18-1 to 0.11.7.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: haskell-hsopenssl openssl
    • Implicit dependency: haskell-hsopenssl haskell-haxr/amd64
    • Implicit dependency: haskell-hsopenssl haskell-haxr/arm64
    • Implicit dependency: haskell-hsopenssl haskell-haxr/armel
    • Implicit dependency: haskell-hsopenssl haskell-haxr/armhf
    • Implicit dependency: haskell-hsopenssl haskell-haxr/i386
    • Implicit dependency: haskell-hsopenssl haskell-haxr/mips64el
    • Implicit dependency: haskell-hsopenssl haskell-haxr/mipsel
    • Implicit dependency: haskell-hsopenssl haskell-haxr/ppc64el
    • Implicit dependency: haskell-hsopenssl haskell-haxr/s390x
    • Implicit dependency: haskell-hsopenssl haskell-hookup/amd64
    • Implicit dependency: haskell-hsopenssl haskell-hookup/arm64
    • Implicit dependency: haskell-hsopenssl haskell-hookup/armel
    • Implicit dependency: haskell-hsopenssl haskell-hookup/armhf
    • Implicit dependency: haskell-hsopenssl haskell-hookup/i386
    • Implicit dependency: haskell-hsopenssl haskell-hookup/mips64el
    • Implicit dependency: haskell-hsopenssl haskell-hookup/mipsel
    • Implicit dependency: haskell-hsopenssl haskell-hookup/ppc64el
    • Implicit dependency: haskell-hsopenssl haskell-hookup/s390x
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/amd64
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/arm64
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/armel
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/armhf
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/i386
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/mips64el
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/mipsel
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/ppc64el
    • Implicit dependency: haskell-hsopenssl haskell-hsopenssl-x509-system/s390x
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/amd64
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/arm64
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/armel
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/armhf
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/i386
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/mips64el
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/mipsel
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/ppc64el
    • Implicit dependency: haskell-hsopenssl haskell-http-streams/s390x
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/amd64
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/arm64
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/armel
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/armhf
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/i386
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/mips64el
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/mipsel
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/ppc64el
    • Implicit dependency: haskell-hsopenssl haskell-openssl-streams/s390x
  • Additional info:
    • Updating haskell-hsopenssl will fix bugs in testing: #996424
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hsopenssl.html
    • 23 days old (needed 5 days)
• nextcloud-desktop (3.4.2-1 to 3.5.1-1)
  • Migration status for nextcloud-desktop (3.4.2-1 to 3.5.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: nextcloud-desktop openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextcloud-desktop.html
    • 23 days old (needed 5 days)
• openjdk-19 (- to 19~23ea-1)
  • Migration status for openjdk-19 (- to 19~23ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/openjdk-19.html
  • Additional info:
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-19/19~23ea-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 23 days old (needed 5 days)
• precious (0.1.3-5 to 0.1.3-6)
  • Migration status for precious (0.1.3-5 to 0.1.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: precious rustc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/precious.html
    • 23 days old (needed 5 days)
• python-cryptography (3.4.8-1 to 3.4.8-2)
  • Migration status for python-cryptography (3.4.8-1 to 3.4.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for barbican/1:14.0.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for python-cryptography/3.4.8-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Depends: python-cryptography openssl
  • Additional info:
    • Updating python-cryptography will fix bugs in testing: #1006008
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cryptography.html
    • 23 days old (needed 5 days)
• cappuccino (- to 0.5.1-10)
  • Migration status for cappuccino (- to 0.5.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cappuccino would introduce bugs in testing: #999145
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cappuccino.html
    • 24 days old (needed 5 days)
• libtree (3.1.0-1 to 3.1.1-1)
  • Migration status for libtree (3.1.0-1 to 3.1.1-1): 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 mipsel
    • missing build on s390x
    • arch:arm64 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/libt/libtree.html
    • 24 days old (needed 5 days)
• mu-editor (- to 1.0.3+dfsg-4)
  • Migration status for mu-editor (- to 1.0.3+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mu-editor python-uflash (not considered)
    • Depends: mu-editor python-uflash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mu-editor.html
    • autopkgtest for mu-editor/1.0.3+dfsg-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 24 days old (needed 2 days)
• mysql-8.0 (- to 8.0.29-1)
  • Migration status for mysql-8.0 (- to 8.0.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-8.0 would introduce bugs in testing: #1005720, #1010052, #853008
    • autopkgtest for mysql-8.0/8.0.29-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
    • missing build on armhf
    • Not touching package due to block request by pochu (please contact debian-release if update is needed)
    • arch:armhf not built yet, autopkgtest delayed there
    • Depends: mysql-8.0 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-8.0.html
    • 24 days old (needed 5 days)
• tiledb-r (0.12.0-1 to 0.13.0-1)
  • Migration status for tiledb-r (0.12.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: tiledb-r tiledb
  • Additional info:
    • Updating tiledb-r will fix bugs in testing: #1011012
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledb-r.html
    • 24 days old (needed 5 days)
• uxplay (- to 1.52-2)
  • Migration status for uxplay (- to 1.52-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): uxplay openssl
    • Depends: uxplay openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uxplay.html
    • 24 days old (needed 5 days)
• hubicfuse (3.0.1-4 to 3.0.1-5)
  • Migration status for hubicfuse (3.0.1-4 to 3.0.1-5): Will attempt migration (Any information below is purely informational)
    • Depends: hubicfuse openssl
  • Additional info:
    • Updating hubicfuse will fix bugs in testing: #1011045
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hubicfuse.html
    • 25 days old (needed 5 days)
• openpace (1.1.2+ds-1 to 1.1.2+ds+git20220117+453c3d6b03a0-1)
  • Migration status for openpace (1.1.2+ds-1 to 1.1.2+ds+git20220117+453c3d6b03a0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openpace would introduce bugs in testing: #1011393
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • Depends: openpace openssl
  • Additional info:
    • Updating openpace will fix bugs in testing: #1006513
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openpace.html
    • 25 days old (needed 5 days)
• orthanc-neuro (- to 1.0-1)
  • Migration status for orthanc-neuro (- to 1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-neuro dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-neuro orthanc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-neuro.html
    • 25 days old (needed 10 days)
• psycopg3 (- to 3.0.1-1)
  • Migration status for psycopg3 (- 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 tomasz.rybak@post.pl, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psycopg3.html
    • 25 days old (needed 5 days)
• r-cran-vegan (2.5-7+dfsg-2 to 2.6-2+dfsg-1)
  • Migration status for r-cran-vegan (2.5-7+dfsg-2 to 2.6-2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-vegan/2.6-2+dfsg-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vegan.html
    • 25 days old (needed 5 days)
• sogo (5.5.1-1 to 5.6.0-1)
  • Migration status for sogo (5.5.1-1 to 5.6.0-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
    • Depends: sogo openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sogo.html
    • 25 days old (needed 5 days)
• ecflow (5.8.3-2 to 5.8.4-1)
  • Migration status for ecflow (5.8.3-2 to 5.8.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: ecflow openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecflow.html
    • autopkgtest for ecflow/5.8.4-1: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Pass, ppc64el: Pass, s390x: Pass
    • 26 days old (needed 5 days)
• fastnetmon (1.2.0+git20220506-1 to 1.2.1-1)
  • Migration status for fastnetmon (1.2.0+git20220506-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: fastnetmon openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastnetmon.html
    • 26 days old (needed 5 days)
• foxeye (- to 0.12.1-4)
  • Migration status for foxeye (- to 0.12.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: foxeye openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxeye.html
    • 26 days old (needed 5 days)
• fusesmb (- to 0.8.7-3)
  • Migration status for fusesmb (- to 0.8.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fusesmb would introduce bugs in testing: #534756, #981523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fusesmb.html
    • 26 days old (needed 5 days)
• golang-github-mendersoftware-openssl (1.1.0-2 to 1.1.0-3)
  • Migration status for golang-github-mendersoftware-openssl (1.1.0-2 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): golang-github-mendersoftware-openssl openssl
    • Depends: golang-github-mendersoftware-openssl openssl
  • Additional info:
    • Updating golang-github-mendersoftware-openssl will fix bugs in testing: #996422
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-mendersoftware-openssl.html
    • autopkgtest for golang-github-mendersoftware-openssl/1.1.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 26 days old (needed 2 days)
• gsad (- to 21.4.4-1)
  • Migration status for gsad (- to 21.4.4-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
    • 26 days old (needed 5 days)
• gvm (- to 21.4.4)
  • Migration status for gvm (- to 21.4.4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gvm gvmd (not considered)
    • Invalidated by dependency
    • Depends: gvm gsad
    • Depends: gvm openvas-scanner
    • Depends: gvm ospd-openvas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm.html
    • 26 days old (needed 5 days)
• nordugrid-arc (6.15.1-1 to 6.15.1-2)
  • Migration status for nordugrid-arc (6.15.1-1 to 6.15.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: nordugrid-arc openssl
  • Additional info:
    • Updating nordugrid-arc will fix bugs in testing: #1006516
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nordugrid-arc.html
    • 26 days old (needed 5 days)
• nsd (4.4.0-1 to 4.5.0-1)
  • Migration status for nsd (4.4.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: nsd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nsd.html
    • autopkgtest for nsd/4.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 26 days old (needed 2 days)
• opencl-clang-12 (- to 12.0.0-4)
  • Migration status for opencl-clang-12 (- to 12.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
    • Build-Depends(-Arch): opencl-clang-12 spirv-llvm-translator-12
    • Depends: opencl-clang-12 spirv-llvm-translator-12
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencl-clang-12.html
    • 26 days old (needed 5 days)
• pappl (1.1.0-3 to 1.2.0-1)
  • Migration status for pappl (1.1.0-3 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pappl would introduce bugs in testing: #1011990
    • autopkgtest for pappl/1.2.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pappl.html
    • 26 days old (needed 5 days)
• paramiko (2.8.1-1 to 2.10.4-1)
  • Migration status for paramiko (2.8.1-1 to 2.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating paramiko would introduce bugs in testing: #1010214
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paramiko.html
    • autopkgtest for paramiko/2.10.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 26 days old (needed 2 days)
• sendmail (8.16.1-3 to 8.17.1-2)
  • Migration status for sendmail (8.16.1-3 to 8.17.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: sendmail openssl
  • Additional info:
    • Updating sendmail will fix bugs in testing: #1006574
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sendmail.html
    • 26 days old (needed 5 days)
• spirv-llvm-translator-12 (- to 12.0.0-4)
  • Migration status for spirv-llvm-translator-12 (- to 12.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by elbrus
    • Trying to remove package, not update it
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-12.html
    • 26 days old (needed 5 days)
• srain (1.3.2-1 to 1.4.0-1)
  • Migration status for srain (1.3.2-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: srain openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/srain.html
    • 26 days old (needed 5 days)
• telegram-desktop (3.7.3+ds-1 to 3.7.3+ds-2)
  • Migration status for telegram-desktop (3.7.3+ds-1 to 3.7.3+ds-2): Will attempt migration (Any information below is purely informational)
    • Depends: telegram-desktop openssl
  • Additional info:
    • Updating telegram-desktop will fix bugs in testing: #1011019
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-desktop.html
    • 26 days old (needed 5 days)
• thrift (0.16.0-4 to 0.16.0-5)
  • Migration status for thrift (0.16.0-4 to 0.16.0-5): Will attempt migration (Any information below is purely informational)
    • Depends: thrift openssl
  • Additional info:
    • Updating thrift will fix bugs in testing: #1011011
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thrift.html
    • 26 days old (needed 5 days)
• tpm2-openssl (- to 1.1.0-2)
  • Migration status for tpm2-openssl (- to 1.1.0-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): tpm2-openssl openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-openssl.html
    • 26 days old (needed 5 days)
• aiohttp-wsgi (- to 0.10.0-1)
  • Migration status for aiohttp-wsgi (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiohttp-wsgi would introduce bugs in testing: #1002334
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiohttp-wsgi.html
    • autopkgtest for aiohttp-wsgi/0.10.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 27 days old (needed 10 days)
• libnet-ssleay-perl (1.92-1 to 1.92-2)
  • Migration status for libnet-ssleay-perl (1.92-1 to 1.92-2): Will attempt migration (Any information below is purely informational)
    • Depends: libnet-ssleay-perl openssl
    • Depends: libnet-ssleay-perl perl-openssl-defaults/amd64
    • Depends: libnet-ssleay-perl perl-openssl-defaults/arm64
    • Depends: libnet-ssleay-perl perl-openssl-defaults/armel
    • Depends: libnet-ssleay-perl perl-openssl-defaults/armhf
    • Depends: libnet-ssleay-perl perl-openssl-defaults/i386
    • Depends: libnet-ssleay-perl perl-openssl-defaults/mips64el
    • Depends: libnet-ssleay-perl perl-openssl-defaults/mipsel
    • Depends: libnet-ssleay-perl perl-openssl-defaults/ppc64el
    • Depends: libnet-ssleay-perl perl-openssl-defaults/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-ssleay-perl.html
    • autopkgtest for libnet-ssleay-perl/1.92-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• node-base16 (- to 1.0.0+~cs1.0.2-1)
  • Migration status for node-base16 (- to 1.0.0+~cs1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-base16/1.0.0+~cs1.0.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by lolando, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-base16.html
    • 27 days old (needed 5 days)
• node-v8-compile-cache (- to 2.3.0-1)
  • Migration status for node-v8-compile-cache (- 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 kapouer@melix.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-v8-compile-cache.html
    • autopkgtest for node-v8-compile-cache/2.3.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• node-yarn-tool-resolve-package (- to 1.0.46-2)
  • Migration status for node-yarn-tool-resolve-package (- to 1.0.46-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lolando, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-yarn-tool-resolve-package node-ws-iconv
    • Depends: node-yarn-tool-resolve-package node-ws-iconv
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-yarn-tool-resolve-package.html
    • autopkgtest for node-yarn-tool-resolve-package/1.0.46-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 27 days old (needed 5 days)
• nrepl-clojure (0.6.0-2 to 0.9.0-1)
  • Migration status for nrepl-clojure (0.6.0-2 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nrepl-clojure would introduce bugs in testing: #1011821, #1011970
    • autopkgtest for cljx-clojure/0.6.0-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for nrepl-clojure/0.9.0-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nrepl-clojure.html
    • 27 days old (needed 5 days)
• r-bioc-megadepth (- to 1.6.0+ds-1)
  • Migration status for r-bioc-megadepth (- to 1.6.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-megadepth/1.6.0+ds-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-megadepth.html
    • 27 days old (needed 5 days)
• ruby-oj (3.13.9-1 to 3.13.9-2)
  • Migration status for ruby-oj (3.13.9-1 to 3.13.9-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 ruby-oj/3.13.9-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-oj.html
    • 27 days old (needed 5 days)
• serf (1.3.9-10 to 1.3.9-11)
  • Migration status for serf (1.3.9-10 to 1.3.9-11): Will attempt migration (Any information below is purely informational)
    • Depends: serf openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/serf.html
    • autopkgtest for serf/1.3.9-11: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• show-in-file-manager (- to 1.1.4-1)
  • Migration status for show-in-file-manager (- to 1.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/show-in-file-manager.html
    • 27 days old (needed 5 days)
• spice (0.15.0-3 to 0.15.0-4)
  • Migration status for spice (0.15.0-3 to 0.15.0-4): Will attempt migration (Any information below is purely informational)
    • Depends: spice openssl
  • Additional info:
    • Updating spice will fix bugs in testing: #1010990
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spice.html
    • 27 days old (needed 5 days)
• swupdate (2021.11-1 to 2022.05-1)
  • Migration status for swupdate (2021.11-1 to 2022.05-1): Will attempt migration (Any information below is purely informational)
    • Depends: swupdate openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swupdate.html
    • autopkgtest for swupdate/2022.05-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • Required age is not allowed to drop below 2 days
    • 27 days old (needed 2 days)
• core-async-clojure (1.3.610-4 to 1.3.610-5)
  • Migration status for core-async-clojure (1.3.610-4 to 1.3.610-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating core-async-clojure would introduce bugs in testing: #1011791
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/core-async-clojure.html
    • 28 days old (needed 5 days)
• cyclonedds (0.9.0-3 to 0.9.1-1)
  • Migration status for cyclonedds (0.9.0-3 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: cyclonedds openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyclonedds.html
    • autopkgtest for cyclonedds/0.9.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• distrobox (- to 1.2.15-2)
  • Migration status for distrobox (- to 1.2.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by leitao, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/distrobox.html
    • 28 days old (needed 10 days)
• elpi (1.14.3-1 to 1.15.2-1)
  • Migration status for elpi (1.14.3-1 to 1.15.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: elpi menhir (not considered)
    • Invalidated by dependency
    • Implicit dependency: elpi coq-elpi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elpi.html
    • 28 days old (needed 5 days)
• haproxy (2.4.16-1 to 2.4.17-1)
  • Migration status for haproxy (2.4.16-1 to 2.4.17-1): Will attempt migration (Any information below is purely informational)
    • Depends: haproxy openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haproxy.html
    • autopkgtest for haproxy/2.4.17-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• menhir (20210929-1 to 20220210+ds-2)
  • Migration status for menhir (20210929-1 to 20220210+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: menhir why3 (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: menhir js-of-ocaml/amd64
    • Implicit dependency: menhir js-of-ocaml/arm64
    • Implicit dependency: menhir js-of-ocaml/armel
    • Implicit dependency: menhir js-of-ocaml/armhf
    • Implicit dependency: menhir js-of-ocaml/i386
    • Implicit dependency: menhir js-of-ocaml/mips64el
    • Implicit dependency: menhir js-of-ocaml/mipsel
    • Implicit dependency: menhir js-of-ocaml/ppc64el
    • Implicit dependency: menhir js-of-ocaml/s390x
    • Implicit dependency: menhir morbig/amd64
    • Implicit dependency: menhir morbig/arm64
    • Implicit dependency: menhir morbig/armel
    • Implicit dependency: menhir morbig/armhf
    • Implicit dependency: menhir morbig/i386
    • Implicit dependency: menhir morbig/mips64el
    • Implicit dependency: menhir morbig/mipsel
    • Implicit dependency: menhir morbig/ppc64el
    • Implicit dependency: menhir morbig/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/menhir.html
    • autopkgtest for menhir/20220210+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• nsca-ng (1.6-4 to 1.6-5)
  • Migration status for nsca-ng (1.6-4 to 1.6-5): Will attempt migration (Any information below is purely informational)
    • Depends: nsca-ng openssl
  • Additional info:
    • Updating nsca-ng will fix bugs in testing: #1010959
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nsca-ng.html
    • 28 days old (needed 5 days)
• prometheus-frr-exporter (- to 1.1.1-2)
  • Migration status for prometheus-frr-exporter (- to 1.1.1-2): 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.1.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• rust-fd-find (8.3.1-1 to 8.3.2-1)
  • Migration status for rust-fd-find (8.3.1-1 to 8.3.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-fd-find rustc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fd-find.html
    • 28 days old (needed 5 days)
• rust-pyo3-ffi (- to 0.16.4-1)
  • Migration status for rust-pyo3-ffi (- to 0.16.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-pyo3-ffi rust-pyo3-build-config (not considered)
    • Depends: rust-pyo3-ffi rust-pyo3-build-config (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pyo3-ffi.html
    • autopkgtest for rust-pyo3-ffi/0.16.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• trapperkeeper-clojure (3.1.0-2 to 3.1.0-3)
  • Migration status for trapperkeeper-clojure (3.1.0-2 to 3.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trapperkeeper-clojure would introduce bugs in testing: #1011967
    • autopkgtest for trapperkeeper-clojure/3.1.0-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trapperkeeper-clojure.html
    • 28 days old (needed 5 days)
• vecgeom (- to 1.2.0+dfsg-1)
  • Migration status for vecgeom (- to 1.2.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): 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
    • 28 days old (needed 5 days)
• aseba (1.6.99+dfsg-1 to 1.6.99+dfsg-4)
  • Migration status for aseba (1.6.99+dfsg-1 to 1.6.99+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • missing build on s390x
    • 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/a/aseba.html
    • 29 days old (needed 5 days)
• rust-cargo-outdated (- to 0.10.2-2)
  • Migration status for rust-cargo-outdated (- to 0.10.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-cargo-outdated rustc (not considered)
    • Invalidated by built-using
    • Depends: rust-cargo-outdated openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-outdated.html
    • 29 days old (needed 5 days)
• spades (3.15.4+dfsg-1 to 3.15.4+dfsg-2)
  • Migration status for spades (3.15.4+dfsg-1 to 3.15.4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spades would introduce bugs in testing: #1011968
    • autopkgtest for spades/3.15.4+dfsg-2: amd64: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spades.html
    • 29 days old (needed 5 days)
• tboot (1.10.2+dfsg.0-1 to 1.10.5-1)
  • Migration status for tboot (1.10.2+dfsg.0-1 to 1.10.5-1): Will attempt migration (Any information below is purely informational)
    • Depends: tboot openssl
  • Additional info:
    • Updating tboot will fix bugs in testing: #1006588
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tboot.html
    • 29 days old (needed 5 days)
• aeskulap (0.2.2-beta2+git20190406.ef77f01-3 to 0.2.2-beta2+git20190406.ef77f01-4)
  • Migration status for aeskulap (0.2.2-beta2+git20190406.ef77f01-3 to 0.2.2-beta2+git20190406.ef77f01-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aeskulap dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aeskulap.html
    • 30 days old (needed 5 days)
• amide (1.0.5-15 to 1.0.5-16)
  • Migration status for amide (1.0.5-15 to 1.0.5-16): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: amide dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amide.html
    • 30 days old (needed 5 days)
• cmtk (3.3.1p2+dfsg-1 to 3.3.1p2+dfsg-2)
  • Migration status for cmtk (3.3.1p2+dfsg-1 to 3.3.1p2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cmtk dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmtk.html
    • 30 days old (needed 5 days)
• curl (7.83.0-1 to 7.83.1-1)
  • Migration status for curl (7.83.0-1 to 7.83.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: curl openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curl.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • 30 days old (needed 5 days)
• dicomscope (3.6.0-23 to 3.6.0-24)
  • Migration status for dicomscope (3.6.0-23 to 3.6.0-24): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dicomscope dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dicomscope.html
    • 30 days old (needed 5 days)
• ipykernel (6.9.2-1 to 6.13.0-1)
  • Migration status for ipykernel (6.9.2-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ipykernel would introduce bugs in testing: #1011964
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipykernel.html
    • autopkgtest for ipykernel/6.13.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• mia (2.4.7-8 to 2.4.7-9)
  • Migration status for mia (2.4.7-8 to 2.4.7-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mia dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mia.html
    • 30 days old (needed 5 days)
• odil (0.12.2-1 to 0.12.2-2)
  • Migration status for odil (0.12.2-1 to 0.12.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: odil dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odil.html
    • autopkgtest for odil/0.12.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 30 days old (needed 5 days)
• odin (2.0.5-2 to 2.0.5-3)
  • Migration status for odin (2.0.5-2 to 2.0.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: odin dcmtk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odin.html
    • autopkgtest for odin/2.0.5-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• openimageio (- to 2.3.14.0+dfsg-3)
  • Migration status for openimageio (- to 2.3.14.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): openimageio openvdb (not considered)
    • Depends: openimageio openvdb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): openimageio opencolorio
    • Depends: openimageio dcmtk
    • Depends: openimageio opencolorio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openimageio.html
    • 30 days old (needed 5 days)
• orthanc-wsi (1.1-3 to 1.1-4)
  • Migration status for orthanc-wsi (1.1-3 to 1.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc-wsi dcmtk (not considered)
    • Invalidated by dependency
    • Built-Using: orthanc-wsi orthanc
    • Depends: orthanc-wsi openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-wsi.html
    • 30 days old (needed 5 days)
• python-aiortc (1.3.1-2 to 1.3.2-1)
  • Migration status for python-aiortc (1.3.1-2 to 1.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-aiortc/1.3.2-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by js
    • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiortc.html
    • 30 days old (needed 5 days)
• sofia-sip (1.12.11+20110422.1-2.2 to 1.12.11+20110422.1+1e14eea~dfsg-2)
  • Migration status for sofia-sip (1.12.11+20110422.1-2.2 to 1.12.11+20110422.1+1e14eea~dfsg-2): Will attempt migration (Any information below is purely informational)
    • Depends: sofia-sip openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sofia-sip.html
    • 30 days old (needed 5 days)
• libfido2 (1.10.0-1 to 1.11.0-1)
  • Migration status for libfido2 (1.10.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: libfido2 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfido2.html
    • 31 days old (needed 5 days)
• ntpsec (1.2.1+dfsg1-6 to 1.2.1+dfsg1-7)
  • Migration status for ntpsec (1.2.1+dfsg1-6 to 1.2.1+dfsg1-7): Will attempt migration (Any information below is purely informational)
    • Depends: ntpsec openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntpsec.html
    • 31 days old (needed 5 days)
• partman-hfs (- to 2)
  • Migration status for partman-hfs (- to 2): 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
    • 31 days old (needed 5 days)
• php-excimer (1.0.2-1 to 1.0.4-1)
  • Migration status for php-excimer (1.0.2-1 to 1.0.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-excimer.html
    • autopkgtest for php-excimer/1.0.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 31 days old (needed 2 days)
• qpid-proton (0.22.0-5.1 to 0.37.0-1)
  • Migration status for qpid-proton (0.22.0-5.1 to 0.37.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: qpid-proton openssl
  • Additional info:
    • Updating qpid-proton will fix bugs in testing: #1006562
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton.html
    • autopkgtest for qpid-proton/0.37.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 31 days old (needed 5 days)
• rustc (1.58.1+dfsg1-1 to 1.59.0+dfsg1-1)
  • Migration status for rustc (1.58.1+dfsg1-1 to 1.59.0+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rustc would introduce bugs in testing: #1011975
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rustc.html
    • 31 days old (needed 5 days)
• zimlib (7.2.0-2 to 7.2.1-1)
  • Migration status for zimlib (7.2.0-2 to 7.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-libzim/1.0.0+ds-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zimlib.html
    • 31 days old (needed 5 days)
• git (1:2.35.1-1 to 1:2.36.1-1)
  • Migration status for git (1:2.35.1-1 to 1:2.36.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/git.html
  • Additional info:
    • 32 days old (needed 10 days)
• llvm-toolchain-snapshot (- to 1:15~++20220509105605+460fc79a080b-1~exp1)
  • Migration status for llvm-toolchain-snapshot (- to 1:15~++20220509105605+460fc79a080b-1~exp1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for llvm-toolchain-snapshot/1:15~++20220509105605+460fc79a080b-1~exp1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not touching package due to block request by jcristau (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-snapshot.html
    • 32 days old (needed 5 days)
• git-annex (8.20211123-1 to 10.20220504-1)
  • Migration status for git-annex (8.20211123-1 to 10.20220504-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for git-annex/10.20220504-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-annex.html
    • 33 days old (needed 5 days)
• node-blacklist (- to 1.1.4+ds1-2)
  • Migration status for node-blacklist (- to 1.1.4+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-blacklist/1.1.4+ds1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-blacklist.html
    • 33 days old (needed 5 days)
• node-create-react-class (- to 15.7.0+dfsg-1)
  • Migration status for node-create-react-class (- to 15.7.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-create-react-class/15.7.0+dfsg-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-create-react-class.html
    • 33 days old (needed 5 days)
• node-open (- to 8.4.0-4)
  • Migration status for node-open (- to 8.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): node-open node-is-wsl (not considered)
    • Depends: node-open node-is-wsl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-open.html
    • autopkgtest for node-open/8.4.0-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 33 days old (needed 5 days)
• node-react-highlighter (- to 0.4.3+repack1-1)
  • Migration status for node-react-highlighter (- to 0.4.3+repack1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): node-react-highlighter node-create-react-class (not considered)
    • Depends: node-react-highlighter node-create-react-class (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): node-react-highlighter node-blacklist
    • Depends: node-react-highlighter node-blacklist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-react-highlighter.html
    • autopkgtest for node-react-highlighter/0.4.3+repack1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 33 days old (needed 2 days)
• node-ws-iconv (- to 0.0~git20220306210217.c039e94-2)
  • Migration status for node-ws-iconv (- to 0.0~git20220306210217.c039e94-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-ws-iconv/0.0~git20220306210217.c039e94-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-ws-iconv.html
    • 33 days old (needed 5 days)
• ruby-bootsnap (1.9.3-1 to 1.11.1-1)
  • Migration status for ruby-bootsnap (1.9.3-1 to 1.11.1-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
    • autopkgtest for ruby-bootsnap/1.11.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-bootsnap.html
    • 34 days old (needed 5 days)
• okasha (0.2.4-4 to 0.2.4-5)
  • Migration status for okasha (0.2.4-4 to 0.2.4-5): 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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 37 days old (needed 5 days)
• orthanc (1.10.1+dfsg-1 to 1.10.1+dfsg-2)
  • Migration status for orthanc (1.10.1+dfsg-1 to 1.10.1+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orthanc dcmtk (not considered)
    • Invalidated by dependency
    • Depends: orthanc openssl
  • Additional info:
    • Updating orthanc will fix bugs in testing: #1010554
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc.html
    • 37 days old (needed 5 days)
• zynaddsubfx (3.0.5-2 to 3.0.6-1)
  • Migration status for zynaddsubfx (3.0.5-2 to 3.0.6-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 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/z/zynaddsubfx.html
    • 37 days old (needed 5 days)
• gvmd (- to 21.4.5-1)
  • Migration status for gvmd (- to 21.4.5-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 ospd-openvas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvmd.html
    • autopkgtest for gvmd/21.4.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 38 days old (needed 2 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
    • 38 days old (needed 5 days)
• openjdk-11-jre-dcevm (11.0.12+7-1 to 11.0.15+1-1)
  • Migration status for openjdk-11-jre-dcevm (11.0.12+7-1 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 test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11-jre-dcevm.html
    • 38 days old (needed 5 days)
• openjfx (11.0.11+0-1 to 11.0.11+1-1)
  • Migration status for openjfx (11.0.11+0-1 to 11.0.11+1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armhf
    • arch:arm64 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/o/openjfx.html
    • 38 days old (needed 5 days)
• openvas-scanner (- to 21.4.4-1)
  • Migration status for openvas-scanner (- to 21.4.4-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
    • 38 days old (needed 5 days)
• ospd-openvas (- to 21.4.4-1)
  • Migration status for ospd-openvas (- to 21.4.4-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/21.4.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 38 days old (needed 2 days)
• python-gvm (- to 21.11.0-1)
  • Migration status for python-gvm (- to 21.11.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-gvm gvmd (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gvm.html
    • autopkgtest for python-gvm/21.11.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 38 days old (needed 5 days)
• flask-limiter (- to 1.0.1-3)
  • Migration status for flask-limiter (- to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-limiter would introduce bugs in testing: #982210
    • autopkgtest for flask-limiter/1.0.1-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-limiter.html
    • 39 days old (needed 5 days)
• flask-script (- to 2.0.6-3)
  • Migration status for flask-script (- to 2.0.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-script would introduce bugs in testing: #997472
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-script.html
    • 39 days old (needed 5 days)
• gcc-11-cross-ports (7 to 9)
  • Migration status for gcc-11-cross-ports (7 to 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 i386
    • missing build on ppc64el
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating gcc-11-cross-ports will fix bugs in testing: #1008869
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-ports.html
    • 39 days old (needed 5 days)
• gvm-libs (- to 21.4.4-1)
  • Migration status for gvm-libs (- to 21.4.4-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
    • 39 days old (needed 5 days)
• gvm-tools (- to 21.10.0-2)
  • Migration status for gvm-tools (- to 21.10.0-2): 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/21.10.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 39 days old (needed 5 days)
• openjdk-11 (11.0.14.1+1-1 to 11.0.15+10-1)
  • Migration status for openjdk-11 (11.0.14.1+1-1 to 11.0.15+10-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: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-11/blocked-on-ci-infra: amd64: Not a regression, arm64: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
    • 39 days old (needed 5 days)
• openjdk-18 (- to 18.0.1+10-1)
  • Migration status for openjdk-18 (- to 18.0.1+10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/openjdk-18.html
  • Additional info:
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for openjdk-18/18.0.1+10-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 39 days old (needed 5 days)
• why3 (1.4.1-2 to 1.5.0-1)
  • Migration status for why3 (1.4.1-2 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for frama-c/20211203-chromium-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for why3/1.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Depends: why3 menhir
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/why3.html
    • 39 days old (needed 5 days)
• dxvk (- to 1.10.1+ds1-1)
  • Migration status for dxvk (- to 1.10.1+ds1-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/1.10.1+ds1-1: amd64: Regression ♻ , armhf: Ignored failure, i386: Regression ♻ , ppc64el: Ignored failure, s390x: Ignored failure
    • 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
    • 40 days old (needed 5 days)
• ruby3.0 (3.0.3-1 to 3.0.4-7)
  • Migration status for ruby3.0 (3.0.3-1 to 3.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rails/2:6.1.4.6+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Ignored failure
    • autopkgtest for ruby-bootsnap/1.9.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for ruby-oj/3.13.9-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for ruby3.0/3.0.4-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Depends: ruby3.0 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby3.0.html
    • 40 days old (needed 5 days)
• iperf3 (3.9-1 to 3.11-2)
  • Migration status for iperf3 (3.9-1 to 3.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/i/iperf3.html
    • Depends: iperf3 openssl
  • Additional info:
    • 41 days old (needed 5 days)
• gdb (10.1-2 to 11.2-1)
  • Migration status for gdb (10.1-2 to 11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdb would introduce bugs in testing: #1012494
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdb.html
    • 42 days old (needed 5 days)
• php-xmlrpc (- to 3:1.0.0~rc3-2.1)
  • Migration status for php-xmlrpc (- to 3:1.0.0~rc3-2.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/php-xmlrpc.html
    • 42 days old (needed 5 days)
• plastimatch (1.9.3+dfsg.1-2 to 1.9.3+dfsg.1-3)
  • Migration status for plastimatch (1.9.3+dfsg.1-2 to 1.9.3+dfsg.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plastimatch would introduce bugs in testing: #1012439
    • plastimatch unsatisfiable Build-Depends(-Arch) on i386: libinsighttoolkit5-dev (>= 5.2.1-4)
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating plastimatch will fix bugs in testing: #1005485
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plastimatch.html
    • 43 days old (needed 5 days)
• ruby-prawn-templates (- to 0.1.2-2)
  • Migration status for ruby-prawn-templates (- to 0.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by keithp, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-prawn-templates.html
    • autopkgtest for ruby-prawn-templates/0.1.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 43 days old (needed 5 days)
• ruby3.1 (- to 3.1.2-1)
  • Migration status for ruby3.1 (- to 3.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rails/2:6.1.4.6+dfsg-3: amd64: Pass, arm64: Pass, armhf: Ignored failure, i386: Pass, ppc64el: Pass, s390x: Ignored failure
    • autopkgtest for ruby3.1/3.1.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by terceiro, a new source-only upload is needed to allow migration
    • Depends: ruby3.1 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby3.1.html
    • 43 days old (needed 5 days)
• slic3r-prusa (- to 2.4.2+dfsg-1)
  • Migration status for slic3r-prusa (- to 2.4.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): slic3r-prusa openvdb (not considered)
    • Depends: slic3r-prusa openvdb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • 43 days old (needed 5 days)
• python-svg.path (5.1~dfsg-1 to 6.0-1)
  • Migration status for python-svg.path (5.1~dfsg-1 to 6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-svg.path would introduce bugs in testing: #1010819
    • autopkgtest for python-svg.path/6.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-svg.path.html
    • 44 days old (needed 5 days)
• goffice (0.10.51-1 to 0.10.52-1)
  • Migration status for goffice (0.10.51-1 to 0.10.52-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goffice.html
    • 45 days old (needed 5 days)
• pwntools (- to 4.8.0-1)
  • Migration status for pwntools (- to 4.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pwntools unsatisfiable Build-Depends(-Arch) on amd64: python3-unicorn
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pwntools.html
    • 45 days old (needed 5 days)
• debian-edu-config (2.12.20 to 2.12.21)
  • Migration status for debian-edu-config (2.12.20 to 2.12.21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-edu-config would introduce bugs in testing: #1010432
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/debian-edu-config.html
    • autopkgtest for debian-edu-config/2.12.21: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for debian-edu-install/2.12.5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • 46 days old (needed 5 days)
• node-gitlab-favicon-overlay (- to 2.0.0-1)
  • Migration status for node-gitlab-favicon-overlay (- to 2.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/n/node-gitlab-favicon-overlay.html
    • autopkgtest for node-gitlab-favicon-overlay/2.0.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 46 days old (needed 5 days)
• node-webpack-env (- to 0.8.0-1)
  • Migration status for node-webpack-env (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-webpack-env/0.8.0-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by lolando, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-webpack-env.html
    • 46 days old (needed 5 days)
• openjdk-8 (- to 8u332-ga-1)
  • Migration status for openjdk-8 (- to 8u332-ga-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #989736
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-8.html
    • autopkgtest for libreoffice/blocked-on-ci-infra: i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • autopkgtest for nvidia-cuda-toolkit/blocked-on-ci-infra: ppc64el: Ignored failure
    • autopkgtest for openjdk-8/8u332-ga-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• phosh (0.17.0-1 to 0.17.0-2)
  • Migration status for phosh (0.17.0-1 to 0.17.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by agx
    • Not built on buildd: arch all binaries uploaded by agx, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phosh.html
    • autopkgtest for phosh/0.17.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 47 days old (needed 5 days)
• zpspell (- to 0.4.3-4.2)
  • Migration status for zpspell (- to 0.4.3-4.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zpspell zemberek-server (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zpspell.html
    • 47 days old (needed 5 days)
• ensmallen (2.18.2-1 to 2.19.0-1)
  • Migration status for ensmallen (2.18.2-1 to 2.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ensmallen would introduce bugs in testing: #1010431
    • autopkgtest for ensmallen/2.19.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ensmallen.html
    • 48 days old (needed 5 days)
• python-debianbts (3.2.0 to 3.2.1)
  • Migration status for python-debianbts (3.2.0 to 3.2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by venthur, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-debianbts.html
    • 48 days old (needed 5 days)
• python-duniterpy (0.62.0-3 to 1.1.0-2)
  • Migration status for python-duniterpy (0.62.0-3 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-duniterpy would introduce bugs in testing: #1010310
    • autopkgtest for python-duniterpy/1.1.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for silkaj/0.9.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-duniterpy.html
    • 49 days old (needed 5 days)
• mlpack (- to 3.4.2-7)
  • Migration status for mlpack (- to 3.4.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mlpack unsatisfiable Build-Depends(-Arch) on s390x: libomp-dev [!alpha !hppa !ia64 !m68k !sh4 !x32]
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlpack.html
    • 50 days old (needed 5 days)
• virtualbox-ext-pack (- to 6.1.34-1)
  • Migration status for virtualbox-ext-pack (- to 6.1.34-1): 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
    • 52 days old (needed 5 days)
• ocrad (- to 0.28-2)
  • Migration status for ocrad (- to 0.28-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocrad would introduce bugs in testing: #1004508
    • autopkgtest for ocrad/0.28-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocrad.html
    • 53 days old (needed 5 days)
• pyspread (2.0.1-1 to 2.1-2)
  • Migration status for pyspread (2.0.1-1 to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andreas@noteng.no, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyspread.html
    • autopkgtest for pyspread/2.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 53 days old (needed 2 days)
• db2twitter (- to 0.6-2)
  • Migration status for db2twitter (- to 0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating db2twitter would introduce bugs in testing: #996801
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/db2twitter.html
    • 54 days old (needed 5 days)
• pipenv (- to 11.9.0-2)
  • Migration status for pipenv (- to 11.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pipenv would introduce bugs in testing: #945139
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pipenv.html
    • 54 days old (needed 5 days)
• cgreen (1.4.1-1 to 1.5.1-1)
  • Migration status for cgreen (1.4.1-1 to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cgreen would introduce bugs in testing: #1010589
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for cgreen/1.5.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cgreen.html
    • 55 days old (needed 5 days)
• faketime (0.9.8-9 to 0.9.10-2)
  • Migration status for faketime (0.9.8-9 to 0.9.10-2): 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
    • missing build on mipsel
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for faketime/0.9.10-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating faketime will fix bugs in testing: #1010814
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/faketime.html
    • 55 days old (needed 5 days)
• staticsite (- to 1.5-1)
  • Migration status for staticsite (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating staticsite would introduce bugs in testing: #949756
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/staticsite.html
    • 56 days old (needed 5 days)
• xml2rfc (- to 3.12.4-1)
  • Migration status for xml2rfc (- to 3.12.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xml2rfc would introduce bugs in testing: #1010821
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for xml2rfc/3.12.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 57 days old (needed 2 days)
• bird2 (2.0.8-2 to 2.0.9-3)
  • Migration status for bird2 (2.0.8-2 to 2.0.9-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating bird2 will fix bugs in testing: #1012187
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bird2.html
    • 58 days old (needed 5 days)
• golang-github-sylabs-sif (- to 2.3.1-3)
  • Migration status for golang-github-sylabs-sif (- to 2.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-sylabs-sif/2.3.1-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sylabs-sif.html
    • 58 days old (needed 5 days)
• nvidia-settings-legacy-340xx (- to 340.108-5)
  • Migration status for nvidia-settings-legacy-340xx (- to 340.108-5): 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)
    • 58 days old (needed 5 days)
• nvidia-settings-tesla-418 (- to 418.113-7)
  • Migration status for nvidia-settings-tesla-418 (- to 418.113-7): 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)
    • 58 days old (needed 5 days)
• foliate (- to 2.6.4-1+dfsg1)
  • Migration status for foliate (- to 2.6.4-1+dfsg1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating foliate would introduce bugs in testing: #1009669
    • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foliate.html
    • 59 days old (needed 5 days)
• kross-interpreters (- to 4:21.12.3-1)
  • Migration status for kross-interpreters (- to 4:21.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kross-interpreters would introduce bugs in testing: #936809
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kross-interpreters.html
    • 59 days old (needed 5 days)
• node-canvas-confetti (- to 1.5.1-1)
  • Migration status for node-canvas-confetti (- to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-canvas-confetti/1.5.1-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by x.guimard@free.fr, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-canvas-confetti.html
    • 59 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-14)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #973599, #979671, #987217, #991352
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-14: amd64: No test results, armhf: No test results, i386: No test results
    • 60 days old (needed 5 days)
• appstream-generator (- to 0.8.8-1)
  • Migration status for appstream-generator (- to 0.8.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: appstream-generator -> libphobos2-ldc-shared98/1:1.28.1-1/amd64
    • Impossible Depends: appstream-generator -> libphobos2-ldc-shared98/1:1.28.1-1/arm64
    • Build-Depends(-Arch): appstream-generator glib-d
    • Depends: appstream-generator glib-d
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-generator.html
    • 61 days old (needed 5 days)
• libgrokj2k (- to 9.7.5-1)
  • Migration status for libgrokj2k (- to 9.7.5-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 mipsel
    • missing build on ppc64el
    • missing build on s390x
    • 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/libg/libgrokj2k.html
    • 61 days old (needed 5 days)
• python-gitlab (1:2.10.1-2 to 1:3.3.0-1)
  • Migration status for python-gitlab (1:2.10.1-2 to 1:3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-gitlab would introduce bugs in testing: #1010119
  • Additional info:
    • Updating python-gitlab will fix bugs in testing: #1012628
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gitlab.html
    • autopkgtest for python-gitlab/1:3.3.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 61 days old (needed 5 days)
• boxbackup (- to 0.13~~git20220405.g7703ac8-1)
  • Migration status for boxbackup (- to 0.13~~git20220405.g7703ac8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating boxbackup would introduce bugs in testing: #995640
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boxbackup.html
    • 62 days old (needed 5 days)
• medialibrary (- to 0.11.2-1)
  • Migration status for medialibrary (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating medialibrary would introduce bugs in testing: #949532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/medialibrary.html
    • 62 days old (needed 5 days)
• ruby-webauthn (- to 2.5.1-1)
  • Migration status for ruby-webauthn (- to 2.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-webauthn would introduce bugs in testing: #1005444
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-webauthn.html
    • autopkgtest for ruby-webauthn/2.5.1-1: amd64: No test results, arm64: No test results, armhf: Not a regression, i386: Not a regression, ppc64el: No test results, s390x: No test results
    • 62 days old (needed 5 days)
• symfit (- to 0.5.5-1)
  • Migration status for symfit (- to 0.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for symfit/0.5.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/symfit.html
    • 62 days old (needed 5 days)
• mediaconch (- to 22.03-2)
  • Migration status for mediaconch (- to 22.03-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mediaconch would introduce bugs in testing: #963445
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediaconch.html
    • 64 days old (needed 5 days)
• rust-sha-1 (- to 0.8.1-2.1)
  • Migration status for rust-sha-1 (- to 0.8.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-sha-1+asm-dev/amd64 has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/amd64 has unsatisfiable dependency
    • librust-sha-1+asm-dev/arm64 has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/arm64 has unsatisfiable dependency
    • librust-sha-1+asm-dev/armel has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/armel has unsatisfiable dependency
    • librust-sha-1+asm-dev/armhf has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/armhf has unsatisfiable dependency
    • librust-sha-1+asm-dev/i386 has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/i386 has unsatisfiable dependency
    • librust-sha-1+asm-dev/mips64el has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/mips64el has unsatisfiable dependency
    • librust-sha-1+asm-dev/mipsel has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/mipsel has unsatisfiable dependency
    • librust-sha-1+asm-dev/ppc64el has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/ppc64el has unsatisfiable dependency
    • librust-sha-1+asm-dev/s390x has unsatisfiable dependency
    • librust-sha-1+sha1-asm-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha-1.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
    • 64 days old (needed 5 days)
• icingaweb2 (- to 2.10.1-1)
  • Migration status for icingaweb2 (- to 2.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating icingaweb2 would introduce bugs in testing: #1000474
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2.html
    • 65 days old (needed 5 days)
• xfce4-panel-profiles (- to 1.0.13-1)
  • Migration status for xfce4-panel-profiles (- to 1.0.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by samueloph, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-panel-profiles.html
    • 65 days old (needed 5 days)
• blender (- to 3.1.2+dfsg-1)
  • Migration status for blender (- to 3.1.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating blender would introduce bugs in testing: #1011653
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mipsel
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): blender embree
    • Build-Depends(-Arch): blender opencolorio
    • Build-Depends(-Arch): blender openimageio
    • Build-Depends(-Arch): blender openvdb
    • Depends: blender embree
    • Depends: blender openimageio
    • Depends: blender openvdb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blender.html
    • 66 days old (needed 5 days)
• mptcpd (- to 0.9-1)
  • Migration status for mptcpd (- to 0.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kilobyte
    • Not built on buildd: arch all binaries uploaded by kilobyte, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mptcpd.html
    • 66 days old (needed 5 days)
• remrun (- to 0.2.0-1)
  • Migration status for remrun (- 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 roam@ringlet.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/remrun.html
    • autopkgtest for remrun/0.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 66 days old (needed 2 days)
• xserver-xorg-video-qxl (- to 0.1.5+git20200331-3)
  • Migration status for xserver-xorg-video-qxl (- to 0.1.5+git20200331-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-qxl would introduce bugs in testing: #1004154
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-qxl.html
    • 66 days old (needed 5 days)
• embree (- to 3.13.3+dfsg-1)
  • Migration status for embree (- to 3.13.3+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): embree openimageio (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/embree.html
    • 67 days old (needed 5 days)
• cawbird (- to 1.5-1)
  • Migration status for cawbird (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cawbird/1.5-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cawbird.html
    • 68 days old (needed 5 days)
• puma (5.5.2-2 to 5.6.4-1)
  • Migration status for puma (5.5.2-2 to 5.6.4-1): Will attempt migration (Any information below is purely informational)
    • Depends: puma openssl
  • Additional info:
    • Updating puma will fix bugs in testing: #1006022
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puma.html
    • autopkgtest for puma/5.6.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rails/2:6.1.4.6+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Ignored failure
    • Required age reduced by 3 days because of autopkgtest
    • 68 days old (needed 2 days)
• rust-zstd-sys (- to 1.4.15-1.1)
  • Migration status for rust-zstd-sys (- to 1.4.15-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-zstd-sys/1.4.15-1.1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zstd-sys.html
    • 68 days old (needed 5 days)
• android-platform-system-core (- to 1:10.0.0+r36-10)
  • Migration status for android-platform-system-core (- to 1:10.0.0+r36-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • android-libadb/amd64 has unsatisfiable dependency
    • android-libadb-dev/amd64 has unsatisfiable dependency
    • android-libnativebridge-dev/amd64 has unsatisfiable dependency
    • android-libnativeloader-dev/amd64 has unsatisfiable dependency
    • android-libadb/arm64 has unsatisfiable dependency
    • android-libadb-dev/arm64 has unsatisfiable dependency
    • android-libnativebridge-dev/arm64 has unsatisfiable dependency
    • android-libnativeloader-dev/arm64 has unsatisfiable dependency
    • android-libadb/armel has unsatisfiable dependency
    • android-libadb/armhf has unsatisfiable dependency
    • android-libadb/i386 has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-system-core.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • autopkgtest for android-platform-system-core/1:10.0.0+r36-10: armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 69 days old (needed 5 days)
• intake (- to 0.6.5-2)
  • Migration status for intake (- to 0.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intake would introduce bugs in testing: #997059
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • autopkgtest for intake/0.6.5-2: arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • 69 days old (needed 5 days)
• ippsample (- to 0.0~git20220215.f365352-1)
  • Migration status for ippsample (- to 0.0~git20220215.f365352-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ippsample would introduce bugs in testing: #1009437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • 70 days old (needed 5 days)
• prospector (- to 1.1.7-3)
  • Migration status for prospector (- to 1.1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prospector would introduce bugs in testing: #947551
    • Build-Depends(-Arch): prospector python-requirements-detector
    • Depends: prospector python-requirements-detector
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prospector.html
    • autopkgtest for prospector/1.1.7-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 70 days old (needed 2 days)
• sfepy (- to 2021.4-1)
  • Migration status for sfepy (- to 2021.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/sfepy.html
    • 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 mipsel
    • missing build on ppc64el
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): sfepy python-sparse
  • Additional info:
    • 70 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 unsatisfiable Build-Depends(-Arch) on amd64: libpappsomspp-dev (>= 0.8.49)
    • i2masschroq unsatisfiable Build-Depends(-Arch) on amd64: libpappsomspp-widget-dev (>= 0.8.49)
    • 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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2masschroq.html
    • 71 days old (needed 5 days)
• slop (7.5-1.1 to 7.6-1)
  • Migration status for slop (7.5-1.1 to 7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slop would introduce bugs in testing: #1009010
  • Additional info:
    • Updating slop will fix bugs in testing: #1012190
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slop.html
    • 71 days old (needed 5 days)
• xorgxrdp (- to 1:0.2.18-1)
  • Migration status for xorgxrdp (- to 1:0.2.18-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): xorgxrdp xrdp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xorgxrdp.html
    • autopkgtest for xorgxrdp/1:0.2.18-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 71 days old (needed 2 days)
• xrdp (- to 0.9.19-1)
  • Migration status for xrdp (- to 0.9.19-1): Will attempt migration (Any information below is purely informational)
    • Depends: xrdp openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrdp.html
    • 71 days old (needed 5 days)
• git-sizer (1.3.0+dfsg-1 to 1.5.0-1)
  • Migration status for git-sizer (1.3.0+dfsg-1 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git-sizer would introduce bugs in testing: #1009690, #1010541
  • Additional info:
    • Updating git-sizer will fix bugs in testing: #1012192
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-sizer.html
    • autopkgtest for git-sizer/1.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 72 days old (needed 2 days)
• openstack-trove (- to 1:17.0.0-1)
  • Migration status for openstack-trove (- to 1:17.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: openstack-trove python-cassandra-driver (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstack-trove.html
    • 72 days old (needed 5 days)
• gliese (- to 3.0.95-3)
  • Migration status for gliese (- to 3.0.95-3): 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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 73 days old (needed 5 days)
• yale (- to 5.0.95-3)
  • Migration status for yale (- to 5.0.95-3): 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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 73 days old (needed 5 days)
• pigx-rnaseq (- to 0.0.19+ds-1)
  • Migration status for pigx-rnaseq (- to 0.0.19+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pigx-rnaseq salmon (not considered)
    • Depends: pigx-rnaseq salmon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pigx-rnaseq.html
    • 75 days old (needed 5 days)
• yosys (0.9-2 to 0.15-1)
  • Migration status for yosys (0.9-2 to 0.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yosys would introduce bugs in testing: #1010964
    • autopkgtest for yosys/0.15-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Pass
    • missing build on mips64el
  • Additional info:
    • Updating yosys will fix bugs in testing: #1008718
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yosys.html
    • 75 days old (needed 5 days)
• jellyfish1 (1.1.11-6 to 1.1.11-7)
  • Migration status for jellyfish1 (1.1.11-6 to 1.1.11-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jellyfish1 would introduce bugs in testing: #1008944
    • autopkgtest for jellyfish1/1.1.11-7: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Updating jellyfish1 will fix bugs in testing: #1011541
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jellyfish1.html
    • 78 days old (needed 5 days)
• nautilus-sendto (- to 3.8.6-4)
  • Migration status for nautilus-sendto (- to 3.8.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nautilus-sendto would introduce bugs in testing: #966180
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-sendto.html
    • 79 days old (needed 5 days)
• node-openid (- to 2.0.10+~2.0.2-3)
  • Migration status for node-openid (- to 2.0.10+~2.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-openid would introduce bugs in testing: #1008170
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-openid.html
    • autopkgtest for node-openid/2.0.10+~2.0.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: No test results, ppc64el: No test results, s390x: No test results
    • 79 days old (needed 5 days)
• golang-github-apptainer-container-key-client (- to 0.7.2-1)
  • Migration status for golang-github-apptainer-container-key-client (- to 0.7.2-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/g/golang-github-apptainer-container-key-client.html
    • autopkgtest for golang-github-apptainer-container-key-client/0.7.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 80 days old (needed 2 days)
• golang-github-apptainer-container-library-client (- to 1.2.2-1)
  • Migration status for golang-github-apptainer-container-library-client (- to 1.2.2-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/g/golang-github-apptainer-container-library-client.html
    • autopkgtest for golang-github-apptainer-container-library-client/1.2.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 80 days old (needed 2 days)
• kotlin-mode (- to 0.0~git20210917.3e0c340-1)
  • Migration status for kotlin-mode (- to 0.0~git20210917.3e0c340-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by nsteeves@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlin-mode.html
    • autopkgtest for kotlin-mode/0.0~git20210917.3e0c340-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 80 days old (needed 2 days)
• pytorch (- to 1.8.1-5)
  • Migration status for pytorch (- to 1.8.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytorch would introduce bugs in testing: #1009200
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch.html
    • autopkgtest for pytorch/1.8.1-5: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Not a regression
    • 80 days old (needed 5 days)
• victoriametrics (1.74.0+ds1-1 to 1.75.0+ds1-1)
  • Migration status for victoriametrics (1.74.0+ds1-1 to 1.75.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating victoriametrics would introduce bugs in testing: #1010544
    • missing build on armel
  • Additional info:
    • Updating victoriametrics will fix bugs in testing: #1011409
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/victoriametrics.html
    • autopkgtest for victoriametrics/1.75.0+ds1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 80 days old (needed 2 days)
• win32-loader (0.10.4 to 0.10.6)
  • Migration status for win32-loader (0.10.4 to 0.10.6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: win32-loader grub2 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Updating win32-loader will fix bugs in testing: #998353
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win32-loader.html
    • autopkgtest for win32-loader/0.10.6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 80 days old (needed 2 days)
• mkdocs-material (- to 8.2.5-1)
  • Migration status for mkdocs-material (- to 8.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mkdocs-material/amd64 has unsatisfiable dependency
    • mkdocs-material/arm64 has unsatisfiable dependency
    • Updating mkdocs-material would introduce bugs in testing: #1008691
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mkdocs-material.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 81 days old (needed 5 days)
• parlatype (3.0-2 to 3.1-1)
  • Migration status for parlatype (3.0-2 to 3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parlatype would introduce bugs in testing: #1008132
    • missing build on mips64el
    • missing build on mipsel
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for parlatype/3.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Updating parlatype will fix bugs in testing: #1011356
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parlatype.html
    • 83 days old (needed 5 days)
• xtpcpp (- to 0.4.53-1)
  • Migration status for xtpcpp (- to 0.4.53-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xtpcpp unsatisfiable Build-Depends(-Arch) on arm64: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on arm64: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on armel: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on armel: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on armhf: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on armhf: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on i386: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on i386: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on mips64el: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on mips64el: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on mipsel: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on mipsel: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on ppc64el: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on ppc64el: libpappsomspp-widget-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on s390x: libpappsomspp-dev (>= 0.8.49)
    • xtpcpp unsatisfiable Build-Depends(-Arch) on s390x: libpappsomspp-widget-dev (>= 0.8.49)
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on mipsel
    • missing build on ppc64el
    • 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:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 83 days old (needed 5 days)
• budgie-indicator-applet (- to 0.7.2-2)
  • Migration status for budgie-indicator-applet (- to 0.7.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: budgie-indicator-applet ayatana-indicator-application (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/budgie-indicator-applet.html
    • 84 days old (needed 5 days)
• knot-resolver (- to 5.5.0-1)
  • Migration status for knot-resolver (- to 5.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for knot-resolver/5.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: No test results
    • Depends: knot-resolver lua-http
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knot-resolver.html
    • 85 days old (needed 5 days)
• node-is-wsl (- to 2.2.0-2)
  • Migration status for node-is-wsl (- to 2.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-is-wsl/2.2.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-is-wsl.html
    • 86 days old (needed 5 days)
• ruby-simplecov (0.19.1-1 to 0.21.2-1)
  • Migration status for ruby-simplecov (0.19.1-1 to 0.21.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-simplecov would introduce bugs in testing: #1008214
    • autopkgtest for ruby-simplecov/0.21.2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating ruby-simplecov will fix bugs in testing: #1010969
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-simplecov.html
    • 89 days old (needed 5 days)
• cryptsetup-nuke-password (- to 3)
  • Migration status for cryptsetup-nuke-password (- to 3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cryptsetup-nuke-password would introduce bugs in testing: #1007237
    • autopkgtest for cryptsetup-nuke-password/3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by mejo
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptsetup-nuke-password.html
    • 90 days old (needed 5 days)
• pushpin (- to 1.35.0-1)
  • Migration status for pushpin (- to 1.35.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pushpin.html
    • 90 days old (needed 5 days)
• aeonbits-owner (- to 1.0.12+ds-2)
  • Migration status for aeonbits-owner (- to 1.0.12+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: aeonbits-owner zookeeper (not considered)
    • Invalidated by build-dependency (indep)
    • Build-Depends-Indep: aeonbits-owner apache-curator
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aeonbits-owner.html
    • 91 days old (needed 5 days)
• lomiri-settings-components (- to 1.0.0-3)
  • Migration status for lomiri-settings-components (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • qml-module-lomiri-settings-fingerprint/amd64 has unsatisfiable dependency
    • qml-module-lomiri-settings-fingerprint/arm64 has unsatisfiable dependency
    • qml-module-lomiri-settings-fingerprint/armel has unsatisfiable dependency
    • qml-module-lomiri-settings-fingerprint/armhf has unsatisfiable dependency
    • qml-module-lomiri-settings-fingerprint/i386 has unsatisfiable dependency
    • qml-module-lomiri-settings-fingerprint/ppc64el has unsatisfiable dependency
    • qml-module-lomiri-settings-fingerprint/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): lomiri-settings-components lomiri-ui-toolkit
    • Depends: lomiri-settings-components lomiri-ui-toolkit
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lomiri-settings-components.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
    • 92 days old (needed 5 days)
• pysph (- to 1.0~b1-1)
  • Migration status for pysph (- to 1.0~b1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pysph unsatisfiable Build-Depends(-Arch) on ppc64el: python3-pyopencl
    • pysph unsatisfiable Build-Depends(-Arch) on s390x: python3-pyopencl
    • missing build on ppc64el
    • missing build on s390x
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for pysph/1.0~b1-1: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Not a regression
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysph.html
    • 92 days old (needed 5 days)
• content-hub (- to 1.0.0-2)
  • Migration status for content-hub (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for content-hub/1.0.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Build-Depends(-Arch): content-hub lomiri-app-launch
    • Build-Depends(-Arch): content-hub lomiri-download-manager
    • Build-Depends(-Arch): content-hub lomiri-ui-toolkit
    • Depends: content-hub lomiri-app-launch
    • Depends: content-hub lomiri-download-manager
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/content-hub.html
    • 94 days old (needed 5 days)
• php-horde-imap-client (- to 2.30.4-1)
  • Migration status for php-horde-imap-client (- to 2.30.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-imap-client php-horde-secret (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imap-client.html
    • autopkgtest for php-horde-imap-client/2.30.4-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 94 days old (needed 5 days)
• php-horde-mime-viewer (- to 2.2.4+debian0-1)
  • Migration status for php-horde-mime-viewer (- to 2.2.4+debian0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-mime-viewer php-horde-compress (not considered)
    • Invalidated by dependency
    • Depends: php-horde-mime-viewer php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime-viewer.html
    • 94 days old (needed 5 days)
• php-solr (- to 2.5.1+2.4.0-15)
  • Migration status for php-solr (- to 2.5.1+2.4.0-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by ondrej
    • Not built on buildd: arch all binaries uploaded by ondrej, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-solr.html
    • 94 days old (needed 5 days)
• pngnq (- to 1.1+ds-1)
  • Migration status for pngnq (- to 1.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pngnq would introduce bugs in testing: #1008342
    • 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 mipsel
    • 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: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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pngnq.html
    • 95 days old (needed 5 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 95 days old (needed 2 days)
• lomiri-ui-extras (- to 0.5-2)
  • Migration status for lomiri-ui-extras (- to 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): lomiri-ui-extras lomiri-ui-toolkit (not considered)
    • Depends: lomiri-ui-extras lomiri-ui-toolkit (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-ui-extras.html
    • 96 days old (needed 5 days)
• aqsis (- to 1.8.2+git20210815-1)
  • Migration status for aqsis (- to 1.8.2+git20210815-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aqsis would introduce bugs in testing: #1010140
    • Not built on buildd: arch all binaries uploaded by manuel.montezelo@gmail.com, a new source-only upload is needed to allow migration
    • missing build on armel
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for aqsis/1.8.2+git20210815-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aqsis.html
    • 97 days old (needed 5 days)
• freecad (- to 0.19.4+dfsg1-1)
  • Migration status for freecad (- to 0.19.4+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freecad would introduce bugs in testing: #1007013
    • autopkgtest for freecad/0.19.4+dfsg1-1: amd64: Pass, arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecad.html
    • 98 days old (needed 5 days)
• libigloo (0.9.0-1 to 0.9.1-1)
  • Migration status for libigloo (0.9.0-1 to 0.9.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
  • Additional info:
    • Updating libigloo will fix bugs in testing: #1010484
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libigloo.html
    • 101 days old (needed 5 days)
• hurd (- to 1:0.9.git20220301-1)
  • Migration status for hurd (- to 1:0.9.git20220301-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
    • 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
    • 102 days old (needed 5 days)
• kakoune (2020.09.01-3 to 2021.11.08-1)
  • Migration status for kakoune (2020.09.01-3 to 2021.11.08-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kakoune would introduce bugs in testing: #1011978
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for kakoune/2021.11.08-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Updating kakoune will fix bugs in testing: #1010335
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kakoune.html
    • 103 days old (needed 5 days)
• mkdocs-material-extensions (- to 1.0.3-1)
  • Migration status for mkdocs-material-extensions (- to 1.0.3-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/m/mkdocs-material-extensions.html
    • 103 days old (needed 5 days)
• ayatana-webmail (- to 22.2.26+dfsg1-1)
  • Migration status for ayatana-webmail (- to 22.2.26+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ayatana-webmail ayatana-indicator-messages (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-webmail.html
    • 104 days old (needed 5 days)
• drool (- to 2.0.0-1)
  • Migration status for drool (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drool.html
    • 104 days old (needed 5 days)
• guzzle (- to 7.4.1-1)
  • Migration status for guzzle (- to 7.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guzzle would introduce bugs in testing: #1011636
    • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guzzle.html
    • 104 days old (needed 5 days)
• lomiri-url-dispatcher (- to 0.1.0-7)
  • Migration status for lomiri-url-dispatcher (- to 0.1.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-url-dispatcher lomiri-app-launch (not considered)
    • Depends: lomiri-url-dispatcher lomiri-app-launch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-url-dispatcher.html
    • 104 days old (needed 5 days)
• matrix-mirage (- to 0.7.2~dfsg+~hsluv1.0.0+~1.0.0-9)
  • Migration status for matrix-mirage (- to 0.7.2~dfsg+~hsluv1.0.0+~1.0.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: matrix-mirage python-html-sanitizer (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matrix-mirage.html
    • 105 days old (needed 5 days)
• adldap2 (- to 10.4.1-1)
  • Migration status for adldap2 (- to 10.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
    • Depends: adldap2 php-laravel-framework
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adldap2.html
    • 106 days old (needed 5 days)
• ayatana-indicator-sound (- to 22.2.0-2)
  • Migration status for ayatana-indicator-sound (- to 22.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): ayatana-indicator-sound libayatana-common (not considered)
    • Depends: ayatana-indicator-sound libayatana-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-sound.html
    • 106 days old (needed 5 days)
• jp (- to 0.1.3-3)
  • Migration status for jp (- 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): jp golang-codegangsta-cli (not considered)
    • Built-Using: jp golang-codegangsta-cli (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jp.html
    • 106 days old (needed 5 days)
• pass-audit (- to 1.2-1)
  • Migration status for pass-audit (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-audit.html
    • autopkgtest for pass-audit/1.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 106 days old (needed 2 days)
• visp (- to 3.5.0-2)
  • Migration status for visp (- to 3.5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): visp ogre-1.9 (not considered)
    • Depends: visp ogre-1.9 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/visp.html
    • autopkgtest for visp/3.5.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 107 days old (needed 2 days)
• ruby-clockwork (- to 2.0.4-2)
  • Migration status for ruby-clockwork (- to 2.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-clockwork would introduce bugs in testing: #1006982
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-clockwork.html
    • autopkgtest for ruby-clockwork/2.0.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 108 days old (needed 2 days)
• tilix (- to 1.9.5-1)
  • Migration status for tilix (- to 1.9.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: tilix -> libphobos2-ldc-shared98/1:1.28.1-1/amd64
    • Impossible Depends: tilix -> libphobos2-ldc-shared98/1:1.28.1-1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tilix.html
    • 108 days old (needed 5 days)
• collectd (- to 5.12.0-9)
  • Migration status for collectd (- to 5.12.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): collectd varnish (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/collectd.html
    • 109 days old (needed 5 days)
• python-aioapns (- to 2.1-1)
  • Migration status for python-aioapns (- to 2.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioapns.html
    • autopkgtest for python-aioapns/2.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 109 days old (needed 5 days)
• python-rcon (- to 1.3.8-1)
  • Migration status for python-rcon (- to 1.3.8-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-rcon.html
    • autopkgtest for python-rcon/1.3.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 109 days old (needed 2 days)
• screenruler (- to 1.0-2)
  • Migration status for screenruler (- to 1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: screenruler ruby-gnome (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/screenruler.html
    • 109 days old (needed 5 days)
• ayatana-indicator-datetime (- to 22.2.0-1)
  • Migration status for ayatana-indicator-datetime (- to 22.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): ayatana-indicator-datetime lomiri-url-dispatcher (not considered)
    • Depends: ayatana-indicator-datetime lomiri-url-dispatcher (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ayatana-indicator-datetime ayatana-indicator-messages
    • Build-Depends(-Arch): ayatana-indicator-datetime libayatana-common
    • Depends: ayatana-indicator-datetime ayatana-indicator-messages
    • Depends: ayatana-indicator-datetime libayatana-common
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-datetime.html
    • 110 days old (needed 5 days)
• ayatana-indicator-power (- to 22.2.0-1)
  • Migration status for ayatana-indicator-power (- to 22.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): ayatana-indicator-power libayatana-common (not considered)
    • Depends: ayatana-indicator-power libayatana-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-power.html
    • 110 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • autopkgtest for notcurses/3.0.7+dfsg.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 110 days old (needed 5 days)
• golang-github-goccy-go-yaml (- to 1.9.5-2)
  • Migration status for golang-github-goccy-go-yaml (- to 1.9.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-goccy-go-yaml/1.9.5-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-goccy-go-yaml.html
    • 111 days old (needed 5 days)
• ayatana-indicator-application (- to 22.2.0-1)
  • Migration status for ayatana-indicator-application (- to 22.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ayatana-indicator-application libayatana-common (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-application.html
    • 112 days old (needed 5 days)
• ayatana-indicator-bluetooth (- to 22.2.0-1)
  • Migration status for ayatana-indicator-bluetooth (- to 22.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): ayatana-indicator-bluetooth libayatana-common (not considered)
    • Depends: ayatana-indicator-bluetooth libayatana-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-bluetooth.html
    • 112 days old (needed 5 days)
• ayatana-indicator-display (- to 22.2.0-1)
  • Migration status for ayatana-indicator-display (- to 22.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): ayatana-indicator-display libayatana-common (not considered)
    • Depends: ayatana-indicator-display libayatana-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-display.html
    • 112 days old (needed 5 days)
• ayatana-indicator-keyboard (- to 22.2.0-1)
  • Migration status for ayatana-indicator-keyboard (- to 22.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): ayatana-indicator-keyboard libayatana-common (not considered)
    • Depends: ayatana-indicator-keyboard libayatana-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-keyboard.html
    • 112 days old (needed 5 days)
• ayatana-indicator-messages (- to 22.2.0-1)
  • Migration status for ayatana-indicator-messages (- to 22.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ayatana-indicator-messages libayatana-common (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-messages.html
    • 112 days old (needed 5 days)
• ayatana-indicator-notifications (- to 22.2.0-1)
  • Migration status for ayatana-indicator-notifications (- to 22.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ayatana-indicator-notifications libayatana-common (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-notifications.html
    • 112 days old (needed 5 days)
• ayatana-indicator-printers (- to 22.2.0-1)
  • Migration status for ayatana-indicator-printers (- to 22.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ayatana-indicator-printers libayatana-common (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-printers.html
    • 112 days old (needed 5 days)
• gazebo (- to 11.10.1+dfsg-2)
  • Migration status for gazebo (- to 11.10.1+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gazebo ogre-1.9 (not considered)
    • Depends: gazebo ogre-1.9 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gazebo.html
    • autopkgtest for gazebo/11.10.1+dfsg-2: amd64: No test results, arm64: Not a regression, armhf: Not a regression, i386: No test results, ppc64el: Not a regression, s390x: Not a regression
    • 112 days old (needed 5 days)
• ayatana-indicator-session (- to 22.2.0-1)
  • Migration status for ayatana-indicator-session (- to 22.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): ayatana-indicator-session libayatana-common (not considered)
    • Depends: ayatana-indicator-session libayatana-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-session.html
    • autopkgtest for ayatana-indicator-session/blocked-on-ci-infra: amd64: Ignored failure, arm64: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • 113 days old (needed 5 days)
• libayatana-common (- to 0.9.7-1)
  • Migration status for libayatana-common (- to 0.9.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: libayatana-common lomiri-url-dispatcher (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libayatana-common.html
    • 113 days old (needed 5 days)
• node-lockfile (- to 1.0.4+~1.0.2-1)
  • Migration status for node-lockfile (- to 1.0.4+~1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-lockfile would introduce bugs in testing: #1005940
    • autopkgtest for node-lockfile/1.0.4+~1.0.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-lockfile.html
    • 113 days old (needed 5 days)
• eye (- to 22.0203.1955~ds-1)
  • Migration status for eye (- to 22.0203.1955~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eye would introduce bugs in testing: #1006818
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eye.html
    • autopkgtest for eye/22.0203.1955~ds-1: amd64: Pass, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 115 days old (needed 5 days)
• golang-github-smallstep-certificates (- to 0.15.15-2)
  • Migration status for golang-github-smallstep-certificates (- to 0.15.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-smallstep-certificates would introduce bugs in testing: #1010392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-smallstep-certificates.html
    • autopkgtest for golang-github-smallstep-certificates/0.15.15-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 115 days old (needed 2 days)
• firmware-microbit-micropython (- to 1.0.1-3)
  • Migration status for firmware-microbit-micropython (- to 1.0.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): firmware-microbit-micropython yotta (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firmware-microbit-micropython.html
    • 116 days old (needed 5 days)
• ghdl (- to 1.0.0+dfsg-8)
  • Migration status for ghdl (- to 1.0.0+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ghdl would introduce bugs in testing: #1010539
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for ghdl/1.0.0+dfsg-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghdl.html
    • 116 days old (needed 5 days)
• python-uflash (- to 1.2.4+dfsg-9)
  • Migration status for python-uflash (- to 1.2.4+dfsg-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-uflash firmware-microbit-micropython (not considered)
    • Depends: python-uflash firmware-microbit-micropython (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uflash.html
    • autopkgtest for python-uflash/1.2.4+dfsg-9: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 116 days old (needed 2 days)
• tpot (- to 0.11.7+dfsg-3)
  • Migration status for tpot (- to 0.11.7+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tpot pytorch (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpot.html
    • autopkgtest for tpot/0.11.7+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 116 days old (needed 5 days)
• exempi (2.5.2-1 to 2.6.1-1)
  • Migration status for exempi (2.5.2-1 to 2.6.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
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Updating exempi will fix bugs in testing: #1009733
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exempi.html
    • 117 days old (needed 5 days)
• gifwrap (- to 0.0.6+dfsg-1)
  • Migration status for gifwrap (- to 0.0.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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/g/gifwrap.html
    • autopkgtest for gifwrap/0.0.6+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 117 days old (needed 2 days)
• logging-tree (- to 1.9-1)
  • Migration status for logging-tree (- to 1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/logging-tree.html
    • 117 days old (needed 5 days)
• python-pathvalidate (- to 2.5.0-1)
  • Migration status for python-pathvalidate (- to 2.5.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
    • Build-Depends(-Arch): python-pathvalidate python-allpairspy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pathvalidate.html
    • autopkgtest for python-pathvalidate/2.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 117 days old (needed 2 days)
• libvmod-re2 (- to 2.0.0-1)
  • Migration status for libvmod-re2 (- 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): 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-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 118 days old (needed 2 days)
• libvmod-redis (- to 13.0-1)
  • Migration status for libvmod-redis (- to 13.0-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/13.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 118 days old (needed 2 days)
• libvmod-selector (- to 2.6.0-1)
  • Migration status for libvmod-selector (- to 2.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): 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-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 118 days old (needed 2 days)
• node-bash-color (- to 0.0.4-1)
  • Migration status for node-bash-color (- to 0.0.4-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-bash-color.html
    • autopkgtest for node-bash-color/0.0.4-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 118 days old (needed 5 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 118 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:
    • 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 118 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-bash-color
    • Build-Depends(-Arch): node-grunt-timer node-functional.js
    • Depends: node-grunt-timer node-bash-color
    • 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 118 days old (needed 2 days)
• poliastro (- to 0.16.2-1)
  • Migration status for poliastro (- to 0.16.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): poliastro numba (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poliastro.html
    • autopkgtest for poliastro/0.16.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 118 days old (needed 5 days)
• sphinx-notfound-page (- to 0.8-1)
  • Migration status for sphinx-notfound-page (- to 0.8-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-notfound-page.html
    • 118 days old (needed 5 days)
• mpl-sphinx-theme (- to 0.0.6-1)
  • Migration status for mpl-sphinx-theme (- to 0.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by morph, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpl-sphinx-theme.html
    • autopkgtest for mpl-sphinx-theme/0.0.6-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 121 days old (needed 5 days)
• nbsdgames (- to 5-2)
  • Migration status for nbsdgames (- to 5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/nbsdgames.html
  • Additional info:
    • 121 days old (needed 5 days)
• rust-tree-magic (- to 0.2.3-1)
  • Migration status for rust-tree-magic (- to 0.2.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-tree-magic rust-nom-3 (not considered)
    • Depends: rust-tree-magic rust-nom-3 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tree-magic.html
    • autopkgtest for rust-tree-magic/0.2.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 121 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
    • Depends: guacamole-server openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guacamole-server.html
    • 123 days old (needed 5 days)
• lava (- to 2022.01.3-3)
  • Migration status for lava (- to 2022.01.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lava would introduce bugs in testing: #979887
    • autopkgtest for lava/2022.01.3-3: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
    • 123 days old (needed 5 days)
• rust-os-display (- to 0.1.3-1)
  • Migration status for rust-os-display (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-os-display/0.1.3-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-os-display.html
    • 123 days old (needed 5 days)
• yotta (- to 0.20.5-5)
  • Migration status for yotta (- to 0.20.5-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): yotta jekyll (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yotta.html
    • autopkgtest for yotta/0.20.5-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 126 days old (needed 2 days)
• debian-design (- to 3.0.26)
  • Migration status for debian-design (- to 3.0.26): 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
    • Depends: debian-design luakit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-design.html
    • 127 days old (needed 5 days)
• gst-plugins-bad1.0-contrib (- to 1.20.0-1)
  • Migration status for gst-plugins-bad1.0-contrib (- to 1.20.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on i386
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 127 days old (needed 5 days)
• octave-database (- to 2.4.4-5)
  • Migration status for octave-database (- to 2.4.4-5): 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-5: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Pass, ppc64el: Pass, s390x: Pass
    • 128 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:
    • dioptas unsatisfiable Build-Depends(-Arch) on amd64: python3-pyepics
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dioptas.html
    • 129 days old (needed 5 days)
• hddemux (- to 0.5-1)
  • Migration status for hddemux (- to 0.5-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
    • autopkgtest for hddemux/0.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: No test results
    • Build-Depends(-Arch): hddemux knot-resolver
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hddemux.html
    • 130 days old (needed 5 days)
• openvpn-auth-ldap (- to 2.0.4-2)
  • Migration status for openvpn-auth-ldap (- to 2.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openvpn-auth-ldap would introduce bugs in testing: #1001669
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvpn-auth-ldap.html
    • autopkgtest for openvpn-auth-ldap/2.0.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 131 days old (needed 5 days)
• osk-sdl (- to 0.66-4)
  • Migration status for osk-sdl (- to 0.66-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating osk-sdl would introduce bugs in testing: #1006642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osk-sdl.html
    • autopkgtest for osk-sdl/0.66-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 131 days old (needed 5 days)
• goxel (- to 0.10.8-1)
  • Migration status for goxel (- to 0.10.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating goxel would introduce bugs in testing: #984155
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goxel.html
    • 132 days old (needed 5 days)
• ruby-html-proofer (- to 3.19.2-4)
  • Migration status for ruby-html-proofer (- to 3.19.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-html-proofer would introduce bugs in testing: #1009384
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-html-proofer.html
    • autopkgtest for ruby-html-proofer/3.19.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 132 days old (needed 5 days)
• python-allpairspy (- to 2.5.0-1)
  • Migration status for python-allpairspy (- to 2.5.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-allpairspy.html
    • autopkgtest for python-allpairspy/2.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 134 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: Pass, arm64: Regression ♻ , armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-quote.html
    • 134 days old (needed 5 days)
• gcc-snapshot (- to 1:20220126-1)
  • Migration status for gcc-snapshot (- to 1:20220126-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-snapshot would introduce bugs in testing: #321449, #651291
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for gcc-snapshot/1:20220126-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
    • 136 days old (needed 5 days)
• jupyter-kernel-test (- to 0.4.3-1)
  • Migration status for jupyter-kernel-test (- to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jupyter-kernel-test/0.4.3-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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/j/jupyter-kernel-test.html
    • 136 days old (needed 5 days)
• python-fluids (- to 1.0.9-1)
  • Migration status for python-fluids (- to 1.0.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-fluids would introduce bugs in testing: #1004875, #1008451
    • autopkgtest for python-fluids/1.0.9-1: amd64: Pass, arm64: Regression ♻ (reference ♻), armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Build-Depends(-Arch): python-fluids numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fluids.html
    • 136 days old (needed 5 days)
• ruby-gitlab-license-finder (- to 6.14.2.1-2)
  • Migration status for ruby-gitlab-license-finder (- to 6.14.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-license-finder would introduce bugs in testing: #1004356, #1011445
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-license-finder.html
    • autopkgtest for ruby-gitlab-license-finder/6.14.2.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 138 days old (needed 5 days)
• python-flask-marshmallow (- to 0.14.0-1)
  • Migration status for python-flask-marshmallow (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-flask-marshmallow would introduce bugs in testing: #1002385
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flask-marshmallow.html
    • autopkgtest for python-flask-marshmallow/0.14.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 140 days old (needed 2 days)
• python-streamz (- to 0.6.3-2)
  • Migration status for python-streamz (- to 0.6.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-streamz would introduce bugs in testing: #1008452
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-streamz.html
    • autopkgtest for python-streamz/0.6.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 140 days old (needed 2 days)
• ruby-redis-activesupport (- to 5.3.0-1)
  • Migration status for ruby-redis-activesupport (- to 5.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): ruby-redis-activesupport ruby-redis-store (not considered)
    • Depends: ruby-redis-activesupport ruby-redis-store (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-activesupport.html
    • autopkgtest for ruby-redis-activesupport/5.3.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 140 days old (needed 2 days)
• quantlib-swig (- to 1.25-1)
  • Migration status for quantlib-swig (- to 1.25-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quantlib-swig.html
    • 141 days old (needed 5 days)
• scamper (- to 20211212-1)
  • Migration status for scamper (- to 20211212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scamper would introduce bugs in testing: #1010122
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on mipsel
    • missing build on ppc64el
    • 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: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/scamper.html
    • 141 days old (needed 5 days)
• golang-github-aquasecurity-go-dep-parser (- to 0.0~git20220110.4a30ebc-1)
  • Migration status for golang-github-aquasecurity-go-dep-parser (- to 0.0~git20220110.4a30ebc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-aquasecurity-go-dep-parser/0.0~git20220110.4a30ebc-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-aquasecurity-go-dep-parser.html
    • 143 days old (needed 5 days)
• mplayer (- to 2:1.4+ds1-3)
  • Migration status for mplayer (- to 2:1.4+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mplayer would introduce bugs in testing: #1005899
    • Depends: mplayer mplayer-blue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mplayer.html
    • 145 days old (needed 5 days)
• python-html-sanitizer (- to 1.9.3-1)
  • Migration status for python-html-sanitizer (- to 1.9.3-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/1.9.3-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 146 days old (needed 5 days)
• dvhtool (- to 1.0.1-6)
  • Migration status for dvhtool (- to 1.0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvhtool would introduce bugs in testing: #965501
    • autopkgtest for dvhtool/1.0.1-6: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvhtool.html
    • 148 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
    • 148 days old (needed 5 days)
• vdr-plugin-live (- to 3.1.3-2)
  • Migration status for vdr-plugin-live (- to 3.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vdr-plugin-live cxxtools (not considered)
    • Depends: vdr-plugin-live cxxtools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): vdr-plugin-live tntnet
    • Depends: vdr-plugin-live tntnet
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-live.html
    • 149 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 150 days old (needed 2 days)
• asmjit (- to 0.0~git20211214.2a706fd-1)
  • Migration status for asmjit (- to 0.0~git20211214.2a706fd-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asmjit.html
    • autopkgtest for asmjit/0.0~git20211214.2a706fd-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 152 days old (needed 2 days)
• python-cooler (- to 0.8.11-2)
  • Migration status for python-cooler (- to 0.8.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-cooler/0.8.11-2: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cooler.html
    • 152 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/mipsel has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/ppc64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/s390x has unsatisfiable dependency
    • 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 arm64: librust-heck-0.3+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 armhf: librust-heck-0.3+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 mips64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mipsel: librust-heck-0.3+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 s390x: librust-heck-0.3+default-dev
    • Build-Depends(-Arch): rust-wasm-bindgen-webidl rust-weedle
  • Additional info:
    • Piuparts tested OK - 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 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
    • 153 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-redis-redis.html
    • autopkgtest for golang-github-go-redis-redis/6.15.0-2: arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • autopkgtest for golang-github-go-redis-redis/blocked-on-ci-infra: amd64: Not a regression
    • 154 days old (needed 5 days)
• icingaweb2-module-reactbundle (- to 0.9.0-1)
  • Migration status for icingaweb2-module-reactbundle (- to 0.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-reactbundle icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-reactbundle.html
    • 156 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 mipsel 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
    • 156 days old (needed 5 days)
• golang-github-komkom-toml (- to 0.0~git20211215.3c8ee9d-1)
  • Migration status for golang-github-komkom-toml (- to 0.0~git20211215.3c8ee9d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-komkom-toml would introduce bugs in testing: #1004048
    • autopkgtest for golang-github-komkom-toml/0.0~git20211215.3c8ee9d-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-komkom-toml.html
    • 157 days old (needed 5 days)
• golang-github-likexian-gokit (- to 0.25.6-1)
  • Migration status for golang-github-likexian-gokit (- to 0.25.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-likexian-gokit would introduce bugs in testing: #995329
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-likexian-gokit.html
    • 157 days old (needed 5 days)
• icingaweb2-module-pdfexport (- to 0.9.1-2)
  • Migration status for icingaweb2-module-pdfexport (- to 0.9.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-pdfexport icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-pdfexport.html
    • 158 days old (needed 5 days)
• php-smbclient (- to 1.0.6-6)
  • Migration status for php-smbclient (- to 1.0.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-smbclient would introduce bugs in testing: #948075
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-smbclient.html
    • 158 days old (needed 5 days)
• bookletimposer (- to 0.3.1-1)
  • Migration status for bookletimposer (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bookletimposer would introduce bugs in testing: #1010820
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookletimposer.html
    • autopkgtest for bookletimposer/0.3.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 159 days old (needed 2 days)
• icingaweb2-module-incubator (- to 0.6.0-2)
  • Migration status for icingaweb2-module-incubator (- to 0.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-incubator icingaweb2 (not considered)
    • Invalidated by dependency
    • Depends: icingaweb2-module-incubator icingaweb2-module-ipl
    • Depends: icingaweb2-module-incubator icingaweb2-module-reactbundle
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-incubator.html
    • 159 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:
    • tiledarray unsatisfiable Build-Depends(-Arch) on amd64: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on arm64: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on armel: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on armhf: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on i386: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on mips64el: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on mipsel: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on ppc64el: libbtas-dev
    • tiledarray unsatisfiable Build-Depends(-Arch) on s390x: libbtas-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 mipsel
    • 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: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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 159 days old (needed 5 days)
• mlucas (- to 20.1.1-1)
  • Migration status for mlucas (- to 20.1.1-1): 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 i386
    • arch:arm64 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
    • 160 days old (needed 5 days)
• icingaweb2-module-businessprocess (- to 2.3.1-2)
  • Migration status for icingaweb2-module-businessprocess (- to 2.3.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-businessprocess icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-businessprocess.html
    • 163 days old (needed 5 days)
• icingaweb2-module-cube (- to 1.1.1-2)
  • Migration status for icingaweb2-module-cube (- to 1.1.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-cube icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-cube.html
    • 163 days old (needed 5 days)
• icingaweb2-module-eventdb (- to 1.3.0-3)
  • Migration status for icingaweb2-module-eventdb (- to 1.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-eventdb icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-eventdb.html
    • 163 days old (needed 5 days)
• icingaweb2-module-fileshipper (- to 1.2.0-2)
  • Migration status for icingaweb2-module-fileshipper (- to 1.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-fileshipper icingaweb2 (not considered)
    • Invalidated by dependency
    • Depends: icingaweb2-module-fileshipper icingaweb2-module-director
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-fileshipper.html
    • 163 days old (needed 5 days)
• icingaweb2-module-generictts (- to 2.0.0+20201009-2)
  • Migration status for icingaweb2-module-generictts (- to 2.0.0+20201009-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-generictts icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-generictts.html
    • 163 days old (needed 5 days)
• icingaweb2-module-graphite (- to 1.1.0-3)
  • Migration status for icingaweb2-module-graphite (- to 1.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-graphite icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-graphite.html
    • 163 days old (needed 5 days)
• icingaweb2-module-idoreports (- to 0.9.1-2)
  • Migration status for icingaweb2-module-idoreports (- to 0.9.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-idoreports icingaweb2 (not considered)
    • Invalidated by dependency
    • Depends: icingaweb2-module-idoreports icingaweb2-module-reporting
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-idoreports.html
    • 163 days old (needed 5 days)
• icingaweb2-module-map (- to 1.1.0-3)
  • Migration status for icingaweb2-module-map (- to 1.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-map icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-map.html
    • 163 days old (needed 5 days)
• icingaweb2-module-statusmap (- to 20160720-3)
  • Migration status for icingaweb2-module-statusmap (- to 20160720-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-statusmap icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-statusmap.html
    • 163 days old (needed 5 days)
• xtide (- to 2.15.2-1.1)
  • Migration status for xtide (- to 2.15.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): xtide tcd-utils (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtide.html
    • 163 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
    • 163 days old (needed 5 days)
• icingaweb2-module-audit (- to 1.0.1-2)
  • Migration status for icingaweb2-module-audit (- to 1.0.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-audit icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-audit.html
    • 164 days old (needed 5 days)
• icingaweb2-module-boxydash (- to 0.0.1+20160321-4)
  • Migration status for icingaweb2-module-boxydash (- to 0.0.1+20160321-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-boxydash icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-boxydash.html
    • 164 days old (needed 5 days)
• icingaweb2-module-director (- to 1.8.1-2)
  • Migration status for icingaweb2-module-director (- to 1.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-director icingaweb2 (not considered)
    • Invalidated by dependency
    • Depends: icingaweb2-module-director icingaweb2-module-incubator
    • Depends: icingaweb2-module-director icingaweb2-module-ipl
    • Depends: icingaweb2-module-director icingaweb2-module-reactbundle
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-director.html
    • 164 days old (needed 5 days)
• icingaweb2-module-nagvis (- to 1.1.1-3)
  • Migration status for icingaweb2-module-nagvis (- to 1.1.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-nagvis icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-nagvis.html
    • 164 days old (needed 5 days)
• icingaweb2-module-pnp (- to 1.1.0-3)
  • Migration status for icingaweb2-module-pnp (- to 1.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-pnp icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-pnp.html
    • 164 days old (needed 5 days)
• icingaweb2-module-reporting (- to 0.9.2+20200529-2)
  • Migration status for icingaweb2-module-reporting (- to 0.9.2+20200529-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-reporting icingaweb2 (not considered)
    • Invalidated by dependency
    • Depends: icingaweb2-module-reporting icingaweb2-module-ipl
    • Depends: icingaweb2-module-reporting icingaweb2-module-pdfexport
    • Depends: icingaweb2-module-reporting icingaweb2-module-reactbundle
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-reporting.html
    • 164 days old (needed 5 days)
• icingaweb2-module-toplevelview (- to 0.3.3-1)
  • Migration status for icingaweb2-module-toplevelview (- 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: icingaweb2-module-toplevelview icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-toplevelview.html
    • 164 days old (needed 5 days)
• icingaweb2-module-x509 (- to 20190125-3)
  • Migration status for icingaweb2-module-x509 (- to 20190125-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-x509 icingaweb2 (not considered)
    • Invalidated by dependency
    • Depends: icingaweb2-module-x509 icingaweb2-module-ipl
    • Depends: icingaweb2-module-x509 icingaweb2-module-reactbundle
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-x509.html
    • 164 days old (needed 5 days)
• opencolorio (- to 1.1.1~dfsg0-7.1)
  • Migration status for opencolorio (- to 1.1.1~dfsg0-7.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): opencolorio openimageio (not considered)
    • Depends: opencolorio openimageio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencolorio.html
    • 164 days old (needed 5 days)
• php-laravel-framework (- to 6.20.14+dfsg-3)
  • Migration status for php-laravel-framework (- to 6.20.14+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-illuminate-console/amd64 has unsatisfiable dependency
    • php-illuminate-cookie/amd64 has unsatisfiable dependency
    • php-illuminate-filesystem/amd64 has unsatisfiable dependency
    • php-illuminate-http/amd64 has unsatisfiable dependency
    • php-illuminate-queue/amd64 has unsatisfiable dependency
    • php-illuminate-routing/amd64 has unsatisfiable dependency
    • php-illuminate-session/amd64 has unsatisfiable dependency
    • php-illuminate-validation/amd64 has unsatisfiable dependency
    • php-laravel-framework/amd64 has unsatisfiable dependency
    • php-illuminate-console/arm64 has unsatisfiable dependency
    • php-illuminate-cookie/arm64 has unsatisfiable dependency
    • php-illuminate-filesystem/arm64 has unsatisfiable dependency
    • php-illuminate-http/arm64 has unsatisfiable dependency
    • php-illuminate-queue/arm64 has unsatisfiable dependency
    • php-illuminate-routing/arm64 has unsatisfiable dependency
    • php-illuminate-session/arm64 has unsatisfiable dependency
    • php-illuminate-validation/arm64 has unsatisfiable dependency
    • php-laravel-framework/arm64 has unsatisfiable dependency
    • Updating php-laravel-framework would introduce bugs in testing: #1000560
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/php-laravel-framework.html
    • Not built on buildd: arch all binaries uploaded by robin@rgson.se, a new source-only upload is needed to allow migration
    • Depends: php-laravel-framework symfony
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 164 days old (needed 5 days)
• lsp-plugins (- to 1.1.31-1)
  • Migration status for lsp-plugins (- to 1.1.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lsp-plugins would introduce bugs in testing: #1003904
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for lsp-plugins/1.1.31-1: amd64: No test results, arm64: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsp-plugins.html
    • 165 days old (needed 5 days)
• memtest86 (- to 4.3.7-4)
  • Migration status for memtest86 (- to 4.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating memtest86 would introduce bugs in testing: #540972, #563095
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/memtest86.html
    • 165 days old (needed 5 days)
• trace-summary (- to 0.92-1)
  • Migration status for trace-summary (- to 0.92-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: trace-summary pysubnettree (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trace-summary.html
    • 165 days old (needed 5 days)
• openmw (- to 0.47.0-1)
  • Migration status for openmw (- to 0.47.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openmw mygui (not considered)
    • Depends: openmw mygui (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmw.html
    • 166 days old (needed 5 days)
• q2-fragment-insertion (- to 2021.8.0-3)
  • Migration status for q2-fragment-insertion (- to 2021.8.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-fragment-insertion/2021.8.0-3: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by moeller, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-fragment-insertion.html
    • 167 days old (needed 5 days)
• sslsplit (- to 0.5.5-2)
  • Migration status for sslsplit (- to 0.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sslsplit would introduce bugs in testing: #1007962
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sslsplit.html
    • 167 days old (needed 5 days)
• opentsne (- to 0.6.1-2)
  • Migration status for opentsne (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opentsne would introduce bugs in testing: #1004706, #1008996
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for opentsne/0.6.1-2: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentsne.html
    • 171 days old (needed 5 days)
• lomiri-app-launch (- to 0.1.1-1)
  • Migration status for lomiri-app-launch (- to 0.1.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-app-launch click (not considered)
    • Depends: lomiri-app-launch click (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-app-launch.html
    • 173 days old (needed 5 days)
• renpy (- to 7.3.5+dfsg-2)
  • Migration status for renpy (- to 7.3.5+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating renpy would introduce bugs in testing: #1006540, #938351
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/renpy.html
  • Additional info:
    • 174 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
    • 175 days old (needed 5 days)
• rinutils (- to 0.10.0-1)
  • Migration status for rinutils (- 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 bastian.germann@linutronix.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rinutils.html
    • 175 days old (needed 5 days)
• weex (- to 2.8.4.1)
  • Migration status for weex (- to 2.8.4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating weex would introduce bugs in testing: #965875
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/weex.html
    • 175 days old (needed 5 days)
• liboqs (- to 0.7.1-1)
  • Migration status for liboqs (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liboqs would introduce bugs in testing: #1000303
    • Depends: liboqs openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboqs.html
    • 176 days old (needed 5 days)
• mygui (- to 3.4.1+dfsg-1)
  • Migration status for mygui (- to 3.4.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mygui unsatisfiable Build-Depends(-Arch) on mipsel: libogre-1.12-dev
    • Not built on buildd: arch all binaries uploaded by bastian.germann@linutronix.de, a new source-only upload is needed to allow migration
    • Not built on buildd: arch i386 binaries uploaded by bastian.germann@linutronix.de
    • missing build on mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mygui.html
    • 177 days old (needed 5 days)
• libmath-matrix-maybegsl-perl (- to 0.007-2)
  • Migration status for libmath-matrix-maybegsl-perl (- to 0.007-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libmath-matrix-maybegsl-perl/0.007-2: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmath-matrix-maybegsl-perl.html
    • 179 days old (needed 5 days)
• mate-media (- to 1.26.0-1)
  • Migration status for mate-media (- to 1.26.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mate-media would introduce bugs in testing: #971783
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-media.html
    • 179 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
    • 179 days old (needed 5 days)
• qmc (- to 0.94-4)
  • Migration status for qmc (- to 0.94-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qmc would introduce bugs in testing: #668644
    • Build-Depends(-Arch): qmc dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qmc.html
    • 179 days old (needed 5 days)
• salmon (- to 1.6.0+ds1-1)
  • Migration status for salmon (- to 1.6.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating salmon would introduce bugs in testing: #1008252
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/salmon.html
    • 179 days old (needed 5 days)
• ruby-riddle (- to 2.4.2-1)
  • Migration status for ruby-riddle (- to 2.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-riddle/2.4.2-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ (reference ♻), ppc64el: Pass, s390x: Not a regression
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-riddle.html
    • 180 days old (needed 5 days)
• ruby2.7 (- to 2.7.5-1)
  • Migration status for ruby2.7 (- to 2.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby2.7 would introduce bugs in testing: #1005643
    • autopkgtest for ruby2.7/2.7.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Regression ♻ (reference ♻)
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby2.7.html
    • 180 days old (needed 5 days)
• giara (- to 0.3-3)
  • Migration status for giara (- to 0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating giara would introduce bugs in testing: #1003570
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giara.html
    • autopkgtest for giara/0.3-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 181 days old (needed 5 days)
• ruby-ipynbdiff (- to 0.3.8-2)
  • Migration status for ruby-ipynbdiff (- to 0.3.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-ipynbdiff/0.3.8-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ipynbdiff.html
    • 181 days old (needed 5 days)
• lomiri-ui-toolkit (- to 1.3.3000+dfsg-5)
  • Migration status for lomiri-ui-toolkit (- to 1.3.3000+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lomiri-ui-toolkit would introduce bugs in testing: #1009444
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-ui-toolkit.html
    • 183 days old (needed 5 days)
• php-horde-compress (- to 2.2.4-1)
  • Migration status for php-horde-compress (- to 2.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-compress would introduce bugs in testing: #1003652
    • autopkgtest for php-horde-compress/2.2.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-compress.html
    • 183 days old (needed 5 days)
• ruby-omniauth-openid-connect (- to 0.8.0-2)
  • Migration status for ruby-omniauth-openid-connect (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-openid-connect would introduce bugs in testing: #999721
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-openid-connect.html
    • autopkgtest for ruby-omniauth-openid-connect/0.8.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 183 days old (needed 2 days)
• rainloop (- to 1.16.0+dfsg-1)
  • Migration status for rainloop (- to 1.16.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rainloop would introduce bugs in testing: #1001632, #1006060
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rainloop.html
    • 184 days old (needed 5 days)
• ruby-jekyll-commonmark (- to 1.3.1-6)
  • Migration status for ruby-jekyll-commonmark (- to 1.3.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-commonmark jekyll (not considered)
    • Depends: ruby-jekyll-commonmark jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-commonmark.html
    • autopkgtest for ruby-jekyll-commonmark/1.3.1-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 184 days old (needed 2 days)
• ruby-jquery-atwho-rails (- to 1.5.4+dfsg-2)
  • Migration status for ruby-jquery-atwho-rails (- to 1.5.4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jquery-atwho-rails would introduce bugs in testing: #1008468
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jquery-atwho-rails.html
    • autopkgtest for ruby-jquery-atwho-rails/1.5.4+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 185 days old (needed 2 days)
• ruby-psych (- to 3.3.2-1)
  • Migration status for ruby-psych (- to 3.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-psych would introduce bugs in testing: #1008697
    • autopkgtest for ruby-psych/3.3.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
    • Build-Depends(-Arch): ruby-psych jruby
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-psych.html
    • 185 days old (needed 5 days)
• ruby-rufus-scheduler (- to 3.8.0-2)
  • Migration status for ruby-rufus-scheduler (- to 3.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rufus-scheduler would introduce bugs in testing: #1002083
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rufus-scheduler.html
    • autopkgtest for ruby-rufus-scheduler/3.8.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 185 days old (needed 2 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
    • 186 days old (needed 5 days)
• luakit (- to 1:2.3-1)
  • Migration status for luakit (- to 1:2.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): luakit luajit (not considered)
    • Invalidated by build-dependency
    • Depends: luakit luajit2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/luakit.html
    • 186 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Depends: epigrass python-epimodels
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epigrass.html
    • 187 days old (needed 5 days)
• gnome-shell-extension-draw-on-your-screen (- to 11-2)
  • Migration status for gnome-shell-extension-draw-on-your-screen (- to 11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-draw-on-your-screen/amd64 has unsatisfiable dependency
    • gnome-shell-extension-draw-on-your-screen/arm64 has unsatisfiable dependency
    • Updating gnome-shell-extension-draw-on-your-screen would introduce bugs in testing: #1008544
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-draw-on-your-screen.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 187 days old (needed 5 days)
• roundcube (- to 1.5.1+dfsg-1)
  • Migration status for roundcube (- to 1.5.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating roundcube would introduce bugs in testing: #1000642, #1003027
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/roundcube.html
    • autopkgtest for roundcube/1.5.1+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 188 days old (needed 5 days)
• gosa-plugin-netgroups (- to 0.2-3)
  • Migration status for gosa-plugin-netgroups (- to 0.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugin-netgroups gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugin-netgroups.html
    • 189 days old (needed 5 days)
• gosa-plugin-pwreset (- to 0.99.5-4)
  • Migration status for gosa-plugin-pwreset (- to 0.99.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugin-pwreset gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugin-pwreset.html
    • 189 days old (needed 5 days)
• khmer (- to 2.1.2+dfsg-10)
  • Migration status for khmer (- to 2.1.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating khmer would introduce bugs in testing: #1008402
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khmer.html
    • autopkgtest for khmer/2.1.2+dfsg-10: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 189 days old (needed 5 days)
• python-onewire (- to 0.2-2)
  • Migration status for python-onewire (- to 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): python-onewire owfs (not considered)
    • Depends: python-onewire owfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-onewire.html
    • autopkgtest for python-onewire/0.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 189 days old (needed 5 days)
• scm (- to 5f3-1)
  • Migration status for scm (- to 5f3-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 mipsel
    • arch:armhf not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): scm slib
    • Depends: scm slib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scm.html
    • 190 days old (needed 5 days)
• jacal (- to 1c7-3)
  • Migration status for jacal (- to 1c7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jacal scm (not considered)
    • Invalidated by dependency
    • Depends: jacal slib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jacal.html
    • 192 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: #1009173, #950372
    • Build-Depends(-Arch): radare2 freebsd-glue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2.html
    • 192 days old (needed 5 days)
• ruby-active-model-serializers (- to 0.10.12-1)
  • Migration status for ruby-active-model-serializers (- to 0.10.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-active-model-serializers ruby-grape (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-active-model-serializers.html
    • autopkgtest for ruby-active-model-serializers/0.10.12-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 192 days old (needed 2 days)
• rust-elfx86exts (- to 0.3.0-5)
  • Migration status for rust-elfx86exts (- to 0.3.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-elfx86exts unsatisfiable Build-Depends(-Arch) on armel: librust-capstone-0+default-dev
    • missing build on armel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-elfx86exts.html
    • 192 days old (needed 5 days)
• grub-efi-amd64-signed (1+2.04+20 to 1+2.06+2)
  • Migration status for grub-efi-amd64-signed (1+2.04+20 to 1+2.06+2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grub-efi-amd64-signed unsatisfiable Build-Depends(-Arch) on amd64: grub-efi-amd64-bin (= 2.06-2)
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Built-Using: grub-efi-amd64-signed grub2
    • Depends: grub-efi-amd64-signed grub2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub-efi-amd64-signed.html
    • 193 days old (needed 5 days)
• grub-efi-arm64-signed (1+2.04+20 to 1+2.06+2)
  • Migration status for grub-efi-arm64-signed (1+2.04+20 to 1+2.06+2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grub-efi-arm64-signed unsatisfiable Build-Depends(-Arch) on arm64: grub-efi-arm64-bin (= 2.06-2)
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Built-Using: grub-efi-arm64-signed grub2
    • Depends: grub-efi-arm64-signed grub2
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 193 days old (needed 5 days)
• grub-efi-ia32-signed (1+2.04+20 to 1+2.06+2)
  • Migration status for grub-efi-ia32-signed (1+2.04+20 to 1+2.06+2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grub-efi-ia32-signed unsatisfiable Build-Depends(-Arch) on i386: grub-efi-ia32-bin (= 2.06-2)
    • Not built on buildd: upload info for arch i386 binaries not found
    • Built-Using: grub-efi-ia32-signed grub2
    • Depends: grub-efi-ia32-signed grub2
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 193 days old (needed 5 days)
• ruby-handlebars-assets (- to 2:0.23.8+dfsg-4)
  • Migration status for ruby-handlebars-assets (- to 2:0.23.8+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-handlebars-assets would introduce bugs in testing: #1005631
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-handlebars-assets.html
    • autopkgtest for ruby-handlebars-assets/2:0.23.8+dfsg-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 193 days old (needed 2 days)
• ruby-rails-assets-jquery-fullscreen-plugin (- to 0.5.0+dfsg-5)
  • Migration status for ruby-rails-assets-jquery-fullscreen-plugin (- to 0.5.0+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-jquery-fullscreen-plugin would introduce bugs in testing: #979955
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jquery-fullscreen-plugin.html
    • autopkgtest for ruby-rails-assets-jquery-fullscreen-plugin/0.5.0+dfsg-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 193 days old (needed 2 days)
• matrix-sydent (- to 2.5.1-1)
  • Migration status for matrix-sydent (- to 2.5.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/m/matrix-sydent.html
  • Additional info:
    • autopkgtest for matrix-sydent/2.5.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 194 days old (needed 5 days)
• ruby-leaflet-rails (- to 1.6.0+dfsg-2)
  • Migration status for ruby-leaflet-rails (- to 1.6.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-leaflet-rails would introduce bugs in testing: #1005634
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-leaflet-rails.html
    • autopkgtest for ruby-leaflet-rails/1.6.0+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 194 days old (needed 2 days)
• libhttp-tiny-perl (- to 0.080-1)
  • Migration status for libhttp-tiny-perl (- to 0.080-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libhttp-tiny-perl would introduce bugs in testing: #961283
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhttp-tiny-perl.html
    • autopkgtest for libhttp-tiny-perl/0.080-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 195 days old (needed 2 days)
• lintian (2.111.0 to 2.114.0)
  • Migration status for lintian (2.111.0 to 2.114.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lintian would introduce bugs in testing: #1003272, #999768
  • Additional info:
    • Updating lintian will fix bugs in testing: #1003643
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian.html
    • autopkgtest for lintian/2.114.0: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 195 days old (needed 5 days)
• rust-zram-generator (- to 0.3.2-1)
  • Migration status for rust-zram-generator (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rust-zram-generator.html
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on amd64: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on arm64: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on armel: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on armhf: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on i386: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on mips64el: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on mipsel: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • rust-zram-generator unsatisfiable Build-Depends(-Arch) on s390x: librust-rust-ini-0.16+default-dev | librust-rust-ini-0.15+default-dev | librust-rust-ini-0.14+default-dev | librust-rust-ini-0.13+default-dev
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
  • Additional info:
    • autopkgtest for rust-zram-generator/0.3.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 195 days old (needed 5 days)
• golang-github-go-enry-go-license-detector (- to 4.3.0-3)
  • Migration status for golang-github-go-enry-go-license-detector (- to 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): golang-github-go-enry-go-license-detector golang-github-hhatto-gorst (not considered)
    • Built-Using: golang-github-go-enry-go-license-detector golang-github-hhatto-gorst (not considered)
    • Depends: golang-github-go-enry-go-license-detector golang-github-hhatto-gorst (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
    • Build-Depends(-Arch): golang-github-go-enry-go-license-detector golang-gonum-v1-gonum
    • Built-Using: golang-github-go-enry-go-license-detector golang-gonum-v1-gonum
    • Depends: golang-github-go-enry-go-license-detector golang-gonum-v1-gonum
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-enry-go-license-detector.html
    • autopkgtest for golang-github-go-enry-go-license-detector/4.3.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 196 days old (needed 2 days)
• perfect-scrollbar (- to 1.5.2+ds-1)
  • Migration status for perfect-scrollbar (- to 1.5.2+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/perfect-scrollbar.html
    • 196 days old (needed 5 days)
• php-mysqlnd-ms (- to 1.6.0+svn333622-12)
  • Migration status for php-mysqlnd-ms (- to 1.6.0+svn333622-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-mysqlnd-ms/amd64 has unsatisfiable dependency
    • php-mysqlnd-ms/arm64 has unsatisfiable dependency
    • php-mysqlnd-ms/armel has unsatisfiable dependency
    • php-mysqlnd-ms/armhf has unsatisfiable dependency
    • php-mysqlnd-ms/i386 has unsatisfiable dependency
    • php-mysqlnd-ms/mips64el has unsatisfiable dependency
    • php-mysqlnd-ms/mipsel has unsatisfiable dependency
    • php-mysqlnd-ms/ppc64el has unsatisfiable dependency
    • php-mysqlnd-ms/s390x has unsatisfiable dependency
    • Not built on buildd: arch amd64 binaries uploaded by ondrej
    • Not built on buildd: arch all binaries uploaded by ondrej, 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/p/php-mysqlnd-ms.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
    • 196 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, #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 mipsel
    • missing build on ppc64el
    • 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:
    • 197 days old (needed 5 days)
• origami-pdf (- to 2.0.4+dfsg-1)
  • Migration status for origami-pdf (- to 2.0.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating origami-pdf would introduce bugs in testing: #911735
    • autopkgtest for origami-pdf/2.0.4+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/origami-pdf.html
    • 197 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 197 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 197 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 197 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: #996847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysrepo.html
    • 197 days old (needed 5 days)
• libobject-pad-slotattr-final-perl (- to 0.04-2)
  • Migration status for libobject-pad-slotattr-final-perl (- to 0.04-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libobject-pad-slotattr-final-perl would introduce bugs in testing: #1005016
    • autopkgtest for libobject-pad-slotattr-final-perl/0.04-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobject-pad-slotattr-final-perl.html
    • 198 days old (needed 5 days)
• libobject-pad-slotattr-isa-perl (- to 0.02-2)
  • Migration status for libobject-pad-slotattr-isa-perl (- to 0.02-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libobject-pad-slotattr-isa-perl would introduce bugs in testing: #1005245
    • autopkgtest for libobject-pad-slotattr-isa-perl/0.02-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobject-pad-slotattr-isa-perl.html
    • 198 days old (needed 5 days)
• libobject-pad-slotattr-lazyinit-perl (- to 0.04-2)
  • Migration status for libobject-pad-slotattr-lazyinit-perl (- to 0.04-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libobject-pad-slotattr-lazyinit-perl would introduce bugs in testing: #1005246
    • autopkgtest for libobject-pad-slotattr-lazyinit-perl/0.04-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobject-pad-slotattr-lazyinit-perl.html
    • 198 days old (needed 5 days)
• libobject-pad-slotattr-trigger-perl (- to 0.05-2)
  • Migration status for libobject-pad-slotattr-trigger-perl (- to 0.05-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libobject-pad-slotattr-trigger-perl would introduce bugs in testing: #1005247
    • autopkgtest for libobject-pad-slotattr-trigger-perl/0.05-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobject-pad-slotattr-trigger-perl.html
    • 198 days old (needed 5 days)
• libusermetrics (- to 1.2.0-2)
  • Migration status for libusermetrics (- to 1.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): libusermetrics click (not considered)
    • Depends: libusermetrics click (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libusermetrics.html
    • 200 days old (needed 5 days)
• libcrypt-openssl-pkcs12-perl (- to 1.9-1)
  • Migration status for libcrypt-openssl-pkcs12-perl (- to 1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcrypt-openssl-pkcs12-perl would introduce bugs in testing: #1006386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcrypt-openssl-pkcs12-perl.html
    • autopkgtest for libcrypt-openssl-pkcs12-perl/1.9-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 201 days old (needed 2 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
    • 201 days old (needed 5 days)
• ruby-fog-google (- to 1.15.0-2)
  • Migration status for ruby-fog-google (- to 1.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-fog-google ruby-google-api-client (not considered)
    • Depends: ruby-fog-google ruby-google-api-client (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fog-google.html
    • autopkgtest for ruby-fog-google/1.15.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 201 days old (needed 5 days)
• pinta (- to 1.6-2.1)
  • Migration status for pinta (- to 1.6-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pinta would introduce bugs in testing: #877106
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pinta.html
    • 202 days old (needed 5 days)
• ruby-api-pagination (- to 4.8.2-2)
  • Migration status for ruby-api-pagination (- to 4.8.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-api-pagination ruby-grape (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-api-pagination.html
    • autopkgtest for ruby-api-pagination/4.8.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 202 days old (needed 2 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
    • Build-Depends(-Arch): jquery-datetimepicker libjs-php-date-formatter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-datetimepicker.html
    • 203 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
    • 203 days old (needed 5 days)
• kotlin (- to 1.3.31+~1.0.1+~0.11.12-2)
  • Migration status for kotlin (- to 1.3.31+~1.0.1+~0.11.12-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kotlin android-platform-tools-base (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): kotlin intellij-community-idea
    • Build-Depends(-Arch): kotlin openjdk-8
    • Build-Depends(-Arch): kotlin protobuf2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlin.html
    • 203 days old (needed 5 days)
• libjs-php-date-formatter (- to 1.3.6+ds-1)
  • Migration status for libjs-php-date-formatter (- to 1.3.6+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/libj/libjs-php-date-formatter.html
    • 203 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
    • 203 days old (needed 5 days)
• sortablejs (- to 1.14.0+ds-1)
  • Migration status for sortablejs (- to 1.14.0+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/s/sortablejs.html
    • 203 days old (needed 5 days)
• time-decode (- to 3.2.0-1)
  • Migration status for time-decode (- 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 samueloph, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/time-decode.html
    • autopkgtest for time-decode/3.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 203 days old (needed 2 days)
• golang-github-hhatto-gorst (- to 0.0~git20181029.ca9f730-2)
  • Migration status for golang-github-hhatto-gorst (- to 0.0~git20181029.ca9f730-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-hhatto-gorst/0.0~git20181029.ca9f730-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hhatto-gorst.html
    • 204 days old (needed 5 days)
• ruby-gitlab-fog-azure-rm (- to 1.2.0-1)
  • Migration status for ruby-gitlab-fog-azure-rm (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-fog-azure-rm would introduce bugs in testing: #996235
    • autopkgtest for ruby-gitlab-fog-azure-rm/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • 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-gitlab-fog-azure-rm.html
    • 204 days old (needed 5 days)
• sphde (- to 1.4.0-3)
  • Migration status for sphde (- to 1.4.0-3): 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
    • missing build on mipsel
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphde.html
    • 204 days old (needed 5 days)
• taurus (- to 5.0.0-1)
  • Migration status for taurus (- to 5.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): taurus guiqwt (not considered)
    • Depends: taurus guiqwt (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taurus.html
    • 205 days old (needed 5 days)
• taurus-pyqtgraph (- to 0.5.9-1)
  • Migration status for taurus-pyqtgraph (- to 0.5.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): taurus-pyqtgraph taurus (not considered)
    • Depends: taurus-pyqtgraph taurus (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taurus-pyqtgraph.html
    • 205 days old (needed 5 days)
• xmms2 (- to 0.8+dfsg-22)
  • Migration status for xmms2 (- to 0.8+dfsg-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmms2 would introduce bugs in testing: #1005902
    • Depends: xmms2 openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2.html
    • 205 days old (needed 5 days)
• celery-haystack-ng (- to 0.20.post2-1)
  • Migration status for celery-haystack-ng (- to 0.20.post2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating celery-haystack-ng would introduce bugs in testing: #999908
    • 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/c/celery-haystack-ng.html
    • 206 days old (needed 5 days)
• celery-progress (- to 0.1.1-1)
  • Migration status for celery-progress (- to 0.1.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/c/celery-progress.html
    • 206 days old (needed 5 days)
• lxmusic (- to 0.4.7-1.1)
  • Migration status for lxmusic (- to 0.4.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): lxmusic xmms2 (not considered)
    • Depends: lxmusic xmms2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxmusic.html
    • 206 days old (needed 5 days)
• q2-diversity-lib (- to 2021.8.0-1)
  • Migration status for q2-diversity-lib (- to 2021.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-diversity-lib/2021.8.0-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 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/q/q2-diversity-lib.html
    • 206 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): node-solid-keychain node-trust-webcrypto (not considered)
    • Depends: node-solid-keychain node-trust-webcrypto (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-solid-keychain.html
    • autopkgtest for node-solid-keychain/0.1.3-3.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 207 days old (needed 2 days)
• trinityrnaseq (- to 2.13.2+dfsg-3)
  • Migration status for trinityrnaseq (- to 2.13.2+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trinityrnaseq would introduce bugs in testing: #1006336
    • Build-Depends(-Arch): trinityrnaseq salmon
    • Depends: trinityrnaseq salmon
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trinityrnaseq.html
    • autopkgtest for trinityrnaseq/2.13.2+dfsg-3: amd64: Ignored failure, arm64: Ignored failure, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 207 days old (needed 5 days)
• hiera-eyaml (- to 3.2.2-2)
  • Migration status for hiera-eyaml (- to 3.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hiera-eyaml would introduce bugs in testing: #1005758
    • autopkgtest for hiera-eyaml/3.2.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hiera-eyaml.html
    • 208 days old (needed 5 days)
• lomiri-download-manager (- to 0.1.0-9)
  • Migration status for lomiri-download-manager (- to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-download-manager libnih (not considered)
    • Depends: lomiri-download-manager libnih (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-download-manager.html
    • 208 days old (needed 5 days)
• frr (- to 8.1-1)
  • Migration status for frr (- to 8.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frr.html
    • autopkgtest for frr/8.1-1: 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)
• pysubnettree (- to 0.35-1)
  • Migration status for pysubnettree (- to 0.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pysubnettree would introduce bugs in testing: #1005044
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysubnettree.html
    • 209 days old (needed 5 days)
• seqan3 (- to 3.1.0+ds-1)
  • Migration status for seqan3 (- to 3.1.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating seqan3 would introduce bugs in testing: #1008352
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seqan3.html
    • autopkgtest for seqan3/3.1.0+ds-1: amd64: Pass, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 211 days old (needed 5 days)
• ruby-jekyll-data (- to 1.1.1-2)
  • Migration status for ruby-jekyll-data (- to 1.1.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-data jekyll (not considered)
    • Depends: ruby-jekyll-data jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-data.html
    • autopkgtest for ruby-jekyll-data/1.1.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 212 days old (needed 2 days)
• libcamera (- to 0~git20211108+1b30992b623e-3)
  • Migration status for libcamera (- to 0~git20211108+1b30992b623e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcamera would introduce bugs in testing: #962650
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcamera.html
    • 213 days old (needed 5 days)
• node-jsonld (- to 4.0.1-1)
  • Migration status for node-jsonld (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-jsonld would introduce bugs in testing: #1003502, #958682
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-jsonld.html
    • autopkgtest for node-jsonld/4.0.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 214 days old (needed 5 days)
• ruby-jekyll-remote-theme (- to 0.4.3-2)
  • Migration status for ruby-jekyll-remote-theme (- to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-remote-theme jekyll (not considered)
    • Depends: ruby-jekyll-remote-theme jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-feed
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-github-metadata
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-sass-converter
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-seo-tag
    • Build-Depends(-Arch): ruby-jekyll-remote-theme ruby-jekyll-sitemap
    • Depends: ruby-jekyll-remote-theme ruby-jekyll-sass-converter
  • 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-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 214 days old (needed 2 days)
• glib-d (- to 2.3.0-2)
  • Migration status for glib-d (- to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glib-d would introduce bugs in testing: #1008403
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glib-d.html
    • 215 days old (needed 5 days)
• tpm2-tss-engine (- to 1.1.0-2)
  • Migration status for tpm2-tss-engine (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpm2-tss-engine would introduce bugs in testing: #1006585
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-tss-engine.html
    • 215 days old (needed 5 days)
• q2-phylogeny (- to 2021.4.0-2)
  • Migration status for q2-phylogeny (- to 2021.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • q2-phylogeny/arm64 has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-phylogeny.html
    • uninstallable on arch arm64, not running autopkgtest there
    • autopkgtest for q2-phylogeny/2021.4.0-2: amd64: Pass, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 216 days old (needed 5 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 ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-intel-go-cpuid.html
    • 217 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
    • 217 days old (needed 5 days)
• mstflint (- to 4.17.0+1-1)
  • Migration status for mstflint (- to 4.17.0+1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Depends: mstflint openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mstflint.html
    • 217 days old (needed 5 days)
• organize (- to 1.10.1-1)
  • Migration status for organize (- 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 frediz@linux.vnet.ibm.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): organize simplematch
    • Depends: organize simplematch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/organize.html
    • 217 days old (needed 5 days)
• python-beziers (- to 0.3.1+dfsg1-1)
  • Migration status for python-beziers (- to 0.3.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mwei@lxde.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-beziers.html
    • autopkgtest for python-beziers/0.3.1+dfsg1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 217 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
    • 217 days old (needed 5 days)
• ruby-axiom-types (- to 0.1.1-2)
  • Migration status for ruby-axiom-types (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-axiom-types would introduce bugs in testing: #1006026
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-axiom-types.html
    • autopkgtest for ruby-axiom-types/0.1.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 218 days old (needed 2 days)
• python-cogent (- to 2021.10.12a1+dfsg-1)
  • Migration status for python-cogent (- to 2021.10.12a1+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-cogent jupyter-sphinx (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): python-cogent numba
    • Build-Depends(-Arch): python-cogent tinydb
    • Depends: python-cogent tinydb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cogent.html
    • autopkgtest for python-cogent/2021.10.12a1+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 219 days old (needed 5 days)
• django-any-js (- to 1.1-1)
  • Migration status for django-any-js (- to 1.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/d/django-any-js.html
    • 220 days old (needed 5 days)
• django-bleach (- to 0.9.0-1)
  • Migration status for django-bleach (- 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 natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-bleach.html
    • 220 days old (needed 5 days)
• django-cachalot (- to 2.4.3-1)
  • Migration status for django-cachalot (- to 2.4.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-cachalot.html
    • 220 days old (needed 5 days)
• django-celery-email (- to 3.0.0-1)
  • Migration status for django-celery-email (- to 3.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/d/django-celery-email.html
    • 220 days old (needed 5 days)
• django-ckeditor (- to 6.1.0+ds-1)
  • Migration status for django-ckeditor (- to 6.1.0+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/d/django-ckeditor.html
    • 220 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
    • 220 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
    • 220 days old (needed 5 days)
• django-maintenance-mode (- to 0.16.1-1)
  • Migration status for django-maintenance-mode (- to 0.16.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/d/django-maintenance-mode.html
    • 220 days old (needed 5 days)
• django-menu-generator-ng (- to 1.2.3-1)
  • Migration status for django-menu-generator-ng (- to 1.2.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-menu-generator-ng.html
    • 220 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
    • Build-Depends(-Arch): django-otp-yubikey python-yubiotp
    • Depends: django-otp-yubikey python-yubiotp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-otp-yubikey.html
    • 220 days old (needed 5 days)
• django-phonenumber-field (- to 5.2.0-1)
  • Migration status for django-phonenumber-field (- to 5.2.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-phonenumber-field.html
    • 220 days old (needed 5 days)
• django-render-block (- to 0.8.1-1)
  • Migration status for django-render-block (- to 0.8.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/d/django-render-block.html
    • 220 days old (needed 5 days)
• django-select2 (- to 7.7.2-1)
  • Migration status for django-select2 (- to 7.7.2-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-select2.html
    • 220 days old (needed 5 days)
• django-templated-email (- to 3.0.0-1)
  • Migration status for django-templated-email (- to 3.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
    • Build-Depends(-Arch): django-templated-email django-render-block
    • Depends: django-templated-email django-render-block
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-templated-email.html
    • 220 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
    • 220 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
    • 220 days old (needed 5 days)
• ruby-activerecord-precounter (- to 0.4.0-1)
  • Migration status for ruby-activerecord-precounter (- to 0.4.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-activerecord-precounter.html
    • autopkgtest for ruby-activerecord-precounter/0.4.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 221 days old (needed 5 days)
• ruby-uc.micro-rb (- to 1.0.5-1)
  • Migration status for ruby-uc.micro-rb (- to 1.0.5-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-uc.micro-rb.html
    • autopkgtest for ruby-uc.micro-rb/1.0.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 221 days old (needed 2 days)
• gnome-authenticator (- to 3.32.2+dfsg1-4)
  • Migration status for gnome-authenticator (- to 3.32.2+dfsg1-4): 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-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 222 days old (needed 5 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:
    • Piuparts tested OK - 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
    • 223 days old (needed 5 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 225 days old (needed 2 days)
• armnn (- to 20.08-10)
  • Migration status for armnn (- to 20.08-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyarmnn/amd64 has unsatisfiable dependency
    • python3-pyarmnn/arm64 has unsatisfiable dependency
    • python3-pyarmnn/i386 has unsatisfiable dependency
    • python3-pyarmnn/mips64el has unsatisfiable dependency
    • python3-pyarmnn/mipsel has unsatisfiable dependency
    • python3-pyarmnn/ppc64el has unsatisfiable dependency
    • Updating armnn would introduce bugs in testing: #998043
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/armnn.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
    • 226 days old (needed 5 days)
• numba (- to 0.52.0-5)
  • Migration status for numba (- to 0.52.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-numba/amd64 has unsatisfiable dependency
    • python3-numba/arm64 has unsatisfiable dependency
    • python3-numba/armel has unsatisfiable dependency
    • python3-numba/armhf has unsatisfiable dependency
    • python3-numba/i386 has unsatisfiable dependency
    • python3-numba/mips64el has unsatisfiable dependency
    • python3-numba/mipsel has unsatisfiable dependency
    • python3-numba/ppc64el has unsatisfiable dependency
    • python3-numba/s390x has unsatisfiable dependency
    • Updating numba would introduce bugs in testing: #1000336
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/numba.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
    • 226 days old (needed 5 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
    • 226 days old (needed 5 days)
• rgain3 (- to 1.1.1-3)
  • Migration status for rgain3 (- to 1.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rgain3 would introduce bugs in testing: #968186
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rgain3.html
    • autopkgtest for rgain3/1.1.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 226 days old (needed 2 days)
• ruby-stackprof (- to 0.2.17-1)
  • Migration status for ruby-stackprof (- to 0.2.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-stackprof would introduce bugs in testing: #994456
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-stackprof.html
    • autopkgtest for ruby-stackprof/0.2.17-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 226 days old (needed 2 days)
• timew (- to 1.4.3+ds.1-1)
  • Migration status for timew (- to 1.4.3+ds.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating timew would introduce bugs in testing: #1001668
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/timew.html
    • autopkgtest for timew/1.4.3+ds.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 226 days old (needed 2 days)
• ruby-grape-path-helpers (- to 1.7.0-1)
  • Migration status for ruby-grape-path-helpers (- to 1.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): ruby-grape-path-helpers ruby-grape (not considered)
    • Depends: ruby-grape-path-helpers ruby-grape (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape-path-helpers.html
    • autopkgtest for ruby-grape-path-helpers/1.7.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• geany-plugins (- to 1.38+dfsg-1)
  • Migration status for geany-plugins (- to 1.38+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): geany-plugins ctpl (not considered)
    • Depends: geany-plugins ctpl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geany-plugins.html
    • 228 days old (needed 5 days)
• fenicsx-performance-tests (- to 0.0~git20210901.25e932a-1)
  • Migration status for fenicsx-performance-tests (- to 0.0~git20210901.25e932a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fenicsx-performance-tests/0.0~git20210901.25e932a-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • Impossible Depends: fenicsx-performance-tests -> libpetsc-real3.15/3.15.5+dfsg1-1+b2/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenicsx-performance-tests.html
    • 229 days old (needed 5 days)
• xdg-utils-cxx (- to 1.0.1-3)
  • Migration status for xdg-utils-cxx (- to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xdg-utils-cxx would introduce bugs in testing: #1004109
    • Not built on buildd: arch amd64 binaries uploaded by peb@pimeys.fr
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on mipsel
    • missing build on ppc64el
    • missing build on s390x
    • 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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdg-utils-cxx.html
    • 230 days old (needed 5 days)
• calcurse (- to 4.7.1-1)
  • Migration status for calcurse (- to 4.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calcurse would introduce bugs in testing: #1004103
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calcurse.html
    • 232 days old (needed 5 days)
• dvbstreamer (- to 2.1.0-5.4)
  • Migration status for dvbstreamer (- to 2.1.0-5.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvbstreamer would introduce bugs in testing: #965504
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvbstreamer.html
    • 238 days old (needed 5 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
    • 239 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:
    • autopkgtest for prads/0.3.3-7: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • 239 days old (needed 5 days)
• jtreg6 (- to 6+1-1)
  • Migration status for jtreg6 (- to 6+1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/j/jtreg6.html
    • Not built on buildd: arch all binaries uploaded by doko, a new source-only upload is needed to allow migration
  • Additional info:
    • 240 days old (needed 5 days)
• metche (- to 1:1.2.4-2)
  • Migration status for metche (- to 1:1.2.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating metche would introduce bugs in testing: #913719
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metche.html
    • 240 days old (needed 5 days)
• regripper (- to 3.0~git20210405.05ef957+dfsg1-1)
  • Migration status for regripper (- to 3.0~git20210405.05ef957+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by hertzog, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/regripper.html
    • autopkgtest for regripper/3.0~git20210405.05ef957+dfsg1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 240 days old (needed 2 days)
• beignet (- to 1.3.2-9)
  • Migration status for beignet (- to 1.3.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating beignet would introduce bugs in testing: #974792
    • beignet unsatisfiable Build-Depends(-Arch) on amd64: clang-9
    • beignet unsatisfiable Build-Depends(-Arch) on amd64: libclang-9-dev
    • beignet unsatisfiable Build-Depends(-Arch) on amd64: llvm-9-dev
    • beignet unsatisfiable Build-Depends(-Arch) on i386: clang-9
    • beignet unsatisfiable Build-Depends(-Arch) on i386: libclang-9-dev
    • beignet unsatisfiable Build-Depends(-Arch) on i386: llvm-9-dev
    • beignet-opencl-icd/amd64 has unsatisfiable Built-Using on llvm-toolchain-9 1:9.0.1-20
    • beignet-opencl-icd/i386 has unsatisfiable Built-Using on llvm-toolchain-9 1:9.0.1-20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beignet.html
    • autopkgtest for beignet/1.3.2-9: amd64: No test results, i386: No test results
    • 241 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 241 days old (needed 2 days)
• perceptualdiff (- to 2.1-5)
  • Migration status for perceptualdiff (- to 2.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating perceptualdiff would introduce bugs in testing: #982864, #992905
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on mipsel
    • missing build on s390x
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for perceptualdiff/2.1-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perceptualdiff.html
    • 242 days old (needed 5 days)
• uwsgi-plugin-luajit (- to 0.0.7)
  • Migration status for uwsgi-plugin-luajit (- to 0.0.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): uwsgi-plugin-luajit luajit (not considered)
    • Invalidated by build-dependency
    • Depends: uwsgi-plugin-luajit luajit2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi-plugin-luajit.html
    • 242 days old (needed 5 days)
• golang-github-traefik-yaegi (- to 0.10.0-2)
  • Migration status for golang-github-traefik-yaegi (- to 0.10.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-traefik-yaegi would introduce bugs in testing: #1008421
    • yaegi/amd64 has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/arm64 has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/armel has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/armhf has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/i386 has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/mips64el has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/mipsel has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/ppc64el has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • yaegi/s390x has unsatisfiable Built-Using on golang-1.16 1.16.9-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-yaegi.html
    • autopkgtest for golang-github-traefik-yaegi/0.10.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 243 days old (needed 2 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
    • 243 days old (needed 5 days)
• python-yubiotp (- to 1.0.0-2)
  • Migration status for python-yubiotp (- to 1.0.0-2): 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-yubiotp.html
    • 243 days old (needed 5 days)
• rust-kmon (- to 1.5.3-3)
  • Migration status for rust-kmon (- to 1.5.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-kmon would introduce bugs in testing: #997678
    • Build-Depends(-Arch): rust-kmon rust-clipboard
    • Build-Depends(-Arch): rust-kmon rust-tui
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-kmon.html
    • 243 days old (needed 5 days)
• rabbiter (- to 2.0.4-4)
  • Migration status for rabbiter (- to 2.0.4-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rabbiter ruby-gnome (not considered)
    • Invalidated by dependency
    • Depends: rabbiter rabbit
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbiter.html
    • 244 days old (needed 5 days)
• django-uwsgi (- to 1.1.2-1)
  • Migration status for django-uwsgi (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-uwsgi would introduce bugs in testing: #997874
    • autopkgtest for django-uwsgi/1.1.2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • 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-uwsgi.html
    • 245 days old (needed 5 days)
• ttyd (- to 1.6.3+20210924-1)
  • Migration status for ttyd (- to 1.6.3+20210924-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ttyd would introduce bugs in testing: #996042
    • Depends: ttyd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ttyd.html
    • 245 days old (needed 5 days)
• golang-github-uber-go-tally (- to 4.0.1-1)
  • Migration status for golang-github-uber-go-tally (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-uber-go-tally/4.0.1-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-uber-go-tally.html
    • 247 days old (needed 5 days)
• python-loompy (- to 3.0.6+dfsg-5)
  • Migration status for python-loompy (- to 3.0.6+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-loompy/3.0.6+dfsg-5: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • Build-Depends(-Arch): python-loompy numba
    • Build-Depends(-Arch): python-loompy python-numpy-groupies
    • Depends: python-loompy python-numpy-groupies
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-loompy.html
    • 247 days old (needed 5 days)
• golang-github-hashicorp-go-slug (- to 0.7.0-1)
  • Migration status for golang-github-hashicorp-go-slug (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-hashicorp-go-slug would introduce bugs in testing: #997847
    • autopkgtest for golang-github-hashicorp-go-slug/0.7.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-go-slug.html
    • 248 days old (needed 5 days)
• golang-github-hdrhistogram-hdrhistogram-go (- to 1.1.2-2)
  • Migration status for golang-github-hdrhistogram-hdrhistogram-go (- to 1.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): golang-github-hdrhistogram-hdrhistogram-go golang-gonum-v1-gonum (not considered)
    • Depends: golang-github-hdrhistogram-hdrhistogram-go golang-gonum-v1-gonum (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hdrhistogram-hdrhistogram-go.html
    • autopkgtest for golang-github-hdrhistogram-hdrhistogram-go/1.1.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 249 days old (needed 2 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvchecker.html
    • 250 days old (needed 5 days)
• pynpoint (- to 0.10.0-1)
  • Migration status for pynpoint (- to 0.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pynpoint numba (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynpoint.html
    • 250 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:
    • Updating basemap would introduce bugs in testing: #1009424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/basemap.html
    • 253 days old (needed 5 days)
• libgit-raw-perl (- to 0.88+ds-1)
  • Migration status for libgit-raw-perl (- to 0.88+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgit-raw-perl would introduce bugs in testing: #1009031
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/amd64
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/arm64
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/armel
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/armhf
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/i386
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/mips64el
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/mipsel
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/ppc64el
    • Impossible Depends: libgit-raw-perl -> libgit2-1.1/1.1.0+dfsg.1-4.1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgit-raw-perl.html
    • autopkgtest for libgit-raw-perl/0.88+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 253 days old (needed 2 days)
• varnish-vmod-digest (- to 6.4-2)
  • Migration status for varnish-vmod-digest (- to 6.4-2): 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
    • 255 days old (needed 5 days)
• q2-sample-classifier (- to 2021.8.0-1)
  • Migration status for q2-sample-classifier (- to 2021.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-sample-classifier/2021.8.0-1: amd64: Regression ♻ (reference ♻), arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-sample-classifier.html
    • 256 days old (needed 5 days)
• s3ql (- to 3.7.3+dfsg-1)
  • Migration status for s3ql (- to 3.7.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • s3ql/amd64 has unsatisfiable dependency
    • s3ql/arm64 has unsatisfiable dependency
    • s3ql/armel has unsatisfiable dependency
    • s3ql/armhf has unsatisfiable dependency
    • s3ql/i386 has unsatisfiable dependency
    • s3ql/mips64el has unsatisfiable dependency
    • s3ql/mipsel has unsatisfiable dependency
    • s3ql/ppc64el has unsatisfiable dependency
    • s3ql/s390x has unsatisfiable dependency
    • Updating s3ql would introduce bugs in testing: #982381
    • Build-Depends(-Arch): s3ql python-dugong
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/s3ql.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
    • 260 days old (needed 5 days)
• gitlab-shell (- to 13.19.1-2)
  • Migration status for gitlab-shell (- to 13.19.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-shell would introduce bugs in testing: #985840
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-shell.html
    • 262 days old (needed 5 days)
• invesalius (- to 3.1.99995-1)
  • Migration status for invesalius (- to 3.1.99995-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: invesalius keras (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invesalius.html
    • 262 days old (needed 5 days)
• rust-snafu (- to 0.6.10-1)
  • Migration status for rust-snafu (- to 0.6.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-snafu-dev/amd64 has unsatisfiable dependency
    • librust-snafu-dev/arm64 has unsatisfiable dependency
    • librust-snafu-dev/armel has unsatisfiable dependency
    • librust-snafu-dev/armhf has unsatisfiable dependency
    • librust-snafu-dev/i386 has unsatisfiable dependency
    • librust-snafu-dev/mips64el has unsatisfiable dependency
    • librust-snafu-dev/mipsel has unsatisfiable dependency
    • librust-snafu-dev/ppc64el has unsatisfiable dependency
    • librust-snafu-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-snafu.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
    • 263 days old (needed 5 days)
• flask-oidc (- to 1.4.0-2)
  • Migration status for flask-oidc (- to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for flask-oidc/1.4.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Regression ♻
    • 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/f/flask-oidc.html
    • 264 days old (needed 5 days)
• gpyfft (- to 0.7.1-2)
  • Migration status for gpyfft (- to 0.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpyfft would introduce bugs in testing: #995017
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpyfft.html
    • autopkgtest for gpyfft/0.7.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Not a regression, s390x: Not a regression
    • 264 days old (needed 5 days)
• varnish-modules (- to 0.18.0-1)
  • Migration status for varnish-modules (- to 0.18.0-1): 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.18.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 264 days old (needed 2 days)
• twitterwatch (- to 0.1-2)
  • Migration status for twitterwatch (- to 0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating twitterwatch would introduce bugs in testing: #996799
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twitterwatch.html
    • 265 days old (needed 5 days)
• varnish (- to 6.6.1-1)
  • Migration status for varnish (- to 6.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating varnish would introduce bugs in testing: #1004433, #1010582
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varnish.html
    • autopkgtest for varnish/6.6.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 265 days old (needed 2 days)
• openvdb (- to 8.1.0-3)
  • Migration status for openvdb (- to 8.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-openvdb/amd64 has unsatisfiable dependency
    • python3-openvdb/arm64 has unsatisfiable dependency
    • python3-openvdb/armel has unsatisfiable dependency
    • python3-openvdb/armhf has unsatisfiable dependency
    • python3-openvdb/i386 has unsatisfiable dependency
    • python3-openvdb/mips64el has unsatisfiable dependency
    • python3-openvdb/mipsel has unsatisfiable dependency
    • python3-openvdb/ppc64el has unsatisfiable dependency
    • python3-openvdb/s390x has unsatisfiable dependency
    • Updating openvdb would introduce bugs in testing: #997080
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvdb.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
    • 268 days old (needed 5 days)
• puddletag (- to 2.0.1-3)
  • Migration status for puddletag (- to 2.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating puddletag would introduce bugs in testing: #1008686
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puddletag.html
    • 268 days old (needed 5 days)
• textql (- to 2.0.3-4)
  • Migration status for textql (- to 2.0.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating textql would introduce bugs in testing: #1006025
    • textql/amd64 has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/arm64 has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/armel has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/armhf has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/i386 has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • textql/mips64el has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/mipsel has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/ppc64el has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • textql/s390x has unsatisfiable Built-Using on golang-1.16 1.16.8-1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/textql.html
    • 268 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
    • 269 days old (needed 5 days)
• performous (- to 1.1+git20181118-5)
  • Migration status for performous (- to 1.1+git20181118-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating performous would introduce bugs in testing: #1010095
    • Impossible Depends: performous -> libicu67/67.1-7/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/performous.html
    • 270 days old (needed 5 days)
• bitcoin (- to 22.0-1)
  • Migration status for bitcoin (- to 22.0-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 jcristau (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitcoin.html
    • 273 days old (needed 5 days)
• panicparse (- to 1.6.1-3)
  • Migration status for panicparse (- to 1.6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating panicparse would introduce bugs in testing: #997589
    • autopkgtest for panicparse/1.6.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • panicparse/amd64 has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/arm64 has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/armel has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/armhf has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/i386 has unsatisfiable Built-Using on golang-1.16 1.16.9-2
    • panicparse/mips64el has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/mipsel has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/ppc64el has unsatisfiable Built-Using on golang-1.16 1.16.8-1
    • panicparse/s390x has unsatisfiable Built-Using on golang-1.16 1.16.8-1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/panicparse.html
    • 273 days old (needed 5 days)
• golang-github-xenolf-lego (- to 4.1.3-3)
  • Migration status for golang-github-xenolf-lego (- to 4.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): golang-github-xenolf-lego golang-codegangsta-cli (not considered)
    • Depends: golang-github-xenolf-lego golang-codegangsta-cli (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-xenolf-lego.html
    • autopkgtest for golang-github-xenolf-lego/4.1.3-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 274 days old (needed 2 days)
• python-epimodels (- to 0.3.20-1)
  • Migration status for python-epimodels (- to 0.3.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-epimodels would introduce bugs in testing: #1002335
    • autopkgtest for python-epimodels/0.3.20-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • Build-Depends(-Arch): python-epimodels numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-epimodels.html
    • 274 days old (needed 5 days)
• remem (- to 2.12-7.2)
  • Migration status for remem (- to 2.12-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating remem would introduce bugs in testing: #965797, #999161
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/remem.html
    • 274 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
    • 275 days old (needed 5 days)
• brebis (- to 0.10-2)
  • Migration status for brebis (- to 0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating brebis would introduce bugs in testing: #1002414
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/brebis.html
    • 275 days old (needed 5 days)
• go-exploitdb (- to 0.0~git20181130.7c961e7-2)
  • Migration status for go-exploitdb (- to 0.0~git20181130.7c961e7-2): 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-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 277 days old (needed 2 days)
• snort (- to 2.9.15.1-6)
  • Migration status for snort (- to 2.9.15.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): snort luajit (not considered)
    • Invalidated by build-dependency
    • Depends: snort luajit2
    • Depends: snort openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snort.html
    • 278 days old (needed 5 days)
• restic (- to 0.12.1-2)
  • Migration status for restic (- to 0.12.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): restic golang-github-kurin-blazer (not considered)
    • Built-Using: restic golang-github-kurin-blazer (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restic.html
    • 279 days old (needed 5 days)
• ruby-jekyll-toc (- to 0.17.1-1)
  • Migration status for ruby-jekyll-toc (- to 0.17.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-jekyll-toc jekyll (not considered)
    • Depends: ruby-jekyll-toc jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-toc.html
    • autopkgtest for ruby-jekyll-toc/0.17.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 279 days old (needed 2 days)
• haskell-termonad (- to 4.0.0.1-2)
  • Migration status for haskell-termonad (- to 4.0.0.1-2): 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
    • Build-Depends(-Arch): haskell-termonad haskell-gi-gdk
    • Build-Depends(-Arch): haskell-termonad haskell-gi-gio
    • Build-Depends(-Arch): haskell-termonad haskell-gi-gtk
    • Build-Depends(-Arch): haskell-termonad haskell-gi-pango
    • Build-Depends(-Arch): haskell-termonad haskell-gi-vte
    • Build-Depends-Indep: haskell-termonad haskell-gi-gdk
    • Build-Depends-Indep: haskell-termonad haskell-gi-gio
    • Build-Depends-Indep: haskell-termonad haskell-gi-gtk
    • Build-Depends-Indep: haskell-termonad haskell-gi-pango
    • Build-Depends-Indep: haskell-termonad haskell-gi-vte
    • Depends: haskell-termonad haskell-gi-gdk
    • Depends: haskell-termonad haskell-gi-gio
    • Depends: haskell-termonad haskell-gi-gtk
    • Depends: haskell-termonad haskell-gi-pango
    • Depends: haskell-termonad haskell-gi-vte
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-termonad.html
    • 281 days old (needed 5 days)
• jupyter-sphinx (- to 0.3.2-1)
  • Migration status for jupyter-sphinx (- to 0.3.2-1): 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
    • 281 days old (needed 5 days)
• xpra (- to 3.1-1)
  • Migration status for xpra (- to 3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xpra would introduce bugs in testing: #994619
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpra.html
    • autopkgtest for xpra/3.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 281 days old (needed 2 days)
• ruby-jekyll-polyglot (- to 1.5.0-1)
  • Migration status for ruby-jekyll-polyglot (- to 1.5.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-polyglot jekyll (not considered)
    • Depends: ruby-jekyll-polyglot jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-polyglot.html
    • autopkgtest for ruby-jekyll-polyglot/1.5.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 282 days old (needed 2 days)
• gnome-documents (- to 3.34.0-4)
  • Migration status for gnome-documents (- to 3.34.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-documents would introduce bugs in testing: #1005549, #1008526
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-documents.html
    • 284 days old (needed 5 days)
• milter-greylist (- to 4.6.4-1)
  • Migration status for milter-greylist (- to 4.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating milter-greylist would introduce bugs in testing: #1002527
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/milter-greylist.html
    • 284 days old (needed 5 days)
• php-wmerrors (- to 2.0.0~git20190628.183ef7d-3)
  • Migration status for php-wmerrors (- to 2.0.0~git20190628.183ef7d-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-wmerrors/amd64 has unsatisfiable dependency
    • php-wmerrors/arm64 has unsatisfiable dependency
    • php-wmerrors/armel has unsatisfiable dependency
    • php-wmerrors/armhf has unsatisfiable dependency
    • php-wmerrors/i386 has unsatisfiable dependency
    • php-wmerrors/mips64el has unsatisfiable dependency
    • php-wmerrors/mipsel has unsatisfiable dependency
    • php-wmerrors/ppc64el has unsatisfiable dependency
    • php-wmerrors/s390x has unsatisfiable dependency
    • Updating php-wmerrors would introduce bugs in testing: #1003432
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-wmerrors.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
    • 284 days old (needed 5 days)
• gcc-10-cross-ports (- to 19)
  • Migration status for gcc-10-cross-ports (- to 19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10-cross-ports would introduce bugs in testing: #1008326
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-ports.html
    • 285 days old (needed 5 days)
• rust-reqwest (- to 0.9.19-5)
  • Migration status for rust-reqwest (- to 0.9.19-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-reqwest+default-tls-vendored-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+rustls-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+socks-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/amd64 has unsatisfiable dependency
    • librust-reqwest-dev/amd64 has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+rustls-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+socks-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/arm64 has unsatisfiable dependency
    • librust-reqwest-dev/arm64 has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/armel has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/armel has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/armel has unsatisfiable dependency
    • librust-reqwest+rustls-dev/armel has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/armel has unsatisfiable dependency
    • librust-reqwest+socks-dev/armel has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/armel has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/armel has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/armel has unsatisfiable dependency
    • librust-reqwest-dev/armel has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/armhf has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/armhf has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/armhf has unsatisfiable dependency
    • librust-reqwest+rustls-dev/armhf has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/armhf has unsatisfiable dependency
    • librust-reqwest+socks-dev/armhf has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/armhf has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/armhf has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/armhf has unsatisfiable dependency
    • librust-reqwest-dev/armhf has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/i386 has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/i386 has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/i386 has unsatisfiable dependency
    • librust-reqwest+rustls-dev/i386 has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/i386 has unsatisfiable dependency
    • librust-reqwest+socks-dev/i386 has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/i386 has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/i386 has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/i386 has unsatisfiable dependency
    • librust-reqwest-dev/i386 has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+rustls-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+socks-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/mips64el has unsatisfiable dependency
    • librust-reqwest-dev/mips64el has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+rustls-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+socks-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/mipsel has unsatisfiable dependency
    • librust-reqwest-dev/mipsel has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+rustls-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+socks-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest-dev/ppc64el has unsatisfiable dependency
    • librust-reqwest+default-tls-vendored-dev/s390x has unsatisfiable dependency
    • librust-reqwest+hyper-011-dev/s390x has unsatisfiable dependency
    • librust-reqwest+hyper-rustls-dev/s390x has unsatisfiable dependency
    • librust-reqwest+rustls-dev/s390x has unsatisfiable dependency
    • librust-reqwest+rustls-tls-dev/s390x has unsatisfiable dependency
    • librust-reqwest+socks-dev/s390x has unsatisfiable dependency
    • librust-reqwest+tokio-rustls-dev/s390x has unsatisfiable dependency
    • librust-reqwest+trust-dns-dev/s390x has unsatisfiable dependency
    • librust-reqwest+webpki-roots-dev/s390x has unsatisfiable dependency
    • librust-reqwest-dev/s390x has unsatisfiable dependency
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on amd64: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on amd64: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on amd64: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on amd64: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on arm64: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on arm64: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on arm64: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on arm64: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armel: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armel: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armel: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armel: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armhf: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armhf: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armhf: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on armhf: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on i386: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on i386: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on i386: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on i386: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mips64el: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mips64el: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mips64el: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mips64el: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mipsel: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mipsel: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mipsel: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on mipsel: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on ppc64el: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on ppc64el: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on s390x: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on s390x: librust-serde-urlencoded-0.6+default-dev
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on s390x: librust-tokio-0.1+rt-full-dev (>= 0.1.7-~~)
    • rust-reqwest unsatisfiable Build-Depends(-Arch) on s390x: librust-tokio-0.1+tcp-dev (>= 0.1.7-~~)
    • Build-Depends(-Arch): rust-reqwest rust-cookie
    • Build-Depends(-Arch): rust-reqwest rust-cookie-store
    • Build-Depends(-Arch): rust-reqwest rust-hyper
    • Build-Depends(-Arch): rust-reqwest rust-hyper-tls
    • Build-Depends(-Arch): rust-reqwest rust-tokio-executor
    • Build-Depends(-Arch): rust-reqwest rust-tokio-io
    • Build-Depends(-Arch): rust-reqwest rust-tokio-threadpool
    • Build-Depends(-Arch): rust-reqwest rust-tokio-timer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-reqwest.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
    • 286 days old (needed 5 days)
• libisocodes (- to 1.2.4-1)
  • Migration status for libisocodes (- to 1.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libisocodes would introduce bugs in testing: #998612
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libisocodes.html
    • 288 days old (needed 5 days)
• ruby-google-api-client (- to 0.50.0-2)
  • Migration status for ruby-google-api-client (- to 0.50.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-google-api-client ruby-representable (not considered)
    • Depends: ruby-google-api-client ruby-representable (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-google-api-client.html
    • autopkgtest for ruby-google-api-client/0.50.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 288 days old (needed 5 days)
• ruby-grape (- to 1.5.2-2)
  • Migration status for ruby-grape (- to 1.5.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-grape ruby-virtus (not considered)
    • Depends: ruby-grape ruby-virtus (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape.html
    • autopkgtest for ruby-grape/1.5.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 288 days old (needed 2 days)
• simplematch (- to 1.3-1)
  • Migration status for simplematch (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frediz@linux.vnet.ibm.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplematch.html
    • 288 days old (needed 5 days)
• pktstat (- to 1.8.5-7)
  • Migration status for pktstat (- to 1.8.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pktstat would introduce bugs in testing: #995624
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pktstat.html
    • 290 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)
    • 291 days old (needed 5 days)
• golang-gonum-v1-gonum (- to 0.9.0-1)
  • Migration status for golang-gonum-v1-gonum (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-gonum-v1-gonum/0.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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/g/golang-gonum-v1-gonum.html
    • 291 days old (needed 5 days)
• amanda (- to 1:3.5.1-8)
  • Migration status for amanda (- to 1:3.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating amanda would introduce bugs in testing: #1008447
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amanda.html
    • 292 days old (needed 5 days)
• libnih (- to 1.0.3-12)
  • Migration status for libnih (- to 1.0.3-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libnih would introduce bugs in testing: #1008415
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnih.html
    • 293 days old (needed 5 days)
• wims (- to 2:4.22~dfsg1-2)
  • Migration status for wims (- to 2:4.22~dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wims would introduce bugs in testing: #997720
    • Depends: wims slick
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wims.html
    • 293 days old (needed 5 days)
• golang-github-seccomp-containers-golang (- to 0.3.2-2)
  • Migration status for golang-github-seccomp-containers-golang (- to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-seccomp-containers-golang would introduce bugs in testing: #988440
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-seccomp-containers-golang.html
    • autopkgtest for golang-github-seccomp-containers-golang/0.3.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 294 days old (needed 2 days)
• mini-buildd (- to 1.0.49)
  • Migration status for mini-buildd (- to 1.0.49): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mini-buildd would introduce bugs in testing: #933751, #937049
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python (>= 2.7)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.1.3)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-pygraphviz
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-argcomplete (>= 0.5.4)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-keyring (>= 1.6)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-daemon (>= 2.0.5)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-debian (>= 0.1.18~)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-cherrypy3
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-pyftpdlib (>= 1.2.0)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-django (>= 1.7)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-django (<< 1:1.12)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-django-registration (>= 2.0.4)
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-tz
    • mini-buildd unsatisfiable Build-Depends(-Arch) on amd64: python-tzlocal
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mini-buildd.html
    • 294 days old (needed 5 days)
• platformio (- to 4.3.4-2)
  • Migration status for platformio (- to 4.3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating platformio would introduce bugs in testing: #988716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformio.html
    • autopkgtest for platformio/4.3.4-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 294 days old (needed 5 days)
• python-sparse (- to 0.12.0-1)
  • Migration status for python-sparse (- to 0.12.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-sparse numba (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sparse.html
    • autopkgtest for python-sparse/0.12.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 294 days old (needed 5 days)
• crdt-el (- to 0.0~20210526-2)
  • Migration status for crdt-el (- to 0.0~20210526-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by bremner, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crdt-el.html
    • 295 days old (needed 5 days)
• sopel (- to 6.6.9-2)
  • Migration status for sopel (- to 6.6.9-2): 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
    • 295 days old (needed 5 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/mipsel has unsatisfiable dependency
    • purify/mipsel 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:
    • Piuparts tested OK - 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 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
    • 300 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
    • 312 days old (needed 5 days)
• mysql-workbench (- to 8.0.26+dfsg-1)
  • Migration status for mysql-workbench (- to 8.0.26+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mysql-workbench/amd64 has unsatisfiable dependency
    • mysql-workbench/arm64 has unsatisfiable dependency
    • mysql-workbench/armel has unsatisfiable dependency
    • mysql-workbench/armhf has unsatisfiable dependency
    • mysql-workbench/i386 has unsatisfiable dependency
    • mysql-workbench/mips64el has unsatisfiable dependency
    • mysql-workbench/mipsel has unsatisfiable dependency
    • mysql-workbench/ppc64el has unsatisfiable dependency
    • mysql-workbench/s390x has unsatisfiable dependency
    • Updating mysql-workbench would introduce bugs in testing: #1009657, #998833
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mysql-workbench.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
    • 320 days old (needed 5 days)
• pppoeconf (- to 1.21+nmu2)
  • Migration status for pppoeconf (- to 1.21+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pppoeconf would introduce bugs in testing: #965786
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pppoeconf.html
    • 323 days old (needed 5 days)
• networkd-dispatcher (- to 2.1-2)
  • Migration status for networkd-dispatcher (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating networkd-dispatcher would introduce bugs in testing: #1010303
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/networkd-dispatcher.html
    • 334 days old (needed 5 days)
• nomad (- to 0.12.10+dfsg1-3)
  • Migration status for nomad (- to 0.12.10+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomad would introduce bugs in testing: #1000441, #994214
    • nomad/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • nomad/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • Build-Depends(-Arch): nomad golang-github-hashicorp-go-plugin
    • Depends: nomad golang-github-hashicorp-go-plugin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomad.html
    • 335 days old (needed 5 days)
• ruby-rails-assets-diaspora-jsxc (- to 0.1.5+dfsg2~develop.7-6)
  • Migration status for ruby-rails-assets-diaspora-jsxc (- to 0.1.5+dfsg2~develop.7-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-rails-assets-diaspora-jsxc ruby-rails-assets-favico.js (not considered)
    • Depends: ruby-rails-assets-diaspora-jsxc ruby-rails-assets-favico.js (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-rails-assets-diaspora-jsxc ruby-rails-assets-jquery-fullscreen-plugin
    • Depends: ruby-rails-assets-diaspora-jsxc ruby-rails-assets-jquery-fullscreen-plugin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-diaspora-jsxc.html
    • autopkgtest for ruby-rails-assets-diaspora-jsxc/0.1.5+dfsg2~develop.7-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 335 days old (needed 5 days)
• python-pynndescent (- to 0.5.2+dfsg-1)
  • Migration status for python-pynndescent (- to 0.5.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): python-pynndescent numba (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pynndescent.html
    • autopkgtest for python-pynndescent/0.5.2+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 342 days old (needed 2 days)
• libyang (- to 1.0.225-1.1)
  • Migration status for libyang (- to 1.0.225-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libyang would introduce bugs in testing: #1003766, #1003767
    • autopkgtest for libyang/1.0.225-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liby/libyang.html
    • 351 days old (needed 5 days)
• ogmrip (- to 1.0.1-3.1)
  • Migration status for ogmrip (- to 1.0.1-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ogmrip mplayer (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogmrip.html
    • 358 days old (needed 5 days)
• libpam-chroot (- to 0.9-5)
  • Migration status for libpam-chroot (- to 0.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-chroot would introduce bugs in testing: #965672, #991113
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-chroot.html
    • 359 days old (needed 5 days)
• ruby-sidekiq-cron (- to 1.2.0-1)
  • Migration status for ruby-sidekiq-cron (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-sidekiq-cron would introduce bugs in testing: #1002092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-sidekiq-cron.html
    • autopkgtest for ruby-sidekiq-cron/1.2.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 360 days old (needed 2 days)
• haskell-hoogle (- to 5.0.18.1+dfsg1-2)
  • Migration status for haskell-hoogle (- to 5.0.18.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-hoogle would introduce bugs in testing: #971832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hoogle.html
    • autopkgtest for haskell-hoogle/5.0.18.1+dfsg1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 361 days old (needed 2 days)
• ruby-carrierwave (- to 1.3.2-2)
  • Migration status for ruby-carrierwave (- to 1.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-carrierwave ruby-fog-google (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-carrierwave.html
    • autopkgtest for ruby-carrierwave/1.3.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 363 days old (needed 5 days)
• ruby-spamcheck (- to 0.1.0+git20210519.2084b44-2)
  • Migration status for ruby-spamcheck (- to 0.1.0+git20210519.2084b44-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-spamcheck would introduce bugs in testing: #989786
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for ruby-spamcheck/0.1.0+git20210519.2084b44-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 363 days old (needed 5 days)
• xfonts-bolkhov (- to 1.1.20001007-8.2)
  • Migration status for xfonts-bolkhov (- to 1.1.20001007-8.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfonts-bolkhov would introduce bugs in testing: #999281
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfonts-bolkhov.html
    • 370 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: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diaspora-installer.html
    • 378 days old (needed 5 days)
• gosa (- to 2.7.4+reloaded3-16)
  • Migration status for gosa (- to 2.7.4+reloaded3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gosa would introduce bugs in testing: #1003694
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa.html
    • 381 days old (needed 5 days)
• pytest-services (- to 2.2.1+ds-2)
  • Migration status for pytest-services (- to 2.2.1+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytest-services/2.2.1+ds-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Build-Depends(-Arch): pytest-services mysql-8.0
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-services.html
    • 386 days old (needed 5 days)
• vpb-driver (- to 4.2.61-1.2)
  • Migration status for vpb-driver (- to 4.2.61-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vpb-driver would introduce bugs in testing: #1005418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vpb-driver.html
    • 390 days old (needed 5 days)
• trac (- to 1.5.3+dfsg-1)
  • Migration status for trac (- to 1.5.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trac would introduce bugs in testing: #988462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trac.html
    • 396 days old (needed 5 days)
• ring (- to 20210112.2.b757bac~ds1-1)
  • Migration status for ring (- to 20210112.2.b757bac~ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • jami-daemon/amd64 has unsatisfiable dependency
    • jami-daemon/arm64 has unsatisfiable dependency
    • jami-daemon/armel has unsatisfiable dependency
    • jami-daemon/armhf has unsatisfiable dependency
    • jami-daemon/i386 has unsatisfiable dependency
    • jami-daemon/mips64el has unsatisfiable dependency
    • jami-daemon/mipsel has unsatisfiable dependency
    • jami-daemon/ppc64el has unsatisfiable dependency
    • jami-daemon/s390x has unsatisfiable dependency
    • Updating ring would introduce bugs in testing: #984321
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ring.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
    • 405 days old (needed 5 days)
• gosa-plugin-mailaddress (- to 0.99.7-2)
  • Migration status for gosa-plugin-mailaddress (- to 0.99.7-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugin-mailaddress gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugin-mailaddress.html
    • 408 days old (needed 5 days)
• php-horde-crypt (- to 2.7.12-6)
  • Migration status for php-horde-crypt (- to 2.7.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-crypt would introduce bugs in testing: #1003744
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt.html
    • autopkgtest for php-horde-crypt/2.7.12-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 408 days old (needed 5 days)
• virt-top (- to 1.0.9-1.1)
  • Migration status for virt-top (- to 1.0.9-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virt-top would introduce bugs in testing: #1004477
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virt-top.html
    • autopkgtest for virt-top/1.0.9-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 411 days old (needed 2 days)
• python-jenkinsapi (- to 0.3.11-5)
  • Migration status for python-jenkinsapi (- to 0.3.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-jenkinsapi would introduce bugs in testing: #1012326, #998530
    • python-jenkinsapi unsatisfiable Build-Depends(-Arch) on amd64: pylint3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jenkinsapi.html
    • 412 days old (needed 5 days)
• vtk6 (- to 6.3.0+dfsg2-8.1)
  • Migration status for vtk6 (- to 6.3.0+dfsg2-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libvtk6.3/amd64 has unsatisfiable dependency
    • libvtk6.3/arm64 has unsatisfiable dependency
    • libvtk6.3/armel has unsatisfiable dependency
    • libvtk6.3/armhf has unsatisfiable dependency
    • libvtk6.3/i386 has unsatisfiable dependency
    • libvtk6.3/mips64el has unsatisfiable dependency
    • libvtk6.3/mipsel has unsatisfiable dependency
    • libvtk6.3/ppc64el has unsatisfiable dependency
    • libvtk6.3/s390x has unsatisfiable dependency
    • Updating vtk6 would introduce bugs in testing: #1012464, #984398, #996976
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtk6.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
    • 412 days old (needed 5 days)
• syncmaildir (- to 1.3.0-1.1)
  • Migration status for syncmaildir (- to 1.3.0-1.1): 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
    • 413 days old (needed 5 days)
• mailmindr (- to 1.0.0-1~exp1)
  • Migration status for mailmindr (- to 1.0.0-1~exp1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ooo@mechtilde.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailmindr.html
    • 419 days old (needed 5 days)
• log4net (- to 1.2.10+dfsg-8)
  • Migration status for log4net (- to 1.2.10+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating log4net would introduce bugs in testing: #965701, #999313
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/log4net.html
    • 425 days old (needed 5 days)
• php-http-interop-http-factory-tests (- to 0.9.0-1)
  • Migration status for php-http-interop-http-factory-tests (- 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 taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-interop-http-factory-tests.html
    • 426 days old (needed 5 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-1)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Pass
    • 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/g/golang-github-leanovate-gopter.html
    • 429 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
    • 430 days old (needed 5 days)
• cxxtools (- to 2.2.1-4)
  • Migration status for cxxtools (- to 2.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cxxtools would introduce bugs in testing: #984028
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cxxtools.html
    • 448 days old (needed 5 days)
• dnsviz (- to 0.9.3-1)
  • Migration status for dnsviz (- to 0.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dnsviz would introduce bugs in testing: #997329
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnsviz.html
    • 451 days old (needed 5 days)
• shove (- to 0.8.4-1)
  • Migration status for shove (- to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shove would introduce bugs in testing: #985520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shove.html
    • 451 days old (needed 5 days)
• vuls (- to 0.6.1-3)
  • Migration status for vuls (- 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: 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-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 455 days old (needed 2 days)
• ubuntu-keyring (- to 2020.06.17.1-1)
  • Migration status for ubuntu-keyring (- to 2020.06.17.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ubuntu-keyring would introduce bugs in testing: #929165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ubuntu-keyring.html
    • autopkgtest for ubuntu-keyring/2020.06.17.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 461 days old (needed 2 days)
• dogecoin (- to 1.14.3-1)
  • Migration status for dogecoin (- to 1.14.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dogecoin would introduce bugs in testing: #997462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogecoin.html
    • 464 days old (needed 5 days)
• request-tracker5 (- to 5.0.1+dfsg-1)
  • Migration status for request-tracker5 (- to 5.0.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating request-tracker5 would introduce bugs in testing: #985704, #988905, #995167
    • Not built on buildd: arch all binaries uploaded by andrew@etc.gen.nz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/request-tracker5.html
    • 464 days old (needed 5 days)
• activemq (- to 5.16.1-1)
  • Migration status for activemq (- to 5.16.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): activemq zookeeper (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/activemq.html
    • 465 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: #975926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enigmail.html
    • 466 days old (needed 5 days)
• awl (- to 0.62-1)
  • Migration status for awl (- to 0.62-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating awl would introduce bugs in testing: #1005449
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/awl.html
    • 467 days old (needed 5 days)
• davical (- to 1.1.10-1)
  • Migration status for davical (- to 1.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating davical would introduce bugs in testing: #1004285
    • Build-Depends(-Arch): davical awl
    • Depends: davical awl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/davical.html
    • 467 days old (needed 5 days)
• gatos (- to 0.0.5-19.1)
  • Migration status for gatos (- to 0.0.5-19.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gatos would introduce bugs in testing: #965534
    • Build-Depends(-Arch): gatos libibtk
    • Depends: gatos libibtk
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 467 days old (needed 5 days)
• roundcube-plugins-extra (- to 1.4.10+1-3)
  • Migration status for roundcube-plugins-extra (- to 1.4.10+1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): roundcube-plugins-extra roundcube (not considered)
    • Depends: roundcube-plugins-extra roundcube (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/roundcube-plugins-extra.html
    • 467 days old (needed 5 days)
• icingaweb2-module-metapackages (- to 20210209-1)
  • Migration status for icingaweb2-module-metapackages (- to 20210209-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mail@daniel-baumann.ch, a new source-only upload is needed to allow migration
    • Depends: icingaweb2-module-metapackages icingaweb2-module-boxydash
    • Depends: icingaweb2-module-metapackages icingaweb2-module-cube
    • Depends: icingaweb2-module-metapackages icingaweb2-module-idoreports
    • Depends: icingaweb2-module-metapackages icingaweb2-module-map
    • Depends: icingaweb2-module-metapackages icingaweb2-module-statusmap
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-metapackages.html
    • 468 days old (needed 5 days)
• gdnsd (- to 3.5.2-1)
  • Migration status for gdnsd (- to 3.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdnsd would introduce bugs in testing: #1002225
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdnsd.html
    • autopkgtest for gdnsd/3.5.2-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 469 days old (needed 5 days)
• bazel-bootstrap (- to 3.5.1+ds-3)
  • Migration status for bazel-bootstrap (- to 3.5.1+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bazel-bootstrap would introduce bugs in testing: #983982
    • autopkgtest for bazel-bootstrap/3.5.1+ds-3: amd64: Pass, arm64: Pass, armhf: No test results, i386: No test results, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bazel-bootstrap.html
    • 471 days old (needed 5 days)
• python-pygal (- to 2.4.0-2.2)
  • Migration status for python-pygal (- to 2.4.0-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pygal would introduce bugs in testing: #1002367
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pygal.html
    • 471 days old (needed 5 days)
• goval-dictionary (- to 0.2.0-4)
  • Migration status for goval-dictionary (- to 0.2.0-4): 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
    • 473 days old (needed 5 days)
• pytorch-ignite (- to 0.4.3-1)
  • Migration status for pytorch-ignite (- to 0.4.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-ignite pytorch (not considered)
    • Depends: pytorch-ignite pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-ignite.html
    • 473 days old (needed 5 days)
• rt-extension-assetautoname (- to 0.05-2)
  • Migration status for rt-extension-assetautoname (- to 0.05-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rt-extension-assetautoname/0.05-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • rt-extension-assetautoname unsatisfiable Build-Depends-Indep on amd64: libmodule-install-rtx-perl (>= 0.42-1~)
    • Not built on buildd: arch all binaries uploaded by dom, a new source-only upload is needed to allow migration
    • Depends: rt-extension-assetautoname request-tracker5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rt-extension-assetautoname.html
    • 474 days old (needed 5 days)
• rt-extension-assets-import-csv (- to 2.2-1)
  • Migration status for rt-extension-assets-import-csv (- to 2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rt-extension-assets-import-csv unsatisfiable Build-Depends-Indep on amd64: libmodule-install-rtx-perl (>= 0.42)
    • Not built on buildd: arch all binaries uploaded by dom, a new source-only upload is needed to allow migration
    • Depends: rt-extension-assets-import-csv request-tracker5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rt-extension-assets-import-csv.html
    • 474 days old (needed 5 days)
• rt-extension-elapsedbusinesstime (- to 0.05-1)
  • Migration status for rt-extension-elapsedbusinesstime (- to 0.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rt-extension-elapsedbusinesstime/0.05-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • rt-extension-elapsedbusinesstime unsatisfiable Build-Depends-Indep on amd64: libmodule-install-rtx-perl (>= 0.42-1~)
    • Not built on buildd: arch all binaries uploaded by dom, a new source-only upload is needed to allow migration
    • Depends: rt-extension-elapsedbusinesstime request-tracker5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rt-extension-elapsedbusinesstime.html
    • 474 days old (needed 5 days)
• rt-extension-mergeusers (- to 1.06-1)
  • Migration status for rt-extension-mergeusers (- to 1.06-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rt-extension-mergeusers/1.06-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • rt-extension-mergeusers unsatisfiable Build-Depends-Indep on amd64: libmodule-install-rtx-perl (>= 0.42-1~)
    • Not built on buildd: arch all binaries uploaded by dom, a new source-only upload is needed to allow migration
    • Depends: rt-extension-mergeusers request-tracker5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rt-extension-mergeusers.html
    • 474 days old (needed 5 days)
• rt-extension-resetpassword (- to 1.07-1)
  • Migration status for rt-extension-resetpassword (- to 1.07-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rt-extension-resetpassword/1.07-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • rt-extension-resetpassword unsatisfiable Build-Depends-Indep on amd64: libmodule-install-rtx-perl (>= 0.42-1~)
    • Not built on buildd: arch all binaries uploaded by dom, a new source-only upload is needed to allow migration
    • Depends: rt-extension-resetpassword request-tracker5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rt-extension-resetpassword.html
    • 474 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:
    • 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 mipsel: 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
    • 474 days old (needed 5 days)
• direnv (- to 2.25.2-2)
  • Migration status for direnv (- to 2.25.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating direnv would introduce bugs in testing: #997509
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/direnv.html
    • 475 days old (needed 5 days)
• go-cve-dictionary (- to 0.3.1-4)
  • Migration status for go-cve-dictionary (- to 0.3.1-4): 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-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 475 days old (needed 2 days)
• gfpoken (- to 1-3)
  • Migration status for gfpoken (- to 1-3): 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
    • 476 days old (needed 5 days)
• sdic (- to 2.1.3-22.1)
  • Migration status for sdic (- to 2.1.3-22.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sdic would introduce bugs in testing: #754026, #916876
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 476 days old (needed 5 days)
• svtools (- to 0.6-5)
  • Migration status for svtools (- to 0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating svtools would introduce bugs in testing: #981496
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svtools.html
    • autopkgtest for svtools/0.6-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 476 days old (needed 2 days)
• php-horde-text-filter (- to 2.3.7-1)
  • Migration status for php-horde-text-filter (- to 2.3.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-text-filter php-horde-secret (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-filter.html
    • autopkgtest for php-horde-text-filter/2.3.7-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 477 days old (needed 5 days)
• xserver-xorg-video-mach64 (- to 6.9.6-3)
  • Migration status for xserver-xorg-video-mach64 (- to 6.9.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xserver-xorg-video-mach64/amd64 has unsatisfiable dependency
    • xserver-xorg-video-mach64/arm64 has unsatisfiable dependency
    • xserver-xorg-video-mach64/armel has unsatisfiable dependency
    • xserver-xorg-video-mach64/armhf has unsatisfiable dependency
    • xserver-xorg-video-mach64/i386 has unsatisfiable dependency
    • xserver-xorg-video-mach64/mips64el has unsatisfiable dependency
    • xserver-xorg-video-mach64/mipsel has unsatisfiable dependency
    • xserver-xorg-video-mach64/ppc64el has unsatisfiable dependency
    • Updating xserver-xorg-video-mach64 would introduce bugs in testing: #1005462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-mach64.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
    • 478 days old (needed 5 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
    • 479 days old (needed 5 days)
• lua-http (- to 0.4-1)
  • Migration status for lua-http (- to 0.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lua-http lua-luaossl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-http.html
    • autopkgtest for lua-http/0.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 480 days old (needed 2 days)
• libvirt-php (- to 0.5.5-3)
  • Migration status for libvirt-php (- to 0.5.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-libvirt-php/amd64 has unsatisfiable dependency
    • php-libvirt-php/arm64 has unsatisfiable dependency
    • php-libvirt-php/armel has unsatisfiable dependency
    • php-libvirt-php/armhf has unsatisfiable dependency
    • php-libvirt-php/i386 has unsatisfiable dependency
    • php-libvirt-php/mips64el has unsatisfiable dependency
    • php-libvirt-php/mipsel has unsatisfiable dependency
    • php-libvirt-php/ppc64el has unsatisfiable dependency
    • php-libvirt-php/s390x has unsatisfiable dependency
    • Updating libvirt-php would introduce bugs in testing: #1003007
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvirt-php.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
    • 481 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/mipsel has unsatisfiable dependency
    • php-facedetect/ppc64el has unsatisfiable dependency
    • php-facedetect/s390x has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - 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 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
    • 481 days old (needed 5 days)
• ruby-redis-store (- to 1.9.0-1)
  • Migration status for ruby-redis-store (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-store would introduce bugs in testing: #1005422
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-store.html
    • autopkgtest for ruby-redis-store/1.9.0-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 481 days old (needed 5 days)
• slib (- to 3b6-3)
  • Migration status for slib (- to 3b6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slib scm (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slib.html
    • autopkgtest for slib/3b6-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 481 days old (needed 5 days)
• tideways (- to 5.0.4-2)
  • Migration status for tideways (- to 5.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-tideways/amd64 has unsatisfiable dependency
    • php-tideways/arm64 has unsatisfiable dependency
    • php-tideways/armel has unsatisfiable dependency
    • php-tideways/armhf has unsatisfiable dependency
    • php-tideways/i386 has unsatisfiable dependency
    • php-tideways/mips64el has unsatisfiable dependency
    • php-tideways/mipsel has unsatisfiable dependency
    • php-tideways/ppc64el has unsatisfiable dependency
    • php-tideways/s390x has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tideways.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
    • 481 days old (needed 5 days)
• smuxi (- to 1.1-1)
  • Migration status for smuxi (- to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: smuxi log4net (not considered)
    • Depends: smuxi log4net (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends-Indep: smuxi messagingmenu-sharp
    • Build-Depends-Indep: smuxi notify-sharp
    • Depends: smuxi messagingmenu-sharp
    • Depends: smuxi notify-sharp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smuxi.html
    • 483 days old (needed 5 days)
• php-easyrdf (- to 1.0.0-2)
  • Migration status for php-easyrdf (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-easyrdf would introduce bugs in testing: #1001593
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-easyrdf.html
    • autopkgtest for php-easyrdf/1.0.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 485 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 486 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:
    • Updating zeek would introduce bugs in testing: #1002760
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeek.html
    • 487 days old (needed 5 days)
• gom (- to 0.30.3-1)
  • Migration status for gom (- to 0.30.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gom would introduce bugs in testing: #997152
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gom.html
    • 488 days old (needed 5 days)
• jhdf (- to 2.11.0+dfsg-5)
  • Migration status for jhdf (- to 2.11.0+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jhdf would introduce bugs in testing: #853750
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jhdf.html
    • 488 days old (needed 5 days)
• spyder-line-profiler (- to 0.2.1-1)
  • Migration status for spyder-line-profiler (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-line-profiler.html
  • Additional info:
    • autopkgtest for spyder-line-profiler/0.2.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 488 days old (needed 2 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:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-memory-profiler.html
  • Additional info:
    • autopkgtest for spyder-memory-profiler/0.2.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Not a regression
    • 488 days old (needed 5 days)
• varmon (- to 1.2.1-2)
  • Migration status for varmon (- to 1.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating varmon would introduce bugs in testing: #965860, #981522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varmon.html
    • 488 days old (needed 5 days)
• zookeeper (- to 3.4.13-6)
  • Migration status for zookeeper (- to 3.4.13-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-zookeeper/amd64 has unsatisfiable dependency
    • zookeeper-bin/amd64 has unsatisfiable dependency
    • python3-zookeeper/arm64 has unsatisfiable dependency
    • zookeeper-bin/arm64 has unsatisfiable dependency
    • python3-zookeeper/armel has unsatisfiable dependency
    • zookeeper-bin/armel has unsatisfiable dependency
    • python3-zookeeper/armhf has unsatisfiable dependency
    • zookeeper-bin/armhf has unsatisfiable dependency
    • python3-zookeeper/i386 has unsatisfiable dependency
    • zookeeper-bin/i386 has unsatisfiable dependency
    • python3-zookeeper/mips64el has unsatisfiable dependency
    • zookeeper-bin/mips64el has unsatisfiable dependency
    • python3-zookeeper/mipsel has unsatisfiable dependency
    • zookeeper-bin/mipsel has unsatisfiable dependency
    • python3-zookeeper/ppc64el has unsatisfiable dependency
    • zookeeper-bin/ppc64el has unsatisfiable dependency
    • python3-zookeeper/s390x has unsatisfiable dependency
    • zookeeper-bin/s390x has unsatisfiable dependency
    • Updating zookeeper would introduce bugs in testing: #984406, #990345
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/z/zookeeper.html
  • Additional info:
    • 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
    • 488 days old (needed 5 days)
• efax-gtk (- to 3.2.8-2.2)
  • Migration status for efax-gtk (- to 3.2.8-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating efax-gtk would introduce bugs in testing: #965505, #998956
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/efax-gtk.html
    • 489 days old (needed 5 days)
• jamin (- to 0.98.9~git20170111~199091~repack1-1.1)
  • Migration status for jamin (- to 0.98.9~git20170111~199091~repack1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jamin would introduce bugs in testing: #997327
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jamin.html
    • 489 days old (needed 5 days)
• mplayer-blue (- to 1.13-2)
  • Migration status for mplayer-blue (- to 1.13-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mplayer-blue mplayer (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mplayer-blue.html
    • 489 days old (needed 5 days)
• ncurses-hexedit (- to 0.9.7+orig-7.1)
  • Migration status for ncurses-hexedit (- to 0.9.7+orig-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ncurses-hexedit would introduce bugs in testing: #997184
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncurses-hexedit.html
    • autopkgtest for ncurses-hexedit/0.9.7+orig-7.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 489 days old (needed 2 days)
• netdiag (- to 1.2-1.1)
  • Migration status for netdiag (- to 1.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdiag would introduce bugs in testing: #997174
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdiag.html
    • 489 days old (needed 5 days)
• nextepc (- to 0.3.10+nods-4.1)
  • Migration status for nextepc (- to 0.3.10+nods-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nextepc would introduce bugs in testing: #984256
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextepc.html
    • autopkgtest for nextepc/0.3.10+nods-4.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 489 days old (needed 2 days)
• psensor (- to 1.1.5-1.3)
  • Migration status for psensor (- to 1.1.5-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psensor would introduce bugs in testing: #984298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psensor.html
    • 489 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
    • 489 days old (needed 5 days)
• xserver-xorg-video-trident (- to 1:1.3.8-2)
  • Migration status for xserver-xorg-video-trident (- to 1:1.3.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xserver-xorg-video-trident/amd64 has unsatisfiable dependency
    • xserver-xorg-video-trident/arm64 has unsatisfiable dependency
    • xserver-xorg-video-trident/armel has unsatisfiable dependency
    • xserver-xorg-video-trident/armhf has unsatisfiable dependency
    • xserver-xorg-video-trident/i386 has unsatisfiable dependency
    • xserver-xorg-video-trident/mips64el has unsatisfiable dependency
    • xserver-xorg-video-trident/mipsel has unsatisfiable dependency
    • xserver-xorg-video-trident/ppc64el has unsatisfiable dependency
    • Updating xserver-xorg-video-trident would introduce bugs in testing: #1005480
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-trident.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
    • 489 days old (needed 5 days)
• dvi2ps (- to 5.1j-1.4)
  • Migration status for dvi2ps (- to 5.1j-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvi2ps would introduce bugs in testing: #965502
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps.html
    • 490 days old (needed 5 days)
• dvi2ps-fontdesc-morisawa5 (- to 0.6)
  • Migration status for dvi2ps-fontdesc-morisawa5 (- to 0.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvi2ps-fontdesc-morisawa5 would introduce bugs in testing: #965506
    • Depends: dvi2ps-fontdesc-morisawa5 dvi2ps
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps-fontdesc-morisawa5.html
    • 490 days old (needed 5 days)
• paulstretch (- to 2.2-2-4.1)
  • Migration status for paulstretch (- to 2.2-2-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating paulstretch would introduce bugs in testing: #995847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paulstretch.html
    • 490 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
    • 491 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
    • 491 days old (needed 5 days)
• botch (- to 0.23-1)
  • Migration status for botch (- to 0.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • botch/armel has unsatisfiable dependency
    • botch/mips64el has unsatisfiable dependency
    • botch/mipsel has unsatisfiable dependency
    • Updating botch would introduce bugs in testing: #1006049
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/botch.html
    • autopkgtest for botch/0.23-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 491 days old (needed 2 days)
• golang-github-hashicorp-go-plugin (- to 1.0.1-3)
  • Migration status for golang-github-hashicorp-go-plugin (- to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-hashicorp-go-plugin would introduce bugs in testing: #1008434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-go-plugin.html
    • autopkgtest for golang-github-hashicorp-go-plugin/1.0.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 491 days old (needed 2 days)
• mailman3 (- to 3.3.3-1)
  • Migration status for mailman3 (- to 3.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailman3 would introduce bugs in testing: #995779, #996806, #997877
    • autopkgtest for mailman3/3.3.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • Depends: mailman3 mailman-hyperkitty
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman3.html
    • 491 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
    • 491 days old (needed 5 days)
• ruby-gitlab-pg-query (- to 1.3.1-2)
  • Migration status for ruby-gitlab-pg-query (- to 1.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-gitlab-pg-query/mips64el has unsatisfiable dependency
    • ruby-gitlab-pg-query/mipsel has unsatisfiable dependency
    • ruby-gitlab-pg-query/s390x has unsatisfiable dependency
    • Updating ruby-gitlab-pg-query would introduce bugs in testing: #981878
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for ruby-gitlab-pg-query/1.3.1-2: amd64: No test results, arm64: No test results, armhf: No test results
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-pg-query.html
    • uninstallable on arch s390x, not running autopkgtest there
    • 491 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
    • 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
    • autopkgtest for rust-libnotcurses-sys/2.1.8-1: amd64: No test results
    • 491 days old (needed 5 days)
• cadabra2 (- to 2.3.6.8-1)
  • Migration status for cadabra2 (- to 2.3.6.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cadabra2/amd64 has unsatisfiable dependency
    • cadabra2/arm64 has unsatisfiable dependency
    • cadabra2/armel has unsatisfiable dependency
    • cadabra2/armhf has unsatisfiable dependency
    • cadabra2/i386 has unsatisfiable dependency
    • cadabra2/mips64el has unsatisfiable dependency
    • cadabra2/mipsel has unsatisfiable dependency
    • cadabra2/ppc64el has unsatisfiable dependency
    • cadabra2/s390x has unsatisfiable dependency
    • Updating cadabra2 would introduce bugs in testing: #1008690
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cadabra2.html
  • Additional info:
    • 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
    • 492 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
    • cadvisor/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • cadvisor/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 492 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
    • 492 days old (needed 5 days)
• bzr-loom (- to 2.2.0+brz2)
  • Migration status for bzr-loom (- to 2.2.0+brz2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bzr-loom breezy-loom (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bzr-loom.html
    • 493 days old (needed 5 days)
• graftcp (- to 0.3.1+ds1-1)
  • Migration status for graftcp (- to 0.3.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graftcp would introduce bugs in testing: #981713
    • Not built on buildd: arch amd64 binaries uploaded by 073plan@gmail.com
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graftcp.html
    • 493 days old (needed 5 days)
• openscap (- to 1.3.4-1)
  • Migration status for openscap (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libopenscap-perl/amd64 has unsatisfiable dependency
    • python3-openscap/amd64 has unsatisfiable dependency
    • libopenscap-perl/arm64 has unsatisfiable dependency
    • python3-openscap/arm64 has unsatisfiable dependency
    • libopenscap-perl/armel has unsatisfiable dependency
    • python3-openscap/armel has unsatisfiable dependency
    • libopenscap-perl/armhf has unsatisfiable dependency
    • python3-openscap/armhf has unsatisfiable dependency
    • libopenscap-perl/i386 has unsatisfiable dependency
    • python3-openscap/i386 has unsatisfiable dependency
    • libopenscap-perl/mips64el has unsatisfiable dependency
    • python3-openscap/mips64el has unsatisfiable dependency
    • libopenscap-perl/mipsel has unsatisfiable dependency
    • python3-openscap/mipsel has unsatisfiable dependency
    • libopenscap-perl/ppc64el has unsatisfiable dependency
    • python3-openscap/ppc64el has unsatisfiable dependency
    • libopenscap-perl/s390x has unsatisfiable dependency
    • python3-openscap/s390x has unsatisfiable dependency
    • Updating openscap would introduce bugs in testing: #1000279, #990183, #993328
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/openscap.html
  • Additional info:
    • 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
    • 493 days old (needed 5 days)
• python-numpy-groupies (- to 0.9.13-1)
  • Migration status for python-numpy-groupies (- to 0.9.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by ginggs
    • Trying to remove package, not update it
    • Build-Depends(-Arch): python-numpy-groupies numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-numpy-groupies.html
    • autopkgtest for python-numpy-groupies/0.9.13-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 493 days old (needed 5 days)
• puppetdb (- to 6.2.0-5)
  • Migration status for puppetdb (- to 6.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating puppetdb would introduce bugs in testing: #981903, #990419, #990872
    • autopkgtest for puppetdb/6.2.0-5: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppetdb.html
    • 494 days old (needed 5 days)
• icingaweb2-module-ipl (- to 0.5.0-1)
  • Migration status for icingaweb2-module-ipl (- to 0.5.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: icingaweb2-module-ipl icingaweb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-ipl.html
    • 497 days old (needed 5 days)
• php-doctrine-bundle (- to 2.2.3-1)
  • Migration status for php-doctrine-bundle (- to 2.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-doctrine-bundle would introduce bugs in testing: #1002967, #996108
    • autopkgtest for php-doctrine-bundle/2.2.3-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-bundle.html
    • 497 days old (needed 5 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 497 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
    • 499 days old (needed 5 days)
• flask-migrate (- to 2.6.0-1)
  • Migration status for flask-migrate (- to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-migrate would introduce bugs in testing: #997349
    • Build-Depends(-Arch): flask-migrate flask-script
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-migrate.html
    • autopkgtest for flask-migrate/2.6.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 499 days old (needed 5 days)
• keepass2 (- to 2.47+dfsg-2)
  • Migration status for keepass2 (- to 2.47+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating keepass2 would introduce bugs in testing: #1000338, #1008022
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keepass2.html
    • 499 days old (needed 5 days)
• evdi (- to 1.9.0+dfsg-1)
  • Migration status for evdi (- to 1.9.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating evdi would introduce bugs in testing: #994892
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/evdi.html
  • Additional info:
    • autopkgtest for evdi/1.9.0+dfsg-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 500 days old (needed 5 days)
• bcbio (- to 1.2.5-1)
  • Migration status for bcbio (- to 1.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): bcbio salmon (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for bcbio/1.2.5-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Not a regression
    • 501 days old (needed 5 days)
• crossfire (- to 1.75.0-3)
  • Migration status for crossfire (- to 1.75.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crossfire would introduce bugs in testing: #1008637
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crossfire.html
    • 501 days old (needed 5 days)
• radare2-cutter (- to 1.12.0-1)
  • Migration status for radare2-cutter (- to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating radare2-cutter would introduce bugs in testing: #1011350
    • Build-Depends(-Arch): radare2-cutter radare2
    • Depends: radare2-cutter radare2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2-cutter.html
    • 502 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
    • 503 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:
    • srslte-core/amd64 has unsatisfiable dependency
    • srslte-core/arm64 has unsatisfiable dependency
    • srslte-core/armel has unsatisfiable dependency
    • srslte-core/armhf has unsatisfiable dependency
    • srslte-core/i386 has unsatisfiable dependency
    • srslte-core/mips64el has unsatisfiable dependency
    • srslte-core/mipsel has unsatisfiable dependency
    • srslte-core/ppc64el has unsatisfiable dependency
    • srslte-core/s390x has unsatisfiable dependency
    • Updating srslte would introduce bugs in testing: #982113, #993701
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/amd64
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/arm64
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/armel
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/armhf
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/i386
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/mips64el
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/mipsel
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/ppc64el
    • Impossible Depends: srslte -> libmbedcrypto3/2.16.11-0.3/s390x
  • Additional info:
    • Piuparts tested OK - 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 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
    • 503 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dugong.html
    • autopkgtest for python-dugong/3.8.1+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 504 days old (needed 2 days)
• hyperspy (- to 1.6.1-1)
  • Migration status for hyperspy (- to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperspy would introduce bugs in testing: #997475
    • Build-Depends(-Arch): hyperspy numba
    • Build-Depends(-Arch): hyperspy python-sparse
    • Depends: hyperspy python-sparse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperspy.html
    • 506 days old (needed 5 days)
• civicrm (- to 5.33.2+dfsg1-1)
  • Migration status for civicrm (- to 5.33.2+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: civicrm php-mail (not considered)
    • Invalidated by dependency
    • Depends: civicrm php-log
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/civicrm.html
    • 508 days old (needed 5 days)
• tulip (- to 5.4.0+dfsg-3)
  • Migration status for tulip (- to 5.4.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tulip would introduce bugs in testing: #1008850
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tulip.html
    • 508 days old (needed 5 days)
• python-django-registration (- to 2.2-5)
  • Migration status for python-django-registration (- to 2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-registration would introduce bugs in testing: #997331
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-registration.html
    • 509 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 13.3.1+dfsg-4)
  • Migration status for gitlab-ci-multi-runner (- to 13.3.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1005382, #1010452, #985377
    • gitlab-runner/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • 510 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 ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-manyminds-api2go.html
    • 510 days old (needed 5 days)
• volatildap (- to 1.5.0-1)
  • Migration status for volatildap (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating volatildap would introduce bugs in testing: #990335
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/volatildap.html
    • autopkgtest for volatildap/1.5.0-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 510 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
    • 512 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
    • 512 days old (needed 5 days)
• datapacker (- to 1.0.3)
  • Migration status for datapacker (- to 1.0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating datapacker would introduce bugs in testing: #965483, #999274
    • Build-Depends(-Arch): datapacker sgml2x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datapacker.html
    • 513 days old (needed 5 days)
• nomad-driver-podman (- to 0.1.0-2)
  • Migration status for nomad-driver-podman (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomad-driver-podman would introduce bugs in testing: #982632
    • Build-Depends(-Arch): nomad-driver-podman nomad
    • Built-Using: nomad-driver-podman golang-github-hashicorp-go-plugin
    • Built-Using: nomad-driver-podman nomad
    • Depends: nomad-driver-podman nomad
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomad-driver-podman.html
    • 513 days old (needed 5 days)
• rust-html2text (- to 0.2.1-2)
  • Migration status for rust-html2text (- to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-html2text-dev/amd64 has unsatisfiable dependency
    • librust-html2text-dev/arm64 has unsatisfiable dependency
    • librust-html2text-dev/armel has unsatisfiable dependency
    • librust-html2text-dev/armhf has unsatisfiable dependency
    • librust-html2text-dev/i386 has unsatisfiable dependency
    • librust-html2text-dev/mips64el has unsatisfiable dependency
    • librust-html2text-dev/mipsel has unsatisfiable dependency
    • librust-html2text-dev/ppc64el has unsatisfiable dependency
    • librust-html2text-dev/s390x has unsatisfiable dependency
    • Updating rust-html2text would introduce bugs in testing: #985264
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-html2text.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
    • 513 days old (needed 5 days)
• onionshare (- to 2.2-3)
  • Migration status for onionshare (- to 2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating onionshare would introduce bugs in testing: #997499
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onionshare.html
    • 516 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:
    • Updating subvertpy would introduce bugs in testing: #1009423
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subvertpy.html
    • autopkgtest for subvertpy/0.11.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 516 days old (needed 2 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ajg-form.html
    • autopkgtest for golang-github-ajg-form/1.5+git20160822.523a5da-1.1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 517 days old (needed 5 days)
• gost (- to 0.1.0+git20181204.5afeda5e-1.1)
  • Migration status for gost (- to 0.1.0+git20181204.5afeda5e-1.1): 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.0+git20181204.5afeda5e-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 517 days old (needed 2 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
    • 517 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
    • 517 days old (needed 5 days)
• zemberek-server (- to 0.7.1-12.3)
  • Migration status for zemberek-server (- to 0.7.1-12.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zemberek-server would introduce bugs in testing: #965921
    • Build-Depends-Indep: zemberek-server zemberek
    • Depends: zemberek-server zemberek
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zemberek-server.html
    • 517 days old (needed 5 days)
• asterisk-prompt-fr-armelle (- to 20070613-2.1)
  • Migration status for asterisk-prompt-fr-armelle (- to 20070613-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk-prompt-fr-armelle would introduce bugs in testing: #965429, #999033
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-prompt-fr-armelle.html
    • 518 days old (needed 5 days)
• class.js (- to 1.0.0+dfsg-2.1)
  • Migration status for class.js (- to 1.0.0+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating class.js would introduce bugs in testing: #979888
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/class.js.html
    • 518 days old (needed 5 days)
• crossfire-maps-small (- to 1.5.0-3.1)
  • Migration status for crossfire-maps-small (- to 1.5.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crossfire-maps-small would introduce bugs in testing: #965474
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crossfire-maps-small.html
    • 518 days old (needed 5 days)
• golang-github-twstrike-gotk3adapter (- to 0.0~git20170505.0.901a95d+ds-3.1)
  • Migration status for golang-github-twstrike-gotk3adapter (- to 0.0~git20170505.0.901a95d+ds-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-twstrike-gotk3adapter would introduce bugs in testing: #997717
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twstrike-gotk3adapter.html
    • 518 days old (needed 5 days)
• initz (- to 0.0.11+20030603cvs-17.3)
  • Migration status for initz (- to 0.0.11+20030603cvs-17.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating initz would introduce bugs in testing: #965594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/initz.html
    • 518 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
    • 518 days old (needed 5 days)
• omnievents (- to 1:2.6.2-5.1)
  • Migration status for omnievents (- to 1:2.6.2-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating omnievents would introduce bugs in testing: #965754
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/omnievents.html
    • 518 days old (needed 5 days)
• pentium-builder (- to 0.21+nmu1)
  • Migration status for pentium-builder (- to 0.21+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pentium-builder would introduce bugs in testing: #998932
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pentium-builder.html
    • 518 days old (needed 5 days)
• ruby-omniauth-jwt (- to 0.0.2-1.1)
  • Migration status for ruby-omniauth-jwt (- to 0.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-jwt would introduce bugs in testing: #999717
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-jwt.html
    • autopkgtest for ruby-omniauth-jwt/0.0.2-1.1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 518 days old (needed 5 days)
• slick (- to 1.8.0-1.1)
  • Migration status for slick (- to 1.8.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slick would introduce bugs in testing: #979954
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slick.html
    • 518 days old (needed 5 days)
• smtpprox (- to 1.2-1.1)
  • Migration status for smtpprox (- to 1.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smtpprox would introduce bugs in testing: #981670
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smtpprox.html
    • 518 days old (needed 5 days)
• smtpprox-loopprevent (- to 0.1-1.1)
  • Migration status for smtpprox-loopprevent (- to 0.1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: smtpprox-loopprevent smtpprox (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smtpprox-loopprevent.html
    • 518 days old (needed 5 days)
• wims-moodle (- to 4.0-18.1)
  • Migration status for wims-moodle (- to 4.0-18.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wims-moodle wims (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wims-moodle.html
    • 518 days old (needed 5 days)
• asterisk-prompt-fr-proformatique (- to 20070706-1.4-2.1)
  • Migration status for asterisk-prompt-fr-proformatique (- to 20070706-1.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk-prompt-fr-proformatique would introduce bugs in testing: #965421, #999175
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-prompt-fr-proformatique.html
    • 519 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
    • 519 days old (needed 5 days)
• jruby-maven-plugins (- to 1.1.5+ds1-2.1)
  • Migration status for jruby-maven-plugins (- to 1.1.5+ds1-2.1): 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
    • 519 days old (needed 5 days)
• libnet-google-safebrowsing2-perl (- to 1.07-6.1)
  • Migration status for libnet-google-safebrowsing2-perl (- to 1.07-6.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libnet-google-safebrowsing2-perl libtext-string-hexconvert-perl (not considered)
    • Depends: libnet-google-safebrowsing2-perl libtext-string-hexconvert-perl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): libnet-google-safebrowsing2-perl libnet-ipaddress-perl
    • Depends: libnet-google-safebrowsing2-perl libnet-ipaddress-perl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-google-safebrowsing2-perl.html
    • 519 days old (needed 5 days)
• mikutter (- to 4.1.3+dfsg1-1)
  • Migration status for mikutter (- to 4.1.3+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mikutter/amd64 has unsatisfiable dependency
    • mikutter/arm64 has unsatisfiable dependency
    • Updating mikutter would introduce bugs in testing: #997819
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mikutter.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 519 days old (needed 5 days)
• plait (- to 1.6.2-1.1)
  • Migration status for plait (- to 1.6.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plait would introduce bugs in testing: #965781, #999023
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plait.html
    • 519 days old (needed 5 days)
• rtpg (- to 0.2.11-3.1)
  • Migration status for rtpg (- to 0.2.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rtpg would introduce bugs in testing: #965806
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rtpg.html
    • 519 days old (needed 5 days)
• ruby-flot-rails (- to 0.0.7-1.1)
  • Migration status for ruby-flot-rails (- to 0.0.7-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-flot-rails would introduce bugs in testing: #985880
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-flot-rails.html
    • autopkgtest for ruby-flot-rails/0.0.7-1.1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 519 days old (needed 5 days)
• sendpage (- to 1.0.3-1.1)
  • Migration status for sendpage (- to 1.0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sendpage would introduce bugs in testing: #965814, #999051
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sendpage.html
    • 519 days old (needed 5 days)
• yample (- to 0.30-3.1)
  • Migration status for yample (- to 0.30-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yample would introduce bugs in testing: #965906
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yample.html
    • 519 days old (needed 5 days)
• couriergraph (- to 0.25-4.5)
  • Migration status for couriergraph (- to 0.25-4.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating couriergraph would introduce bugs in testing: #999063
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/couriergraph.html
    • 520 days old (needed 5 days)
• devtodo (- to 0.1.20+git20200830.0ad52b0-1)
  • Migration status for devtodo (- to 0.1.20+git20200830.0ad52b0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating devtodo would introduce bugs in testing: #979101
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devtodo.html
    • autopkgtest for devtodo/0.1.20+git20200830.0ad52b0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 520 days old (needed 2 days)
• gle-graphics (- to 4.2.5-9)
  • Migration status for gle-graphics (- to 4.2.5-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gle-graphics would introduce bugs in testing: #984153
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gle-graphics.html
    • 520 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 520 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 520 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 520 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 520 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
    • 520 days old (needed 5 days)
• libnet-ipaddress-perl (- to 1.10-3.1)
  • Migration status for libnet-ipaddress-perl (- to 1.10-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libnet-ipaddress-perl would introduce bugs in testing: #979427
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-ipaddress-perl.html
    • 520 days old (needed 5 days)
• libtext-string-hexconvert-perl (- to 0.01-2.1)
  • Migration status for libtext-string-hexconvert-perl (- to 0.01-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtext-string-hexconvert-perl would introduce bugs in testing: #979504
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtext-string-hexconvert-perl.html
    • 520 days old (needed 5 days)
• proj-ps-doc (- to 4.3.3-5.1)
  • Migration status for proj-ps-doc (- to 4.3.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating proj-ps-doc would introduce bugs in testing: #999293
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proj-ps-doc.html
    • 520 days old (needed 5 days)
• ruby-gettext-i18n-rails-js (- to 1.3.0+dfsg-2.1)
  • Migration status for ruby-gettext-i18n-rails-js (- to 1.3.0+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gettext-i18n-rails-js would introduce bugs in testing: #1005625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gettext-i18n-rails-js.html
    • autopkgtest for ruby-gettext-i18n-rails-js/1.3.0+dfsg-2.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 520 days old (needed 2 days)
• ruby-omniauth-bitbucket (- to 0.0.2-1.1)
  • Migration status for ruby-omniauth-bitbucket (- to 0.0.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): ruby-omniauth-bitbucket ruby-omniauth-oauth (not considered)
    • Depends: ruby-omniauth-bitbucket ruby-omniauth-oauth (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-bitbucket.html
    • autopkgtest for ruby-omniauth-bitbucket/0.0.2-1.1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 520 days old (needed 5 days)
• sisc (- to 1.16.6-1.2)
  • Migration status for sisc (- to 1.16.6-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sisc would introduce bugs in testing: #999294
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sisc.html
    • 520 days old (needed 5 days)
• torrus (- to 3.00-1.1)
  • Migration status for torrus (- to 3.00-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: torrus libgit-objectstore-perl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/torrus.html
    • 520 days old (needed 5 days)
• zemberek (- to 2.1.1-8.3)
  • Migration status for zemberek (- to 2.1.1-8.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zemberek would introduce bugs in testing: #965920
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zemberek.html
    • 520 days old (needed 5 days)
• deps (- to 0.13-4.1)
  • Migration status for deps (- to 0.13-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deps would introduce bugs in testing: #999186
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deps.html
    • 521 days old (needed 5 days)
• gpsshogi (- to 0.7.0-3)
  • Migration status for gpsshogi (- to 0.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by dirson, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpsshogi.html
    • 521 days old (needed 5 days)
• kindleclip (- to 0.6-1.1)
  • Migration status for kindleclip (- to 0.6-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kindleclip ruby-gnome (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kindleclip.html
    • 521 days old (needed 5 days)
• libstatistics-r-perl (- to 0.24-1.1)
  • Migration status for libstatistics-r-perl (- to 0.24-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libstatistics-r-perl would introduce bugs in testing: #1008437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libstatistics-r-perl.html
    • 521 days old (needed 5 days)
• octave-tisean (- to 0.2.3.hg.2019.08.26-1)
  • Migration status for octave-tisean (- to 0.2.3.hg.2019.08.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-tisean/armel has unsatisfiable dependency
    • octave-tisean/s390x has unsatisfiable dependency
    • Updating octave-tisean would introduce bugs in testing: #874116
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-tisean.html
    • uninstallable on arch s390x, not running autopkgtest there
    • autopkgtest for octave-tisean/0.2.3.hg.2019.08.26-1: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 521 days old (needed 2 days)
• openclonk (- to 8.1-2)
  • Migration status for openclonk (- to 8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openclonk would introduce bugs in testing: #984274
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openclonk.html
    • 521 days old (needed 5 days)
• pudb (- to 2020.1-1)
  • Migration status for pudb (- to 2020.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pudb would introduce bugs in testing: #1005854
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pudb.html
    • autopkgtest for pudb/2020.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 521 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-tools.html
    • 521 days old (needed 5 days)
• ruby-omniauth-crowd (- to 2.4.0-1.1)
  • Migration status for ruby-omniauth-crowd (- to 2.4.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-crowd would introduce bugs in testing: #999714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-crowd.html
    • autopkgtest for ruby-omniauth-crowd/2.4.0-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 521 days old (needed 2 days)
• ruby-representable (- to 3.0.4-1.1)
  • Migration status for ruby-representable (- to 3.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): ruby-representable ruby-virtus (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-representable.html
    • autopkgtest for ruby-representable/3.0.4-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 521 days old (needed 2 days)
• xfce4-screensaver (- to 4.16.0-1)
  • Migration status for xfce4-screensaver (- to 4.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfce4-screensaver would introduce bugs in testing: #919348
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-screensaver.html
    • 521 days old (needed 5 days)
• dailystrips (- to 1.0.28-11.1)
  • Migration status for dailystrips (- to 1.0.28-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dailystrips would introduce bugs in testing: #965482
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dailystrips.html
    • 522 days old (needed 5 days)
• hotswap (- to 0.4.0-15.1)
  • Migration status for hotswap (- to 0.4.0-15.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hotswap would introduce bugs in testing: #980338
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hotswap.html
    • 522 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
    • 522 days old (needed 5 days)
• konfont (- to 0.1-8.1)
  • Migration status for konfont (- to 0.1-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating konfont would introduce bugs in testing: #999195
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/konfont.html
    • 522 days old (needed 5 days)
• libsnmp-multi-perl (- to 2.1-4.1)
  • Migration status for libsnmp-multi-perl (- to 2.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsnmp-multi-perl would introduce bugs in testing: #965683, #979304, #998992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsnmp-multi-perl.html
    • 522 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
    • 522 days old (needed 5 days)
• messagingmenu-sharp (- to 1.0.1-1.1)
  • Migration status for messagingmenu-sharp (- to 1.0.1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: messagingmenu-sharp ayatana-indicator-messages (not considered)
    • Depends: messagingmenu-sharp ayatana-indicator-messages (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/messagingmenu-sharp.html
    • 522 days old (needed 5 days)
• msort (- to 8.53-2.3)
  • Migration status for msort (- to 8.53-2.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): msort libuninum (not considered)
    • Depends: msort libuninum (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msort.html
    • 522 days old (needed 5 days)
• pct-scanner-scripts (- to 0.0.4-3.1)
  • Migration status for pct-scanner-scripts (- to 0.0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pct-scanner-scripts would introduce bugs in testing: #999239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pct-scanner-scripts.html
    • 522 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
    • 522 days old (needed 5 days)
• poco-doc (- to 1.3.6-1.1)
  • Migration status for poco-doc (- to 1.3.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating poco-doc would introduce bugs in testing: #965782, #999047
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poco-doc.html
    • 522 days old (needed 5 days)
• ruby-omniauth-kerberos (- to 0.3.0-3.1)
  • Migration status for ruby-omniauth-kerberos (- to 0.3.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): ruby-omniauth-kerberos ruby-omniauth-multipassword (not considered)
    • Depends: ruby-omniauth-kerberos ruby-omniauth-multipassword (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-kerberos.html
    • autopkgtest for ruby-omniauth-kerberos/0.3.0-3.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 522 days old (needed 2 days)
• ruby-omniauth-multipassword (- to 0.4.2-1.1)
  • Migration status for ruby-omniauth-multipassword (- to 0.4.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-multipassword would introduce bugs in testing: #999719
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-multipassword.html
    • autopkgtest for ruby-omniauth-multipassword/0.4.2-1.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 522 days old (needed 2 days)
• ruby-omniauth-oauth (- to 1.1.0-2.1)
  • Migration status for ruby-omniauth-oauth (- to 1.1.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-oauth would introduce bugs in testing: #999720
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-oauth.html
    • 522 days old (needed 5 days)
• webmagick (- to 2.02-11.1)
  • Migration status for webmagick (- to 2.02-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webmagick would introduce bugs in testing: #897397, #999111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webmagick.html
    • 522 days old (needed 5 days)
• dns-browse (- to 1.9-8.1)
  • Migration status for dns-browse (- to 1.9-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dns-browse would introduce bugs in testing: #965494, #999143
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dns-browse.html
    • 523 days old (needed 5 days)
• keepass2-plugin-keepasshttp (- to 1.8.4.2+dfsg1-2.1)
  • Migration status for keepass2-plugin-keepasshttp (- to 1.8.4.2+dfsg1-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): keepass2-plugin-keepasshttp keepass2 (not considered)
    • Depends: keepass2-plugin-keepasshttp keepass2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keepass2-plugin-keepasshttp.html
    • 523 days old (needed 5 days)
• libjama (- to 1.2.4-2.1)
  • Migration status for libjama (- to 1.2.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libjama would introduce bugs in testing: #999126
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjama.html
    • 523 days old (needed 5 days)
• slack (- to 1:0.15.2-9.1)
  • Migration status for slack (- to 1:0.15.2-9.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slack would introduce bugs in testing: #965820
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slack.html
    • 523 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
    • 523 days old (needed 5 days)
• covered (- to 0.7.10-3.1)
  • Migration status for covered (- to 0.7.10-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating covered would introduce bugs in testing: #1004026
    • Build-Depends(-Arch): covered gplcver
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/covered.html
    • 524 days old (needed 5 days)
• cvsutils (- to 0.2.5-1.1)
  • Migration status for cvsutils (- to 0.2.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cvsutils would introduce bugs in testing: #965479
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvsutils.html
    • 524 days old (needed 5 days)
• dvi2ps-fontdata (- to 1.0.1-3.1)
  • Migration status for dvi2ps-fontdata (- to 1.0.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvi2ps-fontdata would introduce bugs in testing: #965503
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps-fontdata.html
    • 524 days old (needed 5 days)
• graphmonkey (- to 1.7-4.1)
  • Migration status for graphmonkey (- to 1.7-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graphmonkey would introduce bugs in testing: #965568, #999187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graphmonkey.html
    • 524 days old (needed 5 days)
• grub-splashimages (- to 1.2.3+nmu1)
  • Migration status for grub-splashimages (- to 1.2.3+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grub-splashimages would introduce bugs in testing: #965569
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub-splashimages.html
    • 524 days old (needed 5 days)
• ink-generator (- to 0.4-2.1)
  • Migration status for ink-generator (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ink-generator would introduce bugs in testing: #998952
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ink-generator.html
    • 524 days old (needed 5 days)
• libphp-jpgraph (- to 1.5.2-13.1)
  • Migration status for libphp-jpgraph (- to 1.5.2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libphp-jpgraph would introduce bugs in testing: #631280, #965677
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libphp-jpgraph.html
    • 524 days old (needed 5 days)
• openoffice.org-hyphenation-pl (- to 1:3.0a-4.1)
  • Migration status for openoffice.org-hyphenation-pl (- to 1:3.0a-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openoffice.org-hyphenation-pl would introduce bugs in testing: #999193
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openoffice.org-hyphenation-pl.html
    • 524 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
    • 524 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:
    • Updating resvg would introduce bugs in testing: #1002188
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mipsel: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-pico-args-0.3+default-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resvg.html
    • 524 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
    • 524 days old (needed 5 days)
• xfonts-nexus (- to 0.0.2-17.1)
  • Migration status for xfonts-nexus (- to 0.0.2-17.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfonts-nexus would introduce bugs in testing: #965892
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfonts-nexus.html
    • 524 days old (needed 5 days)
• ctpl (- to 0.3.4+dfsg-1.1)
  • Migration status for ctpl (- to 0.3.4+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ctpl would introduce bugs in testing: #997514
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctpl.html
    • 525 days old (needed 5 days)
• grub2-splashimages (- to 1.0.1+nmu2)
  • Migration status for grub2-splashimages (- to 1.0.1+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grub2-splashimages would introduce bugs in testing: #965570
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub2-splashimages.html
    • 525 days old (needed 5 days)
• notify-sharp (- to 0.4.0~r3032-7.1)
  • Migration status for notify-sharp (- to 0.4.0~r3032-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notify-sharp would introduce bugs in testing: #965748
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notify-sharp.html
    • 525 days old (needed 5 days)
• ns2 (- to 2.35+dfsg-3.1)
  • Migration status for ns2 (- to 2.35+dfsg-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ns2 would introduce bugs in testing: #984253
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ns2.html
    • 525 days old (needed 5 days)
• ogre-1.9 (- to 1.9.0+dfsg1-12.1)
  • Migration status for ogre-1.9 (- to 1.9.0+dfsg1-12.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ogre-1.9 blender (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogre-1.9.html
    • 525 days old (needed 5 days)
• oinkmaster (- to 2.0-4.1)
  • Migration status for oinkmaster (- to 2.0-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oinkmaster would introduce bugs in testing: #965755, #999038
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oinkmaster.html
    • 525 days old (needed 5 days)
• openoffice.org-thesaurus-pl (- to 1.5-4.1)
  • Migration status for openoffice.org-thesaurus-pl (- to 1.5-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openoffice.org-thesaurus-pl would introduce bugs in testing: #998968
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openoffice.org-thesaurus-pl.html
    • 525 days old (needed 5 days)
• pkg-mozilla-archive-keyring (- to 1.2+nmu1)
  • Migration status for pkg-mozilla-archive-keyring (- to 1.2+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pkg-mozilla-archive-keyring would introduce bugs in testing: #943607
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pkg-mozilla-archive-keyring.html
    • 525 days old (needed 5 days)
• ruby-pathutil (- to 0.16.1-1.1)
  • Migration status for ruby-pathutil (- to 0.16.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-pathutil would introduce bugs in testing: #1001022
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-pathutil.html
    • autopkgtest for ruby-pathutil/0.16.1-1.1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 525 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
    • 525 days old (needed 5 days)
• xfonts-cyrillic (- to 1:1.0.5)
  • Migration status for xfonts-cyrillic (- to 1:1.0.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfonts-cyrillic would introduce bugs in testing: #999227
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfonts-cyrillic.html
    • 525 days old (needed 5 days)
• golang-code.gitea-git (- to 0.0~git20190411.63b74d4+ds-1)
  • Migration status for golang-code.gitea-git (- to 0.0~git20190411.63b74d4+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-code.gitea-git would introduce bugs in testing: #982830
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-code.gitea-git.html
    • autopkgtest for golang-code.gitea-git/0.0~git20190411.63b74d4+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 527 days old (needed 2 days)
• libdigidoc (- to 3.10.5-2)
  • Migration status for libdigidoc (- to 3.10.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdigidoc would introduce bugs in testing: #1006389
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdigidoc.html
    • 527 days old (needed 5 days)
• oss4 (- to 4.2-build2017-2)
  • Migration status for oss4 (- to 4.2-build2017-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oss4 would introduce bugs in testing: #796636, #919246
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/oss4.html
  • Additional info:
    • 527 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
    • 527 days old (needed 5 days)
• mailman-hyperkitty (- to 1.1.0-10)
  • Migration status for mailman-hyperkitty (- to 1.1.0-10): 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.1.0-10: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 529 days old (needed 2 days)
• dbmix (- to 0.9.8-8)
  • Migration status for dbmix (- to 0.9.8-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dbmix would introduce bugs in testing: #965490, #998988
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbmix.html
    • 530 days old (needed 5 days)
• libcommoncpp2 (- to 1.8.1-10)
  • Migration status for libcommoncpp2 (- to 1.8.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcommoncpp2 would introduce bugs in testing: #984096, #998889
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommoncpp2.html
    • 531 days old (needed 5 days)
• golang-github-hashicorp-go-tfe (- to 0.11.1+git20201207.19dc0b8-2)
  • Migration status for golang-github-hashicorp-go-tfe (- to 0.11.1+git20201207.19dc0b8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-hashicorp-go-tfe golang-github-hashicorp-go-slug (not considered)
    • Depends: golang-github-hashicorp-go-tfe golang-github-hashicorp-go-slug (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-go-tfe.html
    • autopkgtest for golang-github-hashicorp-go-tfe/0.11.1+git20201207.19dc0b8-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 532 days old (needed 2 days)
• fonts-myanmar (- to 0.0-1~exp2.1)
  • Migration status for fonts-myanmar (- to 0.0-1~exp2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fonts-myanmar/0.0-1~exp2.1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-myanmar.html
    • 533 days old (needed 5 days)
• rust-spotify-tui (- to 0.11.0-4)
  • Migration status for rust-spotify-tui (- to 0.11.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-spotify-tui would introduce bugs in testing: #997685
    • Build-Depends(-Arch): rust-spotify-tui rust-clipboard
    • Build-Depends(-Arch): rust-spotify-tui rust-rspotify
    • Build-Depends(-Arch): rust-spotify-tui rust-tui
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-spotify-tui.html
    • 533 days old (needed 5 days)
• julia (- to 1.5.3+dfsg-3)
  • Migration status for julia (- to 1.5.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • julia/amd64 has unsatisfiable dependency
    • libjulia1/amd64 has unsatisfiable dependency
    • julia/arm64 has unsatisfiable dependency
    • libjulia1/arm64 has unsatisfiable dependency
    • julia/armhf has unsatisfiable dependency
    • libjulia1/armhf has unsatisfiable dependency
    • julia/i386 has unsatisfiable dependency
    • libjulia1/i386 has unsatisfiable dependency
    • julia/ppc64el has unsatisfiable dependency
    • libjulia1/ppc64el has unsatisfiable dependency
    • Updating julia would introduce bugs in testing: #1009029, #974779
    • julia unsatisfiable Build-Depends(-Arch) on amd64: llvm-9-dev
    • julia unsatisfiable Build-Depends(-Arch) on arm64: llvm-9-dev
    • julia unsatisfiable Build-Depends(-Arch) on armhf: llvm-9-dev
    • julia unsatisfiable Build-Depends(-Arch) on i386: llvm-9-dev
    • julia unsatisfiable Build-Depends(-Arch) on ppc64el: llvm-9-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/julia.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
    • autopkgtest for julia/1.5.3+dfsg-3: s390x: Not a regression
    • 534 days old (needed 5 days)
• gauche (- to 0.9.10-3)
  • Migration status for gauche (- to 0.9.10-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche slib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche.html
    • 535 days old (needed 5 days)
• acmetool (- to 0.2.1-4)
  • Migration status for acmetool (- to 0.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating acmetool would introduce bugs in testing: #997130
    • acmetool/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • acmetool/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acmetool.html
    • autopkgtest for acmetool/0.2.1-4: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 536 days old (needed 5 days)
• meterec (- to 0.9.3-1)
  • Migration status for meterec (- to 0.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating meterec would introduce bugs in testing: #997183
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meterec.html
    • 536 days old (needed 5 days)
• pytorch-text (- to 0.8.1-1)
  • Migration status for pytorch-text (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torchtext/amd64 has unsatisfiable dependency
    • python3-torchtext/arm64 has unsatisfiable dependency
    • python3-torchtext/ppc64el has unsatisfiable dependency
    • python3-torchtext/s390x has unsatisfiable dependency
    • Updating pytorch-text would introduce bugs in testing: #1008924
    • Build-Depends(-Arch): pytorch-text pytorch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-text.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
    • 536 days old (needed 5 days)
• rust-tui (- to 0.9.0-1)
  • Migration status for rust-tui (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tui+crossterm-dev/amd64 has unsatisfiable dependency
    • librust-tui+curses-dev/amd64 has unsatisfiable dependency
    • librust-tui+easycurses-dev/amd64 has unsatisfiable dependency
    • librust-tui+pancurses-dev/amd64 has unsatisfiable dependency
    • librust-tui+rustbox-dev/amd64 has unsatisfiable dependency
    • librust-tui-dev/amd64 has unsatisfiable dependency
    • librust-tui+crossterm-dev/arm64 has unsatisfiable dependency
    • librust-tui+curses-dev/arm64 has unsatisfiable dependency
    • librust-tui+easycurses-dev/arm64 has unsatisfiable dependency
    • librust-tui+pancurses-dev/arm64 has unsatisfiable dependency
    • librust-tui+rustbox-dev/arm64 has unsatisfiable dependency
    • librust-tui-dev/arm64 has unsatisfiable dependency
    • librust-tui+crossterm-dev/armel has unsatisfiable dependency
    • librust-tui+curses-dev/armel has unsatisfiable dependency
    • librust-tui+easycurses-dev/armel has unsatisfiable dependency
    • librust-tui+pancurses-dev/armel has unsatisfiable dependency
    • librust-tui+rustbox-dev/armel has unsatisfiable dependency
    • librust-tui-dev/armel has unsatisfiable dependency
    • librust-tui+crossterm-dev/armhf has unsatisfiable dependency
    • librust-tui+curses-dev/armhf has unsatisfiable dependency
    • librust-tui+easycurses-dev/armhf has unsatisfiable dependency
    • librust-tui+pancurses-dev/armhf has unsatisfiable dependency
    • librust-tui+rustbox-dev/armhf has unsatisfiable dependency
    • librust-tui-dev/armhf has unsatisfiable dependency
    • librust-tui+crossterm-dev/i386 has unsatisfiable dependency
    • librust-tui+curses-dev/i386 has unsatisfiable dependency
    • librust-tui+easycurses-dev/i386 has unsatisfiable dependency
    • librust-tui+pancurses-dev/i386 has unsatisfiable dependency
    • librust-tui+rustbox-dev/i386 has unsatisfiable dependency
    • librust-tui-dev/i386 has unsatisfiable dependency
    • librust-tui+crossterm-dev/mips64el has unsatisfiable dependency
    • librust-tui+curses-dev/mips64el has unsatisfiable dependency
    • librust-tui+easycurses-dev/mips64el has unsatisfiable dependency
    • librust-tui+pancurses-dev/mips64el has unsatisfiable dependency
    • librust-tui+rustbox-dev/mips64el has unsatisfiable dependency
    • librust-tui-dev/mips64el has unsatisfiable dependency
    • librust-tui+crossterm-dev/mipsel has unsatisfiable dependency
    • librust-tui+curses-dev/mipsel has unsatisfiable dependency
    • librust-tui+easycurses-dev/mipsel has unsatisfiable dependency
    • librust-tui+pancurses-dev/mipsel has unsatisfiable dependency
    • librust-tui+rustbox-dev/mipsel has unsatisfiable dependency
    • librust-tui-dev/mipsel has unsatisfiable dependency
    • librust-tui+crossterm-dev/ppc64el has unsatisfiable dependency
    • librust-tui+curses-dev/ppc64el has unsatisfiable dependency
    • librust-tui+easycurses-dev/ppc64el has unsatisfiable dependency
    • librust-tui+pancurses-dev/ppc64el has unsatisfiable dependency
    • librust-tui+rustbox-dev/ppc64el has unsatisfiable dependency
    • librust-tui-dev/ppc64el has unsatisfiable dependency
    • librust-tui+crossterm-dev/s390x has unsatisfiable dependency
    • librust-tui+curses-dev/s390x has unsatisfiable dependency
    • librust-tui+easycurses-dev/s390x has unsatisfiable dependency
    • librust-tui+pancurses-dev/s390x has unsatisfiable dependency
    • librust-tui+rustbox-dev/s390x has unsatisfiable dependency
    • librust-tui-dev/s390x has unsatisfiable dependency
    • Updating rust-tui would introduce bugs in testing: #984865
    • rust-tui unsatisfiable Build-Depends(-Arch) on amd64: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on arm64: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on armel: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on armhf: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on i386: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on mips64el: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on mipsel: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itertools-0.9+default-dev
    • rust-tui unsatisfiable Build-Depends(-Arch) on s390x: librust-itertools-0.9+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tui.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
    • 537 days old (needed 5 days)
• rust-x11-clipboard (- to 0.5.1-3)
  • Migration status for rust-x11-clipboard (- to 0.5.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-x11-clipboard rust-xcb (not considered)
    • Depends: rust-x11-clipboard rust-xcb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-x11-clipboard.html
    • autopkgtest for rust-x11-clipboard/0.5.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 537 days old (needed 2 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
    • Build-Depends(-Arch): adabrowse asis
    • Depends: adabrowse asis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adabrowse.html
    • autopkgtest for adabrowse/4.0.3-14: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 538 days old (needed 2 days)
• php-horde-ansel (- to 3.0.10+debian1-2)
  • Migration status for php-horde-ansel (- to 3.0.10+debian1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-ansel would introduce bugs in testing: #1003648
    • autopkgtest for php-horde-ansel/3.0.10+debian1-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Regression ♻ (reference ♻)
    • Depends: php-horde-ansel php-horde
    • Depends: php-horde-ansel php-horde-auth
    • Depends: php-horde-ansel php-horde-content
    • Depends: php-horde-ansel php-horde-core
    • Depends: php-horde-ansel php-horde-form
    • Depends: php-horde-ansel php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ansel.html
    • 539 days old (needed 5 days)
• xfractint (- to 20.4.10-2.1)
  • Migration status for xfractint (- to 20.4.10-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfractint would introduce bugs in testing: #999017
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 539 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
    • autopkgtest for spyder-reports/0.1.1-4: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/spyder-reports.html
    • 540 days old (needed 5 days)
• gitlab (- to 13.4.7-2)
  • Migration status for gitlab (- to 13.4.7-2): 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: #915050, #983480, #983915, #983924, #984828, #991744, #995073, #998193
    • autopkgtest for gitlab/13.4.7-2: armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • 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
    • 541 days old (needed 5 days)
• pytorch-audio (- to 0.7.2-1)
  • Migration status for pytorch-audio (- to 0.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torchaudio/amd64 has unsatisfiable dependency
    • python3-torchaudio/arm64 has unsatisfiable dependency
    • python3-torchaudio/ppc64el has unsatisfiable dependency
    • python3-torchaudio/s390x has unsatisfiable dependency
    • Updating pytorch-audio would introduce bugs in testing: #1008922
    • Build-Depends(-Arch): pytorch-audio pytorch
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-audio.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
    • 541 days old (needed 5 days)
• pytorch-vision (- to 0.8.2-1)
  • Migration status for pytorch-vision (- to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torchvision/amd64 has unsatisfiable dependency
    • python3-torchvision/arm64 has unsatisfiable dependency
    • python3-torchvision/ppc64el has unsatisfiable dependency
    • python3-torchvision/s390x has unsatisfiable dependency
    • Updating pytorch-vision would introduce bugs in testing: #1008925
    • Build-Depends(-Arch): pytorch-vision pytorch
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-vision.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
    • 541 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
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 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/c/clippoly.html
    • 543 days old (needed 5 days)
• php-laravel-lumen-framework (- to 6.3.5-2)
  • Migration status for php-laravel-lumen-framework (- to 6.3.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-laravel-lumen-framework/amd64 has unsatisfiable dependency
    • php-laravel-lumen-framework/arm64 has unsatisfiable dependency
    • Updating php-laravel-lumen-framework would introduce bugs in testing: #1000696
    • autopkgtest for php-laravel-lumen-framework/6.3.5-2: armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
    • Build-Depends(-Arch): php-laravel-lumen-framework php-laravel-framework
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-laravel-lumen-framework.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 543 days old (needed 5 days)
• rust-grcov (- to 0.5.15-2)
  • Migration status for rust-grcov (- to 0.5.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-grcov-dev/amd64 has unsatisfiable dependency
    • rust-grcov unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on amd64: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on amd64: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on arm64: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on arm64: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on armel: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on armel: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on armhf: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on armhf: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on i386: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on i386: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on mips64el: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on mips64el: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on mipsel: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on mipsel: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on ppc64el: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on ppc64el: librust-simplelog-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-0.7+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on s390x: librust-md-5-0.9+default-dev
    • rust-grcov unsatisfiable Build-Depends(-Arch) on s390x: librust-simplelog-0.7+default-dev
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on mipsel
    • missing build on ppc64el
    • 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:ppc64el 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/r/rust-grcov.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 543 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:
    • Updating adacontrol would introduce bugs in testing: #1008982
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): adacontrol -> libgnatcoll19-dev/21.0.0-4/s390x
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/amd64
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/arm64
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/armel
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/armhf
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/i386
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/mips64el
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/mipsel
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/ppc64el
    • Impossible Depends: adacontrol -> libgnatcoll19/21.0.0-4/s390x
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/amd64
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/arm64
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/armel
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/armhf
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/i386
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/mips64el
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/mipsel
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/ppc64el
    • Impossible Depends: adacontrol -> libgnatprj8/2021.0.0.0778b109-5/s390x
    • Build-Depends(-Arch): adacontrol asis
    • Depends: adacontrol asis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adacontrol.html
    • autopkgtest for adacontrol/1.21r6b-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 544 days old (needed 2 days)
• asis (- to 2019-5)
  • Migration status for asis (- to 2019-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asis would introduce bugs in testing: #1008979
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): asis -> libgnatcoll19-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): asis -> libxmlada-dom10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): asis -> libxmlada-input10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): asis -> libxmlada-sax10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/amd64
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/arm64
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/armel
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/armhf
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/i386
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/mips64el
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/mipsel
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/ppc64el
    • Impossible Build-Depends(-Arch): asis -> libxmlezout8-dev/1.06.2-4+b1/s390x
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/amd64
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/arm64
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/armel
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/armhf
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/i386
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/mips64el
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/mipsel
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/ppc64el
    • Impossible Depends: asis -> libgnatcoll19/21.0.0-4/s390x
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/amd64
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/arm64
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/armel
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/armhf
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/i386
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/mips64el
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/mipsel
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/ppc64el
    • Impossible Depends: asis -> libgnatprj8/2021.0.0.0778b109-5/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asis.html
    • autopkgtest for asis/2019-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 544 days old (needed 2 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:
    • Updating libaws would introduce bugs in testing: #1008981, #997457
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-dom10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-input10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-sax10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-schema10-dev/21.0.0-4/s390x
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/amd64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/arm64
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/armel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/armhf
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/i386
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/mips64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/mipsel
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/ppc64el
    • Impossible Build-Depends(-Arch): libaws -> libxmlada-unicode10-dev/21.0.0-4/s390x
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/amd64
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/arm64
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/armel
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/armhf
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/i386
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/mips64el
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/mipsel
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/ppc64el
    • Impossible Depends: libaws -> libxmlada-dom10-dev/21.0.0-4/s390x
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/amd64
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/arm64
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/armel
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/armhf
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/i386
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/mips64el
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/mipsel
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/ppc64el
    • Impossible Depends: libaws -> libxmlada-input10-dev/21.0.0-4/s390x
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/amd64
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/arm64
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/armel
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/armhf
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/i386
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/mips64el
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/mipsel
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/ppc64el
    • Impossible Depends: libaws -> libxmlada-sax10-dev/21.0.0-4/s390x
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/amd64
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/arm64
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/armel
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/armhf
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/i386
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/mips64el
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/mipsel
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/ppc64el
    • Impossible Depends: libaws -> libxmlada-schema10-dev/21.0.0-4/s390x
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/amd64
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/arm64
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/armel
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/armhf
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/i386
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/mips64el
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/mipsel
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/ppc64el
    • Impossible Depends: libaws -> libxmlada-unicode10-dev/21.0.0-4/s390x
    • Build-Depends(-Arch): libaws asis
    • Build-Depends(-Arch): libaws libtemplates-parser
    • Depends: libaws asis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libaws.html
    • autopkgtest for libaws/20.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 544 days old (needed 2 days)
• php-sabre-vobject (- to 2.1.7-6)
  • Migration status for php-sabre-vobject (- to 2.1.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-vobject would introduce bugs in testing: #1003674
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-vobject.html
    • autopkgtest for php-sabre-vobject/2.1.7-6: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 544 days old (needed 5 days)
• xorg-gtest (- to 0.7.1-7)
  • Migration status for xorg-gtest (- to 0.7.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xorg-gtest would introduce bugs in testing: #1006045
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xorg-gtest.html
    • 544 days old (needed 5 days)
• bacula-doc (- to 9.6.7-1)
  • Migration status for bacula-doc (- to 9.6.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bacula-doc would introduce bugs in testing: #1002245
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bacula-doc.html
    • 546 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 546 days old (needed 2 days)
• hy (- to 0.19.0-2)
  • Migration status for hy (- to 0.19.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hy would introduce bugs in testing: #1002344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hy.html
    • autopkgtest for hy/0.19.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 547 days old (needed 2 days)
• kopanocore (- to 8.7.0-7.1)
  • Migration status for kopanocore (- to 8.7.0-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kopano-libs/amd64 has unsatisfiable dependency
    • kopano-server/amd64 has unsatisfiable dependency
    • kopano-utils/amd64 has unsatisfiable dependency
    • python3-mapi/amd64 has unsatisfiable dependency
    • kopano-libs/arm64 has unsatisfiable dependency
    • kopano-server/arm64 has unsatisfiable dependency
    • kopano-utils/arm64 has unsatisfiable dependency
    • python3-mapi/arm64 has unsatisfiable dependency
    • kopano-libs/armel has unsatisfiable dependency
    • kopano-server/armel has unsatisfiable dependency
    • kopano-utils/armel has unsatisfiable dependency
    • python3-mapi/armel has unsatisfiable dependency
    • kopano-libs/armhf has unsatisfiable dependency
    • kopano-server/armhf has unsatisfiable dependency
    • kopano-utils/armhf has unsatisfiable dependency
    • python3-mapi/armhf has unsatisfiable dependency
    • kopano-libs/i386 has unsatisfiable dependency
    • kopano-server/i386 has unsatisfiable dependency
    • kopano-utils/i386 has unsatisfiable dependency
    • python3-mapi/i386 has unsatisfiable dependency
    • kopano-libs/mips64el has unsatisfiable dependency
    • kopano-server/mips64el has unsatisfiable dependency
    • kopano-utils/mips64el has unsatisfiable dependency
    • python3-mapi/mips64el has unsatisfiable dependency
    • kopano-libs/mipsel has unsatisfiable dependency
    • kopano-server/mipsel has unsatisfiable dependency
    • kopano-utils/mipsel has unsatisfiable dependency
    • python3-mapi/mipsel has unsatisfiable dependency
    • kopano-libs/ppc64el has unsatisfiable dependency
    • kopano-server/ppc64el has unsatisfiable dependency
    • kopano-utils/ppc64el has unsatisfiable dependency
    • python3-mapi/ppc64el has unsatisfiable dependency
    • kopano-libs/s390x has unsatisfiable dependency
    • kopano-server/s390x has unsatisfiable dependency
    • kopano-utils/s390x has unsatisfiable dependency
    • python3-mapi/s390x has unsatisfiable dependency
    • Updating kopanocore would introduce bugs in testing: #990322
    • Impossible Depends: kopanocore -> libicu67/67.1-7/amd64
    • Impossible Depends: kopanocore -> libicu67/67.1-7/arm64
    • Impossible Depends: kopanocore -> libicu67/67.1-7/armel
    • Impossible Depends: kopanocore -> libicu67/67.1-7/armhf
    • Impossible Depends: kopanocore -> libicu67/67.1-7/i386
    • Impossible Depends: kopanocore -> libicu67/67.1-7/mips64el
    • Impossible Depends: kopanocore -> libicu67/67.1-7/mipsel
    • Impossible Depends: kopanocore -> libicu67/67.1-7/ppc64el
    • Impossible Depends: kopanocore -> libicu67/67.1-7/s390x
    • Depends: kopanocore sleekxmpp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kopanocore.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
    • 548 days old (needed 5 days)
• ola (- to 0.10.8.nojsmin-2)
  • Migration status for ola (- to 0.10.8.nojsmin-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ola would introduce bugs in testing: #1005447
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ola.html
    • autopkgtest for ola/0.10.8.nojsmin-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 548 days old (needed 2 days)
• php-doctrine-reflection (- to 1.2.2-2)
  • Migration status for php-doctrine-reflection (- to 1.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-doctrine-reflection would introduce bugs in testing: #976794
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-reflection.html
    • autopkgtest for php-doctrine-reflection/1.2.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 548 days old (needed 2 days)
• node-copy-webpack-plugin (- to 5.1.2+~cs9.0.2-4)
  • Migration status for node-copy-webpack-plugin (- to 5.1.2+~cs9.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-copy-webpack-plugin would introduce bugs in testing: #997592
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-copy-webpack-plugin.html
    • autopkgtest for node-copy-webpack-plugin/5.1.2+~cs9.0.2-4: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 550 days old (needed 5 days)
• lazpaint (- to 7.1.6-1)
  • Migration status for lazpaint (- to 7.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lazpaint would introduce bugs in testing: #1005672
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lazpaint.html
    • 551 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 553 days old (needed 5 days)
• relion-cuda (- to 3.1.0-2)
  • Migration status for relion-cuda (- to 3.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating relion-cuda would introduce bugs in testing: #995224
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for relion-cuda/3.1.0-2: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 553 days old (needed 2 days)
• clickhouse (- to 18.16.1+ds-7.2)
  • Migration status for clickhouse (- to 18.16.1+ds-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • clickhouse-client/amd64 has unsatisfiable dependency
    • clickhouse-common/amd64 has unsatisfiable dependency
    • clickhouse-server/amd64 has unsatisfiable dependency
    • clickhouse-tools/amd64 has unsatisfiable dependency
    • clickhouse-client/ppc64el has unsatisfiable dependency
    • clickhouse-common/ppc64el has unsatisfiable dependency
    • clickhouse-server/ppc64el has unsatisfiable dependency
    • clickhouse-tools/ppc64el has unsatisfiable dependency
    • Updating clickhouse would introduce bugs in testing: #995660, #996130
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clickhouse.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 554 days old (needed 5 days)
• libapache-mod-auth-kerb (- to 5.4-2.5)
  • Migration status for libapache-mod-auth-kerb (- to 5.4-2.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-mod-auth-kerb would introduce bugs in testing: #976156, #999324
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-auth-kerb.html
    • 554 days old (needed 5 days)
• php-token-stream (- to 4.0.4-1)
  • Migration status for php-token-stream (- to 4.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-token-stream would introduce bugs in testing: #977802
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-token-stream.html
    • autopkgtest for php-token-stream/4.0.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 555 days old (needed 2 days)
• telepathy-gabble (- to 0.18.4-4)
  • Migration status for telepathy-gabble (- to 0.18.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telepathy-gabble would introduce bugs in testing: #938637
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-gabble.html
    • 555 days old (needed 5 days)
• xrdesktop (- to 0.15.1-5)
  • Migration status for xrdesktop (- to 0.15.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xrdesktop would introduce bugs in testing: #997389
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrdesktop.html
    • 555 days old (needed 5 days)
• gitaly (- to 13.4.6+dfsg1-2)
  • Migration status for gitaly (- to 13.4.6+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitaly would introduce bugs in testing: #976820, #983874, #993964, #995910
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gitaly.html
    • autopkgtest for gitaly/13.4.6+dfsg1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • gitaly unsatisfiable Build-Depends(-Arch) on amd64: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on arm64: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on armel: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on armhf: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on i386: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on mips64el: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on mipsel: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on ppc64el: golang-gopkg-libgit2-git2go.v28-dev
    • gitaly unsatisfiable Build-Depends(-Arch) on s390x: golang-gopkg-libgit2-git2go.v28-dev
    • Build-Depends(-Arch): gitaly gitlab-shell
    • Build-Depends(-Arch): gitaly ruby-gitlab-labkit
    • Depends: gitaly gitlab-shell
    • Depends: gitaly ruby-gitlab-labkit
  • Additional info:
    • 556 days old (needed 5 days)
• golang-github-grafana-grafana-plugin-model (- to 0.0~git20200514.df1eb6b-1)
  • Migration status for golang-github-grafana-grafana-plugin-model (- to 0.0~git20200514.df1eb6b-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-grafana-grafana-plugin-model golang-github-hashicorp-go-plugin (not considered)
    • Depends: golang-github-grafana-grafana-plugin-model golang-github-hashicorp-go-plugin (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-grafana-grafana-plugin-model.html
    • autopkgtest for golang-github-grafana-grafana-plugin-model/0.0~git20200514.df1eb6b-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 557 days old (needed 2 days)
• rust-process-viewer (- to 0.2.6-2)
  • Migration status for rust-process-viewer (- to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-process-viewer would introduce bugs in testing: #1002139
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on amd64: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on arm64: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armel: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on armhf: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on i386: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mips64el: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on mipsel: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pango-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-cairo-rs-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-gdk-0.11+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-gdk-pixbuf-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-gio-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.8+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk-0.7+default-dev
    • rust-process-viewer unsatisfiable Build-Depends(-Arch) on s390x: librust-pango-0.7+default-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-process-viewer.html
    • 557 days old (needed 5 days)
• rust-derive-builder (- to 0.9.0-3)
  • Migration status for rust-derive-builder (- to 0.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-derive-builder+compiletest-rs-dev/amd64 has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/amd64 has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/amd64 has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/arm64 has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/arm64 has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/arm64 has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/armel has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/armel has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/armel has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/armhf has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/armhf has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/armhf has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/i386 has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/i386 has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/i386 has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/mips64el has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/mips64el has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/mips64el has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/mipsel has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/mipsel has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/mipsel has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/ppc64el has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/ppc64el has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/ppc64el has unsatisfiable dependency
    • librust-derive-builder+compiletest-rs-dev/s390x has unsatisfiable dependency
    • librust-derive-builder+skeptic-dev/s390x has unsatisfiable dependency
    • librust-derive-builder+skeptic-tests-dev/s390x has unsatisfiable dependency
    • Updating rust-derive-builder would introduce bugs in testing: #970109
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-derive-builder.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
    • 559 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:
    • librust-tcmalloc-dev/amd64 has unsatisfiable dependency
    • librust-tcmalloc-dev/arm64 has unsatisfiable dependency
    • librust-tcmalloc-dev/armel has unsatisfiable dependency
    • librust-tcmalloc-dev/armhf has unsatisfiable dependency
    • librust-tcmalloc-dev/i386 has unsatisfiable dependency
    • librust-tcmalloc-dev/mips64el has unsatisfiable dependency
    • librust-tcmalloc-dev/mipsel has unsatisfiable dependency
    • librust-tcmalloc-dev/ppc64el has unsatisfiable dependency
    • librust-tcmalloc-dev/s390x has unsatisfiable dependency
    • Updating rust-tcmalloc would introduce bugs in testing: #981869
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tcmalloc.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
    • 559 days old (needed 5 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/mipsel has unsatisfiable dependency
    • librust-rust-code-analysis-dev/ppc64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/s390x has unsatisfiable dependency
    • 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-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-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-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-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-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 mipsel: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mipsel: librust-tree-sitter-0.17+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-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
    • Build-Depends(-Arch): rust-rust-code-analysis rust-num-format
  • Additional info:
    • Piuparts tested OK - 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 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
    • 561 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
    • autopkgtest for chibi-scheme/0.9.1-3: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Pass
  • Additional info:
    • 562 days old (needed 5 days)
• hydrapaper (- to 2.0.2-1)
  • Migration status for hydrapaper (- to 2.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hydrapaper would introduce bugs in testing: #1010697
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydrapaper.html
    • 562 days old (needed 5 days)
• rust-termsize (- to 0.1.6-2)
  • Migration status for rust-termsize (- to 0.1.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-termsize/0.1.6-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-termsize.html
    • 562 days old (needed 5 days)
• skorch (- to 0.9.0-3)
  • Migration status for skorch (- to 0.9.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): skorch pytorch (not considered)
    • Depends: skorch pytorch (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skorch.html
    • 562 days old (needed 5 days)
• nomad-driver-lxc (- to 0.3.0-1)
  • Migration status for nomad-driver-lxc (- to 0.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: nomad-driver-lxc golang-github-hashicorp-go-plugin (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): nomad-driver-lxc nomad
    • Built-Using: nomad-driver-lxc nomad
    • Depends: nomad-driver-lxc nomad
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomad-driver-lxc.html
    • 564 days old (needed 5 days)
• rust-num-format (- to 0.4.0-2)
  • Migration status for rust-num-format (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-num-format-dev/amd64 has unsatisfiable dependency
    • librust-num-format-dev/arm64 has unsatisfiable dependency
    • librust-num-format-dev/armel has unsatisfiable dependency
    • librust-num-format-dev/armhf has unsatisfiable dependency
    • librust-num-format-dev/i386 has unsatisfiable dependency
    • librust-num-format-dev/mips64el has unsatisfiable dependency
    • librust-num-format-dev/mipsel has unsatisfiable dependency
    • librust-num-format-dev/ppc64el has unsatisfiable dependency
    • librust-num-format-dev/s390x has unsatisfiable dependency
    • rust-num-format unsatisfiable Build-Depends(-Arch) on amd64: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on amd64: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on amd64: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on amd64: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on arm64: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on arm64: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on arm64: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on arm64: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armel: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armel: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armel: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armel: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armhf: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armhf: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armhf: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on armhf: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on i386: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on i386: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on i386: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on i386: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mips64el: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mips64el: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mips64el: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mips64el: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mipsel: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mipsel: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mipsel: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on mipsel: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on ppc64el: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on ppc64el: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itoa-0.4+i128-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on s390x: librust-arrayvec-0.5+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on s390x: librust-arrayvec-0.5-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on s390x: librust-itoa-0.4+default-dev
    • rust-num-format unsatisfiable Build-Depends(-Arch) on s390x: librust-itoa-0.4+i128-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-format.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
    • 564 days old (needed 5 days)
• gnome-shell-extension-panel-osd (- to 1.0.50.gc032923-1)
  • Migration status for gnome-shell-extension-panel-osd (- to 1.0.50.gc032923-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-panel-osd would introduce bugs in testing: #996068
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-panel-osd.html
    • 568 days old (needed 5 days)
• mps-youtube (- to 0.2.8-1)
  • Migration status for mps-youtube (- to 0.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mps-youtube would introduce bugs in testing: #877035, #952583
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mps-youtube.html
    • 568 days old (needed 5 days)
• prometheus-homeplug-exporter (- to 0.3.0-2)
  • Migration status for prometheus-homeplug-exporter (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prometheus-homeplug-exporter would introduce bugs in testing: #1002268
    • autopkgtest for prometheus-homeplug-exporter/0.3.0-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Regression ♻ (reference ♻)
    • prometheus-homeplug-exporter/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-homeplug-exporter/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-homeplug-exporter.html
    • 569 days old (needed 5 days)
• glom (- to 1.30.4-6.1)
  • Migration status for glom (- to 1.30.4-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • glom/amd64 has unsatisfiable dependency
    • glom/arm64 has unsatisfiable dependency
    • glom/armel has unsatisfiable dependency
    • glom/armhf has unsatisfiable dependency
    • glom/i386 has unsatisfiable dependency
    • glom/mips64el has unsatisfiable dependency
    • glom/mipsel has unsatisfiable dependency
    • glom/ppc64el has unsatisfiable dependency
    • glom/s390x has unsatisfiable dependency
    • Updating glom would introduce bugs in testing: #1001611, #1008825, #976686
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/glom.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
    • 572 days old (needed 5 days)
• mailsync (- to 5.2.7-3)
  • Migration status for mailsync (- to 5.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailsync would introduce bugs in testing: #998950
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailsync.html
    • 572 days old (needed 5 days)
• ruby-gitlab-labkit (- to 0.12.2-1)
  • Migration status for ruby-gitlab-labkit (- to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-labkit would introduce bugs in testing: #995359
    • autopkgtest for ruby-gitlab-labkit/0.12.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-labkit.html
    • 572 days old (needed 5 days)
• photoflow (- to 0.2.8+git20200114-3)
  • Migration status for photoflow (- to 0.2.8+git20200114-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating photoflow would introduce bugs in testing: #984294
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/photoflow.html
    • 576 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
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/amd64
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/arm64
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/armhf
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/i386
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/mips64el
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/ppc64el
    • Impossible Build-Depends(-Arch): qwertone -> librust-gtk+v3-22-dev/0.7.0-1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qwertone.html
    • 576 days old (needed 5 days)
• qpxtool (- to 0.8.1-1)
  • Migration status for qpxtool (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qpxtool would introduce bugs in testing: #984307
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpxtool.html
    • 577 days old (needed 5 days)
• caldav-tester (- to 7.0+20190225-4)
  • Migration status for caldav-tester (- to 7.0+20190225-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating caldav-tester would introduce bugs in testing: #936268
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caldav-tester.html
    • autopkgtest for caldav-tester/7.0+20190225-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 579 days old (needed 2 days)
• ruby-jquery-ui-rails (- to 6.0.1+dfsg-6)
  • Migration status for ruby-jquery-ui-rails (- to 6.0.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jquery-ui-rails would introduce bugs in testing: #1002233
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jquery-ui-rails.html
    • autopkgtest for ruby-jquery-ui-rails/6.0.1+dfsg-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 581 days old (needed 2 days)
• lilo (- to 1:24.2-5.1)
  • Migration status for lilo (- to 1:24.2-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lilo would introduce bugs in testing: #973850
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lilo.html
    • 582 days old (needed 5 days)
• olive-editor (- to 20200620-2)
  • Migration status for olive-editor (- to 20200620-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): olive-editor openimageio (not considered)
    • Depends: olive-editor openimageio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): olive-editor opencolorio
    • Depends: olive-editor opencolorio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/olive-editor.html
    • 582 days old (needed 5 days)
• eztrace-contrib (- to 1.1-10-1)
  • Migration status for eztrace-contrib (- to 1.1-10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libeztrace0-contrib/amd64 has unsatisfiable dependency
    • Updating eztrace-contrib would introduce bugs in testing: #968312
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 584 days old (needed 5 days)
• rust-diesel-migrations (- to 1.4.0-1)
  • Migration status for rust-diesel-migrations (- to 1.4.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-diesel-migrations rust-migrations-internals (not considered)
    • Depends: rust-diesel-migrations rust-migrations-internals (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-diesel-migrations rust-migrations-macros
    • Depends: rust-diesel-migrations rust-migrations-macros
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-diesel-migrations.html
    • autopkgtest for rust-diesel-migrations/1.4.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 586 days old (needed 5 days)
• geneweb (- to 6.08+git20181019+dfsg-3)
  • Migration status for geneweb (- to 6.08+git20181019+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geneweb would introduce bugs in testing: #1002979
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geneweb.html
    • 587 days old (needed 5 days)
• rust-sleef-sys (- to 0.1.2-5)
  • Migration status for rust-sleef-sys (- to 0.1.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-sleef-sys-dev/amd64 has unsatisfiable dependency
    • librust-sleef-sys-dev/arm64 has unsatisfiable dependency
    • librust-sleef-sys-dev/armhf has unsatisfiable dependency
    • librust-sleef-sys-dev/i386 has unsatisfiable dependency
    • librust-sleef-sys-dev/ppc64el has unsatisfiable dependency
    • librust-sleef-sys-dev/s390x has unsatisfiable dependency
    • Updating rust-sleef-sys would introduce bugs in testing: #978322
    • rust-sleef-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-bindgen-0.55+default-dev | librust-bindgen-0.54+default-dev | librust-bindgen-0.53+default-dev | librust-bindgen-0.52+default-dev | librust-bindgen-0.51+default-dev | librust-bindgen-0.50+default-dev | librust-bindgen-0.49+default-dev | librust-bindgen-0.48+default-dev | librust-bindgen-0.47+default-dev | librust-bindgen-0.46+default-dev
    • rust-sleef-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-bindgen-0.55+default-dev | librust-bindgen-0.54+default-dev | librust-bindgen-0.53+default-dev | librust-bindgen-0.52+default-dev | librust-bindgen-0.51+default-dev | librust-bindgen-0.50+default-dev | librust-bindgen-0.49+default-dev | librust-bindgen-0.48+default-dev | librust-bindgen-0.47+default-dev | librust-bindgen-0.46+default-dev
    • rust-sleef-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-bindgen-0.55+default-dev | librust-bindgen-0.54+default-dev | librust-bindgen-0.53+default-dev | librust-bindgen-0.52+default-dev | librust-bindgen-0.51+default-dev | librust-bindgen-0.50+default-dev | librust-bindgen-0.49+default-dev | librust-bindgen-0.48+default-dev | librust-bindgen-0.47+default-dev | librust-bindgen-0.46+default-dev
    • rust-sleef-sys unsatisfiable Build-Depends(-Arch) on i386: librust-bindgen-0.55+default-dev | librust-bindgen-0.54+default-dev | librust-bindgen-0.53+default-dev | librust-bindgen-0.52+default-dev | librust-bindgen-0.51+default-dev | librust-bindgen-0.50+default-dev | librust-bindgen-0.49+default-dev | librust-bindgen-0.48+default-dev | librust-bindgen-0.47+default-dev | librust-bindgen-0.46+default-dev
    • rust-sleef-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bindgen-0.55+default-dev | librust-bindgen-0.54+default-dev | librust-bindgen-0.53+default-dev | librust-bindgen-0.52+default-dev | librust-bindgen-0.51+default-dev | librust-bindgen-0.50+default-dev | librust-bindgen-0.49+default-dev | librust-bindgen-0.48+default-dev | librust-bindgen-0.47+default-dev | librust-bindgen-0.46+default-dev
    • rust-sleef-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-bindgen-0.55+default-dev | librust-bindgen-0.54+default-dev | librust-bindgen-0.53+default-dev | librust-bindgen-0.52+default-dev | librust-bindgen-0.51+default-dev | librust-bindgen-0.50+default-dev | librust-bindgen-0.49+default-dev | librust-bindgen-0.48+default-dev | librust-bindgen-0.47+default-dev | librust-bindgen-0.46+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-sleef-sys.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
    • 587 days old (needed 5 days)
• owfs (- to 3.2p4+dfsg1-4)
  • Migration status for owfs (- to 3.2p4+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libow-perl/amd64 has unsatisfiable dependency
    • libow-php7/amd64 has unsatisfiable dependency
    • libow-perl/arm64 has unsatisfiable dependency
    • libow-php7/arm64 has unsatisfiable dependency
    • libow-perl/armel has unsatisfiable dependency
    • libow-php7/armel has unsatisfiable dependency
    • libow-perl/armhf has unsatisfiable dependency
    • libow-php7/armhf has unsatisfiable dependency
    • libow-perl/i386 has unsatisfiable dependency
    • libow-php7/i386 has unsatisfiable dependency
    • libow-perl/mips64el has unsatisfiable dependency
    • libow-php7/mips64el has unsatisfiable dependency
    • libow-perl/mipsel has unsatisfiable dependency
    • libow-php7/mipsel has unsatisfiable dependency
    • libow-perl/ppc64el has unsatisfiable dependency
    • libow-php7/ppc64el has unsatisfiable dependency
    • libow-perl/s390x has unsatisfiable dependency
    • libow-php7/s390x has unsatisfiable dependency
    • Updating owfs would introduce bugs in testing: #1003472
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/owfs.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
    • 588 days old (needed 5 days)
• tootle (- to 1.0-alpha2-1)
  • Migration status for tootle (- to 1.0-alpha2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tootle would introduce bugs in testing: #993088
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tootle.html
    • 588 days old (needed 5 days)
• z-push (- to 2.6.0-1)
  • Migration status for z-push (- to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/z/z-push.html
    • Depends: z-push awl
    • Depends: z-push kopanocore
  • Additional info:
    • 588 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:
    • Updating libzorpll would introduce bugs in testing: #1006506
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libz/libzorpll.html
    • 592 days old (needed 5 days)
• ams.lv2 (- to 1.2.2-2)
  • Migration status for ams.lv2 (- to 1.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): ams.lv2 lvtk (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ams.lv2.html
    • 596 days old (needed 5 days)
• genx (- to 3.0.2-1)
  • Migration status for genx (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating genx would introduce bugs in testing: #1002314
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genx.html
    • 596 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-mail-autoconfig php-horde-imap-client (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mail-autoconfig.html
    • autopkgtest for php-horde-mail-autoconfig/1.0.3-10: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 597 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-data (not considered)
    • Invalidated by dependency
    • Depends: php-horde-mnemo php-horde
    • Depends: php-horde-mnemo php-horde-auth
    • Depends: php-horde-mnemo php-horde-content
    • Depends: php-horde-mnemo php-horde-core
    • Depends: php-horde-mnemo php-horde-form
    • Depends: php-horde-mnemo php-horde-text-filter
  • 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: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 597 days old (needed 5 days)
• php-horde-activesync (- to 2.41.5-1)
  • Migration status for php-horde-activesync (- to 2.41.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-activesync php-horde-compress (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-activesync.html
    • autopkgtest for php-horde-activesync/2.41.5-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 598 days old (needed 5 days)
• php-horde-lz4 (- to 1.0.10-8)
  • Migration status for php-horde-lz4 (- to 1.0.10-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-horde-lz4/amd64 has unsatisfiable dependency
    • php-horde-lz4/arm64 has unsatisfiable dependency
    • php-horde-lz4/armel has unsatisfiable dependency
    • php-horde-lz4/armhf has unsatisfiable dependency
    • php-horde-lz4/i386 has unsatisfiable dependency
    • php-horde-lz4/mips64el has unsatisfiable dependency
    • php-horde-lz4/mipsel has unsatisfiable dependency
    • php-horde-lz4/ppc64el has unsatisfiable dependency
    • php-horde-lz4/s390x has unsatisfiable dependency
    • Updating php-horde-lz4 would introduce bugs in testing: #1003473
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-lz4.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
    • 599 days old (needed 5 days)
• ruby-jekyll-seo-tag (- to 2.7.1-2)
  • Migration status for ruby-jekyll-seo-tag (- to 2.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): ruby-jekyll-seo-tag jekyll (not considered)
    • Depends: ruby-jekyll-seo-tag jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-jekyll-seo-tag ruby-html-proofer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-seo-tag.html
    • autopkgtest for ruby-jekyll-seo-tag/2.7.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 599 days old (needed 2 days)
• rust-anymap (- to 0.12.1-1)
  • Migration status for rust-anymap (- to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-anymap would introduce bugs in testing: #992046
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-anymap.html
    • autopkgtest for rust-anymap/0.12.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 599 days old (needed 2 days)
• rust-liquid-core (- to 0.21.1-1)
  • Migration status for rust-liquid-core (- to 0.21.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-liquid-core-dev/amd64 has unsatisfiable dependency
    • librust-liquid-core-dev/arm64 has unsatisfiable dependency
    • librust-liquid-core-dev/armel has unsatisfiable dependency
    • librust-liquid-core-dev/armhf has unsatisfiable dependency
    • librust-liquid-core-dev/i386 has unsatisfiable dependency
    • librust-liquid-core-dev/mips64el has unsatisfiable dependency
    • librust-liquid-core-dev/mipsel has unsatisfiable dependency
    • librust-liquid-core-dev/ppc64el has unsatisfiable dependency
    • librust-liquid-core-dev/s390x has unsatisfiable dependency
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on amd64: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on arm64: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on armel: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on armhf: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on i386: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on mips64el: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on mipsel: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itertools-0.9+default-dev
    • rust-liquid-core unsatisfiable Build-Depends(-Arch) on s390x: librust-itertools-0.9+default-dev
    • Build-Depends(-Arch): rust-liquid-core rust-anymap
    • Build-Depends(-Arch): rust-liquid-core rust-liquid-derive
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-liquid-core.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
    • 599 days old (needed 5 days)
• rust-liquid-derive (- to 0.21.0-1)
  • Migration status for rust-liquid-derive (- to 0.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-liquid-derive-dev/amd64 has unsatisfiable dependency
    • librust-liquid-derive-dev/arm64 has unsatisfiable dependency
    • librust-liquid-derive-dev/armel has unsatisfiable dependency
    • librust-liquid-derive-dev/armhf has unsatisfiable dependency
    • librust-liquid-derive-dev/i386 has unsatisfiable dependency
    • librust-liquid-derive-dev/mips64el has unsatisfiable dependency
    • librust-liquid-derive-dev/mipsel has unsatisfiable dependency
    • librust-liquid-derive-dev/ppc64el has unsatisfiable dependency
    • librust-liquid-derive-dev/s390x has unsatisfiable dependency
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on amd64: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on arm64: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on armel: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on armhf: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on i386: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on mips64el: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on mipsel: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on ppc64el: librust-proc-quote-0.3+default-dev
    • rust-liquid-derive unsatisfiable Build-Depends(-Arch) on s390x: librust-proc-quote-0.3+default-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-liquid-derive.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
    • 599 days old (needed 5 days)
• paw (- to 1:2.14.04.dfsg.2-10)
  • Migration status for paw (- to 1:2.14.04.dfsg.2-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): paw cernlib (not considered)
    • Depends: paw cernlib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paw.html
    • 600 days old (needed 5 days)
• tmate-ssh-server (- to 2.3.0-49-g97d20249-1)
  • Migration status for tmate-ssh-server (- to 2.3.0-49-g97d20249-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tmate-ssh-server would introduce bugs in testing: #1001225
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmate-ssh-server.html
    • 600 days old (needed 5 days)
• haskell-gi-harfbuzz (- to 0.0.3-3)
  • Migration status for haskell-gi-harfbuzz (- to 0.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): haskell-gi-harfbuzz haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-harfbuzz haskell-gi-gobject (not considered)
    • Depends: haskell-gi-harfbuzz haskell-gi-gobject (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-gi-harfbuzz.html
    • 601 days old (needed 5 days)
• rust-derive-more (- to 0.99.5-2)
  • Migration status for rust-derive-more (- to 0.99.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-derive-more+generate-parsing-rs-dev/amd64 has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/amd64 has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/arm64 has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/arm64 has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/armel has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/armel has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/armhf has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/armhf has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/i386 has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/i386 has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/mips64el has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/mips64el has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/mipsel has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/mipsel has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/ppc64el has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/ppc64el has unsatisfiable dependency
    • librust-derive-more+generate-parsing-rs-dev/s390x has unsatisfiable dependency
    • librust-derive-more+rustc-version-dev/s390x has unsatisfiable dependency
    • Updating rust-derive-more would introduce bugs in testing: #984622
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-derive-more.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
    • 601 days old (needed 5 days)
• rust-diesel (- to 1.4.4-2)
  • Migration status for rust-diesel (- to 1.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-diesel+bigdecimal-dev/amd64 has unsatisfiable dependency
    • librust-diesel+extras-dev/amd64 has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/amd64 has unsatisfiable dependency
    • librust-diesel+network-address-dev/amd64 has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/amd64 has unsatisfiable dependency
    • librust-diesel+numeric-dev/amd64 has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/amd64 has unsatisfiable dependency
    • librust-diesel+r2d2-dev/amd64 has unsatisfiable dependency
    • librust-diesel+uuid-dev/amd64 has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/arm64 has unsatisfiable dependency
    • librust-diesel+extras-dev/arm64 has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/arm64 has unsatisfiable dependency
    • librust-diesel+network-address-dev/arm64 has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/arm64 has unsatisfiable dependency
    • librust-diesel+numeric-dev/arm64 has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/arm64 has unsatisfiable dependency
    • librust-diesel+r2d2-dev/arm64 has unsatisfiable dependency
    • librust-diesel+uuid-dev/arm64 has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/armel has unsatisfiable dependency
    • librust-diesel+extras-dev/armel has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/armel has unsatisfiable dependency
    • librust-diesel+mysql-dev/armel has unsatisfiable dependency
    • librust-diesel+mysqlclient-sys-dev/armel has unsatisfiable dependency
    • librust-diesel+network-address-dev/armel has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/armel has unsatisfiable dependency
    • librust-diesel+numeric-dev/armel has unsatisfiable dependency
    • librust-diesel+postgres-dev/armel has unsatisfiable dependency
    • librust-diesel+pq-sys-dev/armel has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/armel has unsatisfiable dependency
    • librust-diesel+r2d2-dev/armel has unsatisfiable dependency
    • librust-diesel+uuid-dev/armel has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/armhf has unsatisfiable dependency
    • librust-diesel+extras-dev/armhf has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/armhf has unsatisfiable dependency
    • librust-diesel+mysql-dev/armhf has unsatisfiable dependency
    • librust-diesel+mysqlclient-sys-dev/armhf has unsatisfiable dependency
    • librust-diesel+network-address-dev/armhf has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/armhf has unsatisfiable dependency
    • librust-diesel+numeric-dev/armhf has unsatisfiable dependency
    • librust-diesel+postgres-dev/armhf has unsatisfiable dependency
    • librust-diesel+pq-sys-dev/armhf has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/armhf has unsatisfiable dependency
    • librust-diesel+r2d2-dev/armhf has unsatisfiable dependency
    • librust-diesel+uuid-dev/armhf has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/i386 has unsatisfiable dependency
    • librust-diesel+extras-dev/i386 has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/i386 has unsatisfiable dependency
    • librust-diesel+mysql-dev/i386 has unsatisfiable dependency
    • librust-diesel+mysqlclient-sys-dev/i386 has unsatisfiable dependency
    • librust-diesel+network-address-dev/i386 has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/i386 has unsatisfiable dependency
    • librust-diesel+numeric-dev/i386 has unsatisfiable dependency
    • librust-diesel+postgres-dev/i386 has unsatisfiable dependency
    • librust-diesel+pq-sys-dev/i386 has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/i386 has unsatisfiable dependency
    • librust-diesel+r2d2-dev/i386 has unsatisfiable dependency
    • librust-diesel+uuid-dev/i386 has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/mips64el has unsatisfiable dependency
    • librust-diesel+extras-dev/mips64el has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/mips64el has unsatisfiable dependency
    • librust-diesel+network-address-dev/mips64el has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/mips64el has unsatisfiable dependency
    • librust-diesel+numeric-dev/mips64el has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/mips64el has unsatisfiable dependency
    • librust-diesel+r2d2-dev/mips64el has unsatisfiable dependency
    • librust-diesel+uuid-dev/mips64el has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/mipsel has unsatisfiable dependency
    • librust-diesel+extras-dev/mipsel has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/mipsel has unsatisfiable dependency
    • librust-diesel+mysql-dev/mipsel has unsatisfiable dependency
    • librust-diesel+mysqlclient-sys-dev/mipsel has unsatisfiable dependency
    • librust-diesel+network-address-dev/mipsel has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/mipsel has unsatisfiable dependency
    • librust-diesel+numeric-dev/mipsel has unsatisfiable dependency
    • librust-diesel+postgres-dev/mipsel has unsatisfiable dependency
    • librust-diesel+pq-sys-dev/mipsel has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/mipsel has unsatisfiable dependency
    • librust-diesel+r2d2-dev/mipsel has unsatisfiable dependency
    • librust-diesel+uuid-dev/mipsel has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+extras-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+network-address-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+numeric-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+r2d2-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+uuid-dev/ppc64el has unsatisfiable dependency
    • librust-diesel+bigdecimal-dev/s390x has unsatisfiable dependency
    • librust-diesel+extras-dev/s390x has unsatisfiable dependency
    • librust-diesel+ipnetwork-dev/s390x has unsatisfiable dependency
    • librust-diesel+network-address-dev/s390x has unsatisfiable dependency
    • librust-diesel+num-bigint-dev/s390x has unsatisfiable dependency
    • librust-diesel+numeric-dev/s390x has unsatisfiable dependency
    • librust-diesel+quickcheck-dev/s390x has unsatisfiable dependency
    • librust-diesel+r2d2-dev/s390x has unsatisfiable dependency
    • librust-diesel+uuid-dev/s390x has unsatisfiable dependency
    • Updating rust-diesel would introduce bugs in testing: #984866, #987275
    • Depends: rust-diesel rust-libsqlite3-sys
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-diesel.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
    • 601 days old (needed 5 days)
• rust-lewton (- to 0.9.4-3)
  • Migration status for rust-lewton (- to 0.9.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-lewton+async-ogg-dev/amd64 has unsatisfiable dependency
    • librust-lewton+futures-dev/amd64 has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/arm64 has unsatisfiable dependency
    • librust-lewton+futures-dev/arm64 has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/armel has unsatisfiable dependency
    • librust-lewton+futures-dev/armel has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/armhf has unsatisfiable dependency
    • librust-lewton+futures-dev/armhf has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/i386 has unsatisfiable dependency
    • librust-lewton+futures-dev/i386 has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/mips64el has unsatisfiable dependency
    • librust-lewton+futures-dev/mips64el has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/mipsel has unsatisfiable dependency
    • librust-lewton+futures-dev/mipsel has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/ppc64el has unsatisfiable dependency
    • librust-lewton+futures-dev/ppc64el has unsatisfiable dependency
    • librust-lewton+async-ogg-dev/s390x has unsatisfiable dependency
    • librust-lewton+futures-dev/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): rust-lewton rust-ogg
    • Depends: rust-lewton rust-ogg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lewton.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
    • 601 days old (needed 5 days)
• rust-zstd (- to 0.5.1-2)
  • Migration status for rust-zstd (- to 0.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-zstd would introduce bugs in testing: #969609
    • rust-zstd unsatisfiable Build-Depends(-Arch) on amd64: librust-zstd-safe-2.0.3+experimental-dev
    • rust-zstd unsatisfiable Build-Depends(-Arch) on amd64: librust-zstd-safe-2.0.3+legacy-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-zstd.html
    • 601 days old (needed 5 days)
• libclc (- to 0.2.0+git20190827-8)
  • Migration status for libclc (- to 0.2.0+git20190827-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libclc would introduce bugs in testing: #998091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libclc.html
    • 603 days old (needed 5 days)
• loganalyzer (- to 4.1.5+dfsg-2.1)
  • Migration status for loganalyzer (- to 4.1.5+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating loganalyzer would introduce bugs in testing: #974586
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loganalyzer.html
    • 604 days old (needed 5 days)
• ruby-jekyll-readme-index (- to 0.3.0-2)
  • Migration status for ruby-jekyll-readme-index (- to 0.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-readme-index jekyll (not considered)
    • Depends: ruby-jekyll-readme-index jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-readme-index.html
    • autopkgtest for ruby-jekyll-readme-index/0.3.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 605 days old (needed 5 days)
• yowsup (- to 3.2.3-2)
  • Migration status for yowsup (- to 3.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yowsup would introduce bugs in testing: #990053
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yowsup.html
    • autopkgtest for yowsup/3.2.3-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 605 days old (needed 5 days)
• ubertooth (- to 2018.12.R1-5)
  • Migration status for ubertooth (- to 2018.12.R1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ubertooth would introduce bugs in testing: #991450
    • autopkgtest for ubertooth/2018.12.R1-5: amd64: Regression ♻ (reference ♻), arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Not a regression, ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ubertooth.html
    • 606 days old (needed 5 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
    • 607 days old (needed 5 days)
• ruby-jekyll-default-layout (- to 0.1.5-1)
  • Migration status for ruby-jekyll-default-layout (- 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): ruby-jekyll-default-layout jekyll (not considered)
    • Depends: ruby-jekyll-default-layout jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-default-layout.html
    • autopkgtest for ruby-jekyll-default-layout/0.1.5-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 609 days old (needed 2 days)
• ruby-jekyll-feed (- to 0.15.1-1)
  • Migration status for ruby-jekyll-feed (- to 0.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): ruby-jekyll-feed jekyll (not considered)
    • Depends: ruby-jekyll-feed jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-feed.html
    • autopkgtest for ruby-jekyll-feed/0.15.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 609 days old (needed 2 days)
• ruby-jekyll-include-cache (- to 0.2.1-1)
  • Migration status for ruby-jekyll-include-cache (- to 0.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): ruby-jekyll-include-cache jekyll (not considered)
    • Depends: ruby-jekyll-include-cache jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-include-cache.html
    • autopkgtest for ruby-jekyll-include-cache/0.2.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 609 days old (needed 2 days)
• sardana (- to 3.0.3-1)
  • Migration status for sardana (- to 3.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: sardana taurus (not considered)
    • Depends: sardana taurus (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sardana.html
    • 611 days old (needed 5 days)
• php-horde-ldap (- to 2.4.2-4)
  • Migration status for php-horde-ldap (- to 2.4.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-ldap would introduce bugs in testing: #1003747
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ldap.html
    • autopkgtest for php-horde-ldap/2.4.2-4: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 613 days old (needed 5 days)
• mpqc (- to 2.3.1-21)
  • Migration status for mpqc (- to 2.3.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mpqc would introduce bugs in testing: #984244
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc.html
    • 614 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/mipsel has unsatisfiable dependency
    • librust-rspotify-dev/ppc64el has unsatisfiable dependency
    • librust-rspotify-dev/s390x has unsatisfiable dependency
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.12+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 arm64: librust-base64-0.12+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 armel: librust-base64-0.12+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 armhf: librust-base64-0.12+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 i386: librust-base64-0.12+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 mips64el: librust-base64-0.12+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 mipsel: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mipsel: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mipsel: librust-rand-0.7+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-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 s390x: librust-base64-0.12+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
    • Build-Depends(-Arch): rust-rspotify rust-derive-builder
    • Build-Depends(-Arch): rust-rspotify rust-reqwest
    • Build-Depends(-Arch): rust-rspotify rust-webbrowser
  • 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 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
    • 614 days old (needed 5 days)
• rust-tokio-executor (- to 0.1.8-2)
  • Migration status for rust-tokio-executor (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-executor-dev/amd64 has unsatisfiable dependency
    • librust-tokio-executor-dev/arm64 has unsatisfiable dependency
    • librust-tokio-executor-dev/armel has unsatisfiable dependency
    • librust-tokio-executor-dev/armhf has unsatisfiable dependency
    • librust-tokio-executor-dev/i386 has unsatisfiable dependency
    • librust-tokio-executor-dev/mips64el has unsatisfiable dependency
    • librust-tokio-executor-dev/mipsel has unsatisfiable dependency
    • librust-tokio-executor-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-executor-dev/s390x has unsatisfiable dependency
    • Updating rust-tokio-executor would introduce bugs in testing: #998611
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-executor unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-executor.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
    • 614 days old (needed 5 days)
• rust-tokio-reactor (- to 0.1.8-2)
  • Migration status for rust-tokio-reactor (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-reactor-dev/amd64 has unsatisfiable dependency
    • librust-tokio-reactor-dev/arm64 has unsatisfiable dependency
    • librust-tokio-reactor-dev/armel has unsatisfiable dependency
    • librust-tokio-reactor-dev/armhf has unsatisfiable dependency
    • librust-tokio-reactor-dev/i386 has unsatisfiable dependency
    • librust-tokio-reactor-dev/mips64el has unsatisfiable dependency
    • librust-tokio-reactor-dev/mipsel has unsatisfiable dependency
    • librust-tokio-reactor-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-reactor-dev/s390x has unsatisfiable dependency
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-reactor unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • Build-Depends(-Arch): rust-tokio-reactor rust-tokio-executor
    • Build-Depends(-Arch): rust-tokio-reactor rust-tokio-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-reactor.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
    • 614 days old (needed 5 days)
• rust-tokio-tcp (- to 0.1.4-1)
  • Migration status for rust-tokio-tcp (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-tcp-dev/amd64 has unsatisfiable dependency
    • librust-tokio-tcp-dev/arm64 has unsatisfiable dependency
    • librust-tokio-tcp-dev/armel has unsatisfiable dependency
    • librust-tokio-tcp-dev/armhf has unsatisfiable dependency
    • librust-tokio-tcp-dev/i386 has unsatisfiable dependency
    • librust-tokio-tcp-dev/mips64el has unsatisfiable dependency
    • librust-tokio-tcp-dev/mipsel has unsatisfiable dependency
    • librust-tokio-tcp-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-tcp-dev/s390x has unsatisfiable dependency
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev
    • rust-tokio-tcp unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • Build-Depends(-Arch): rust-tokio-tcp rust-tokio-io
    • Build-Depends(-Arch): rust-tokio-tcp rust-tokio-reactor
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-tcp.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
    • 614 days old (needed 5 days)
• rust-tokio-threadpool (- to 0.1.16-2)
  • Migration status for rust-tokio-threadpool (- to 0.1.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-threadpool-dev/amd64 has unsatisfiable dependency
    • librust-tokio-threadpool-dev/arm64 has unsatisfiable dependency
    • librust-tokio-threadpool-dev/armel has unsatisfiable dependency
    • librust-tokio-threadpool-dev/armhf has unsatisfiable dependency
    • librust-tokio-threadpool-dev/i386 has unsatisfiable dependency
    • librust-tokio-threadpool-dev/mips64el has unsatisfiable dependency
    • librust-tokio-threadpool-dev/mipsel has unsatisfiable dependency
    • librust-tokio-threadpool-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-threadpool-dev/s390x has unsatisfiable dependency
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armel: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mipsel: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-deque-0.7+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-queue-0.2+default-dev
    • rust-tokio-threadpool unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • Build-Depends(-Arch): rust-tokio-threadpool rust-tokio-executor
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-threadpool.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
    • 614 days old (needed 5 days)
• rust-tokio-timer (- to 0.2.11-2)
  • Migration status for rust-tokio-timer (- to 0.2.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-timer-dev/amd64 has unsatisfiable dependency
    • librust-tokio-timer-dev/arm64 has unsatisfiable dependency
    • librust-tokio-timer-dev/armel has unsatisfiable dependency
    • librust-tokio-timer-dev/armhf has unsatisfiable dependency
    • librust-tokio-timer-dev/i386 has unsatisfiable dependency
    • librust-tokio-timer-dev/mips64el has unsatisfiable dependency
    • librust-tokio-timer-dev/mipsel has unsatisfiable dependency
    • librust-tokio-timer-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-timer-dev/s390x has unsatisfiable dependency
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-timer unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • Build-Depends(-Arch): rust-tokio-timer rust-tokio-executor
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-timer.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
    • 614 days old (needed 5 days)
• php-horde-kronolith (- to 4.2.29-2)
  • Migration status for php-horde-kronolith (- 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-kronolith php-horde-data (not considered)
    • Invalidated by dependency
    • Depends: php-horde-kronolith php-horde
    • Depends: php-horde-kronolith php-horde-auth
    • Depends: php-horde-kronolith php-horde-content
    • Depends: php-horde-kronolith php-horde-core
    • Depends: php-horde-kronolith php-horde-dav
    • Depends: php-horde-kronolith php-horde-form
    • Depends: php-horde-kronolith php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
    • autopkgtest for php-horde-kronolith/4.2.29-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 615 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-data (not considered)
    • Invalidated by dependency
    • Depends: php-horde-nag php-horde
    • Depends: php-horde-nag php-horde-auth
    • Depends: php-horde-nag php-horde-content
    • Depends: php-horde-nag php-horde-core
    • Depends: php-horde-nag php-horde-dav
    • Depends: php-horde-nag php-horde-form
    • Depends: php-horde-nag php-horde-text-filter
  • 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: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 615 days old (needed 5 days)
• php-horde-imp (- to 6.2.27-2)
  • Migration status for php-horde-imp (- to 6.2.27-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-imp would introduce bugs in testing: #1003746
    • Depends: php-horde-imp php-horde
    • Depends: php-horde-imp php-horde-auth
    • Depends: php-horde-imp php-horde-compress
    • Depends: php-horde-imp php-horde-core
    • Depends: php-horde-imp php-horde-crypt
    • Depends: php-horde-imp php-horde-imap-client
    • Depends: php-horde-imp php-horde-mail-autoconfig
    • Depends: php-horde-imp php-horde-mime-viewer
    • Depends: php-horde-imp php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
    • autopkgtest for php-horde-imp/6.2.27-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 616 days old (needed 5 days)
• php-horde-ingo (- to 3.2.16-8)
  • Migration status for php-horde-ingo (- to 3.2.16-8): 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-auth (not considered)
    • Invalidated by dependency
    • Depends: php-horde-ingo php-horde
    • Depends: php-horde-ingo php-horde-core
    • Depends: php-horde-ingo php-horde-form
    • Depends: php-horde-ingo php-horde-imap-client
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
    • autopkgtest for php-horde-ingo/3.2.16-8: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 616 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-8)
  • Migration status for php-horde-passwd (- to 5.0.7-8): 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-auth (not considered)
    • Invalidated by dependency
    • Depends: php-horde-passwd php-horde
    • Depends: php-horde-passwd php-horde-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
    • autopkgtest for php-horde-passwd/5.0.7-8: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 616 days old (needed 5 days)
• php-horde-sesha (- to 1.0.0~rc3-8)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-sesha/1.0.0~rc3-8: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Regression ♻ (reference ♻)
    • Depends: php-horde-sesha php-horde
    • Depends: php-horde-sesha php-horde-auth
    • Depends: php-horde-sesha php-horde-core
    • Depends: php-horde-sesha php-horde-form
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
    • 616 days old (needed 5 days)
• php-horde-wicked (- to 2.0.8-8)
  • Migration status for php-horde-wicked (- to 2.0.8-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-wicked would introduce bugs in testing: #1003784
    • Depends: php-horde-wicked php-horde
    • Depends: php-horde-wicked php-horde-auth
    • Depends: php-horde-wicked php-horde-core
    • Depends: php-horde-wicked php-horde-form
    • Depends: php-horde-wicked php-horde-mime-viewer
    • Depends: php-horde-wicked php-horde-rpc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
    • autopkgtest for php-horde-wicked/2.0.8-8: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 616 days old (needed 5 days)
• fuzz (- to 0.6-19)
  • Migration status for fuzz (- to 0.6-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fuzz would introduce bugs in testing: #967987
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fuzz.html
    • autopkgtest for fuzz/0.6-19: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 620 days old (needed 2 days)
• php-horde-content (- to 2.0.6-7)
  • Migration status for php-horde-content (- to 2.0.6-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-content php-horde-core (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-content.html
    • autopkgtest for php-horde-content/2.0.6-7: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 620 days old (needed 5 days)
• gnome-metronome (- to 0.1.1-1)
  • Migration status for gnome-metronome (- to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-metronome would introduce bugs in testing: #993852
    • Build-Depends(-Arch): gnome-metronome libhandy
    • Depends: gnome-metronome libhandy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-metronome.html
    • autopkgtest for gnome-metronome/0.1.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 625 days old (needed 5 days)
• php-horde-text-filter-jsmin (- to 1.0.2-10)
  • Migration status for php-horde-text-filter-jsmin (- to 1.0.2-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-text-filter-jsmin php-horde-text-filter (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for php-horde-text-filter-jsmin/1.0.2-10: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 625 days old (needed 5 days)
• ruby-markdown-it-html5-embed (- to 1.0.0+dfsg-5)
  • Migration status for ruby-markdown-it-html5-embed (- to 1.0.0+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-markdown-it-html5-embed would introduce bugs in testing: #1005630
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-markdown-it-html5-embed.html
    • autopkgtest for ruby-markdown-it-html5-embed/1.0.0+dfsg-5: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 626 days old (needed 5 days)
• bonnie++ (- to 2.00a)
  • Migration status for bonnie++ (- to 2.00a): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bonnie++ would introduce bugs in testing: #983999, #999322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bonnie++.html
    • autopkgtest for bonnie++/2.00a: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 627 days old (needed 5 days)
• php-horde-kolab-server (- to 2.0.5-9)
  • Migration status for php-horde-kolab-server (- to 2.0.5-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-kolab-server php-horde-auth (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-server.html
    • autopkgtest for php-horde-kolab-server/2.0.5-9: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 628 days old (needed 5 days)
• ruby-rails-assets-perfect-scrollbar (- to 1.4.0-4)
  • Migration status for ruby-rails-assets-perfect-scrollbar (- to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-rails-assets-perfect-scrollbar/amd64 has unsatisfiable dependency
    • ruby-rails-assets-perfect-scrollbar/arm64 has unsatisfiable dependency
    • Updating ruby-rails-assets-perfect-scrollbar would introduce bugs in testing: #979936
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-perfect-scrollbar.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • autopkgtest for ruby-rails-assets-perfect-scrollbar/1.4.0-4: armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 629 days old (needed 5 days)
• bist (- to 0.5.2-1.2)
  • Migration status for bist (- to 0.5.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bist/amd64 has unsatisfiable dependency
    • bist/arm64 has unsatisfiable dependency
    • bist/armel has unsatisfiable dependency
    • bist/armhf has unsatisfiable dependency
    • bist/i386 has unsatisfiable dependency
    • bist/mips64el has unsatisfiable dependency
    • bist/mipsel has unsatisfiable dependency
    • bist/ppc64el has unsatisfiable dependency
    • bist/s390x has unsatisfiable dependency
    • Updating bist would introduce bugs in testing: #983991
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bist.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
    • 637 days old (needed 5 days)
• dnshistory (- to 1.3-2.1)
  • Migration status for dnshistory (- to 1.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dnshistory would introduce bugs in testing: #965493, #999236
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnshistory.html
    • 637 days old (needed 5 days)
• claws-mail-themes (- to 20140629+dfsg2-1)
  • Migration status for claws-mail-themes (- to 20140629+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating claws-mail-themes would introduce bugs in testing: #1005840
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/claws-mail-themes.html
    • 638 days old (needed 5 days)
• flmsg (- to 4.0.17-1)
  • Migration status for flmsg (- to 4.0.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flmsg would introduce bugs in testing: #984131
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flmsg.html
    • 638 days old (needed 5 days)
• php-horde-core (- to 2.31.16+debian0-2)
  • Migration status for php-horde-core (- to 2.31.16+debian0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-core would introduce bugs in testing: #1003665
    • Depends: php-horde-core php-horde-auth
    • Depends: php-horde-core php-horde-compress
    • Depends: php-horde-core php-horde-data
    • Depends: php-horde-core php-horde-mime-viewer
    • Depends: php-horde-core php-horde-secret
    • Depends: php-horde-core php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-core.html
    • autopkgtest for php-horde-core/2.31.16+debian0-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 638 days old (needed 5 days)
• wmmatrix (- to 0.2-12.1)
  • Migration status for wmmatrix (- to 0.2-12.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmmatrix would introduce bugs in testing: #965876
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmmatrix.html
    • 638 days old (needed 5 days)
• rust-fs-extra (- to 1.2.0-1)
  • Migration status for rust-fs-extra (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-fs-extra/1.2.0-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fs-extra.html
    • 639 days old (needed 5 days)
• hexcurse (- to 1.58-1.3)
  • Migration status for hexcurse (- to 1.58-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hexcurse would introduce bugs in testing: #994194
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hexcurse.html
    • 646 days old (needed 5 days)
• rust-core-arch (- to 0.1.5-4)
  • Migration status for rust-core-arch (- to 0.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-core-arch would introduce bugs in testing: #976467
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-core-arch.html
    • autopkgtest for rust-core-arch/0.1.5-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 647 days old (needed 5 days)
• rabbit (- to 3.0.0-4)
  • Migration status for rabbit (- to 3.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rabbit ruby-gnome (not considered)
    • Depends: rabbit ruby-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbit.html
    • autopkgtest for rabbit/3.0.0-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 648 days old (needed 2 days)
• sjeng (- to 11.2-8.1)
  • Migration status for sjeng (- to 11.2-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sjeng would introduce bugs in testing: #999026
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sjeng.html
    • 649 days old (needed 5 days)
• intellij-community-idea (- to 183.5153.4-2)
  • Migration status for intellij-community-idea (- to 183.5153.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intellij-community-idea would introduce bugs in testing: #981886
    • Build-Depends(-Arch): intellij-community-idea openjdk-8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intellij-community-idea.html
    • 650 days old (needed 5 days)
• haskell-gi-atk (- to 2.0.22-1)
  • Migration status for haskell-gi-atk (- to 2.0.22-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gi-atk haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-atk haskell-gi-gobject (not considered)
    • Depends: haskell-gi-atk haskell-gi-gobject (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-gi-atk.html
    • 655 days old (needed 5 days)
• haskell-gi-dbusmenu (- to 0.4.8-1)
  • Migration status for haskell-gi-dbusmenu (- to 0.4.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gi-dbusmenu haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-dbusmenu haskell-gi-gobject (not considered)
    • Depends: haskell-gi-dbusmenu haskell-gi-gobject (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-gi-dbusmenu.html
    • 655 days old (needed 5 days)
• haskell-gi-dbusmenugtk3 (- to 0.4.9-1)
  • Migration status for haskell-gi-dbusmenugtk3 (- to 0.4.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-dbusmenugtk3-dev/armhf has unsatisfiable dependency
    • libghc-gi-dbusmenugtk3-prof/armhf has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-atk
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-dbusmenu
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-gdkpixbuf
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-gobject
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-gtk
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-atk
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-dbusmenu
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-gdk
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-gdkpixbuf
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-gobject
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-gtk
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-atk
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-dbusmenu
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gdk
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gdkpixbuf
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gobject
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gtk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-dbusmenugtk3.html
    • uninstallable on arch armhf, not running autopkgtest there
    • 655 days old (needed 5 days)
• haskell-gi-gdk (- to 3.0.23-1)
  • Migration status for haskell-gi-gdk (- to 3.0.23-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gi-gdk haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-gdk haskell-gi-gobject (not considered)
    • Depends: haskell-gi-gdk haskell-gi-gobject (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-gi-gdk haskell-gi-gdkpixbuf
    • Build-Depends(-Arch): haskell-gi-gdk haskell-gi-gio
    • Build-Depends(-Arch): haskell-gi-gdk haskell-gi-pango
    • Build-Depends-Indep: haskell-gi-gdk haskell-gi-gdkpixbuf
    • Build-Depends-Indep: haskell-gi-gdk haskell-gi-gio
    • Build-Depends-Indep: haskell-gi-gdk haskell-gi-pango
    • Depends: haskell-gi-gdk haskell-gi-gdkpixbuf
    • Depends: haskell-gi-gdk haskell-gi-gio
    • Depends: haskell-gi-gdk haskell-gi-pango
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gdk.html
    • 655 days old (needed 5 days)
• haskell-gi-gdkpixbuf (- to 2.0.24-1)
  • Migration status for haskell-gi-gdkpixbuf (- to 2.0.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-gi-gdkpixbuf would introduce bugs in testing: #992229
    • Build-Depends(-Arch): haskell-gi-gdkpixbuf haskell-gi-gio
    • Build-Depends(-Arch): haskell-gi-gdkpixbuf haskell-gi-gobject
    • Build-Depends-Indep: haskell-gi-gdkpixbuf haskell-gi-gio
    • Build-Depends-Indep: haskell-gi-gdkpixbuf haskell-gi-gobject
    • Depends: haskell-gi-gdkpixbuf haskell-gi-gio
    • Depends: haskell-gi-gdkpixbuf haskell-gi-gobject
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gdkpixbuf.html
    • 655 days old (needed 5 days)
• haskell-gi-gdkx11 (- to 3.0.10-1)
  • Migration status for haskell-gi-gdkx11 (- to 3.0.10-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gi-gdkx11 haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-gdkx11 haskell-gi-gobject (not considered)
    • Depends: haskell-gi-gdkx11 haskell-gi-gobject (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-gi-gdkx11 haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gi-gdkx11 haskell-gi-gio
    • Build-Depends-Indep: haskell-gi-gdkx11 haskell-gi-gdk
    • Build-Depends-Indep: haskell-gi-gdkx11 haskell-gi-gio
    • Depends: haskell-gi-gdkx11 haskell-gi-gdk
    • Depends: haskell-gi-gdkx11 haskell-gi-gio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gdkx11.html
    • 655 days old (needed 5 days)
• haskell-gi-gio (- to 2.0.27-1)
  • Migration status for haskell-gi-gio (- to 2.0.27-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gi-gio haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-gio haskell-gi-gobject (not considered)
    • Depends: haskell-gi-gio haskell-gi-gobject (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-gi-gio.html
    • 655 days old (needed 5 days)
• haskell-gi-gobject (- to 2.0.24-1)
  • Migration status for haskell-gi-gobject (- to 2.0.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-gi-gobject would introduce bugs in testing: #1008401
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gobject.html
    • 655 days old (needed 5 days)
• haskell-gi-gtk (- to 3.0.36-1)
  • Migration status for haskell-gi-gtk (- to 3.0.36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-gtk-dev/armhf has unsatisfiable dependency
    • libghc-gi-gtk-prof/armhf has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-atk
    • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-gdkpixbuf
    • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-gio
    • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-gobject
    • Build-Depends(-Arch): haskell-gi-gtk haskell-gi-pango
    • Build-Depends-Indep: haskell-gi-gtk haskell-gi-atk
    • Build-Depends-Indep: haskell-gi-gtk haskell-gi-gdk
    • Build-Depends-Indep: haskell-gi-gtk haskell-gi-gdkpixbuf
    • Build-Depends-Indep: haskell-gi-gtk haskell-gi-gio
    • Build-Depends-Indep: haskell-gi-gtk haskell-gi-gobject
    • Build-Depends-Indep: haskell-gi-gtk haskell-gi-pango
    • Depends: haskell-gi-gtk haskell-gi-atk
    • Depends: haskell-gi-gtk haskell-gi-gdk
    • Depends: haskell-gi-gtk haskell-gi-gdkpixbuf
    • Depends: haskell-gi-gtk haskell-gi-gio
    • Depends: haskell-gi-gtk haskell-gi-gobject
    • Depends: haskell-gi-gtk haskell-gi-pango
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gtk.html
    • uninstallable on arch armhf, not running autopkgtest there
    • 655 days old (needed 5 days)
• haskell-gi-gtk-hs (- to 0.3.9-1)
  • Migration status for haskell-gi-gtk-hs (- to 0.3.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-gtk-hs-dev/armhf has unsatisfiable dependency
    • libghc-gi-gtk-hs-prof/armhf has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-gtk-hs haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gi-gtk-hs haskell-gi-gdkpixbuf
    • Build-Depends(-Arch): haskell-gi-gtk-hs haskell-gi-gobject
    • Build-Depends(-Arch): haskell-gi-gtk-hs haskell-gi-gtk
    • Build-Depends-Indep: haskell-gi-gtk-hs haskell-gi-gdk
    • Build-Depends-Indep: haskell-gi-gtk-hs haskell-gi-gdkpixbuf
    • Build-Depends-Indep: haskell-gi-gtk-hs haskell-gi-gobject
    • Build-Depends-Indep: haskell-gi-gtk-hs haskell-gi-gtk
    • Depends: haskell-gi-gtk-hs haskell-gi-gdk
    • Depends: haskell-gi-gtk-hs haskell-gi-gdkpixbuf
    • Depends: haskell-gi-gtk-hs haskell-gi-gobject
    • Depends: haskell-gi-gtk-hs haskell-gi-gtk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gtk-hs.html
    • uninstallable on arch armhf, not running autopkgtest there
    • 655 days old (needed 5 days)
• haskell-gi-pango (- to 1.0.23-1)
  • Migration status for haskell-gi-pango (- to 1.0.23-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gi-pango haskell-gi-gobject (not considered)
    • Build-Depends-Indep: haskell-gi-pango haskell-gi-gobject (not considered)
    • Depends: haskell-gi-pango haskell-gi-gobject (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-gi-pango haskell-gi-harfbuzz
    • Build-Depends-Indep: haskell-gi-pango haskell-gi-harfbuzz
    • Depends: haskell-gi-pango haskell-gi-harfbuzz
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-pango.html
    • 655 days old (needed 5 days)
• haskell-gi-vte (- to 2.91.27-1)
  • Migration status for haskell-gi-vte (- to 2.91.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-vte-dev/armhf has unsatisfiable dependency
    • libghc-gi-vte-prof/armhf has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-atk
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-gio
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-gobject
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-gtk
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-pango
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-atk
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-gdk
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-gio
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-gobject
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-gtk
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-pango
    • Depends: haskell-gi-vte haskell-gi-atk
    • Depends: haskell-gi-vte haskell-gi-gdk
    • Depends: haskell-gi-vte haskell-gi-gio
    • Depends: haskell-gi-vte haskell-gi-gobject
    • Depends: haskell-gi-vte haskell-gi-gtk
    • Depends: haskell-gi-vte haskell-gi-pango
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-vte.html
    • uninstallable on arch armhf, not running autopkgtest there
    • 655 days old (needed 5 days)
• ruby-rails-assets-favico.js (- to 0.3.10+dfsg-2)
  • Migration status for ruby-rails-assets-favico.js (- to 0.3.10+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-favico.js would introduce bugs in testing: #979962
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-favico.js.html
    • autopkgtest for ruby-rails-assets-favico.js/0.3.10+dfsg-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 655 days old (needed 5 days)
• taffybar (- to 3.2.2-2)
  • Migration status for taffybar (- to 3.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-taffybar-dev/amd64 has unsatisfiable dependency
    • libghc-taffybar-prof/amd64 has unsatisfiable dependency
    • libghc-taffybar-dev/arm64 has unsatisfiable dependency
    • libghc-taffybar-prof/arm64 has unsatisfiable dependency
    • libghc-taffybar-dev/armhf has unsatisfiable dependency
    • libghc-taffybar-prof/armhf has unsatisfiable dependency
    • libghc-taffybar-dev/i386 has unsatisfiable dependency
    • libghc-taffybar-prof/i386 has unsatisfiable dependency
    • libghc-taffybar-dev/mips64el has unsatisfiable dependency
    • libghc-taffybar-prof/mips64el has unsatisfiable dependency
    • libghc-taffybar-dev/mipsel has unsatisfiable dependency
    • libghc-taffybar-prof/mipsel has unsatisfiable dependency
    • libghc-taffybar-dev/ppc64el has unsatisfiable dependency
    • libghc-taffybar-prof/ppc64el has unsatisfiable dependency
    • libghc-taffybar-dev/s390x has unsatisfiable dependency
    • libghc-taffybar-prof/s390x has unsatisfiable dependency
    • Impossible Depends: taffybar -> libffi7/3.3-6/amd64
    • Impossible Depends: taffybar -> libffi7/3.3-6/arm64
    • Impossible Depends: taffybar -> libffi7/3.3-6/armhf
    • Impossible Depends: taffybar -> libffi7/3.3-6/i386
    • Impossible Depends: taffybar -> libffi7/3.3-6/mips64el
    • Impossible Depends: taffybar -> libffi7/3.3-6/mipsel
    • Impossible Depends: taffybar -> libffi7/3.3-6/ppc64el
    • Impossible Depends: taffybar -> libffi7/3.3-6/s390x
    • Build-Depends(-Arch): taffybar haskell-gi-gdk
    • Build-Depends(-Arch): taffybar haskell-gi-gdkpixbuf
    • Build-Depends(-Arch): taffybar haskell-gi-gdkx11
    • Build-Depends(-Arch): taffybar haskell-gi-gtk
    • Build-Depends(-Arch): taffybar haskell-gi-gtk-hs
    • Build-Depends(-Arch): taffybar haskell-gi-pango
    • Build-Depends(-Arch): taffybar haskell-gtk-sni-tray
    • Build-Depends(-Arch): taffybar haskell-gtk-strut
    • Build-Depends-Indep: taffybar haskell-gi-gdk
    • Build-Depends-Indep: taffybar haskell-gi-gdkpixbuf
    • Build-Depends-Indep: taffybar haskell-gi-gdkx11
    • Build-Depends-Indep: taffybar haskell-gi-gtk
    • Build-Depends-Indep: taffybar haskell-gi-gtk-hs
    • Build-Depends-Indep: taffybar haskell-gi-pango
    • Build-Depends-Indep: taffybar haskell-gtk-sni-tray
    • Build-Depends-Indep: taffybar haskell-gtk-strut
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taffybar.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
    • 655 days old (needed 5 days)
• haskell-dhall (- to 1.32.0-1)
  • Migration status for haskell-dhall (- to 1.32.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-dhall haskell-serialise (not considered)
    • Build-Depends-Indep: haskell-dhall haskell-serialise (not considered)
    • Depends: haskell-dhall haskell-serialise (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-dhall.html
    • 658 days old (needed 5 days)
• haskell-yesod-bin (- to 1.6.0.6-1)
  • Migration status for haskell-yesod-bin (- to 1.6.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-yesod-bin would introduce bugs in testing: #982095
    • autopkgtest for haskell-yesod-bin/1.6.0.6-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-yesod-bin.html
    • 658 days old (needed 5 days)
• lambdabot (- to 5.3.0.1-1)
  • Migration status for lambdabot (- to 5.3.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): lambdabot haskell-lambdabot-haskell-plugins (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lambdabot.html
    • 658 days old (needed 5 days)
• snmptrapfmt (- to 1.17)
  • Migration status for snmptrapfmt (- to 1.17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating snmptrapfmt would introduce bugs in testing: #999166
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snmptrapfmt.html
    • 659 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
    • Depends: prayer openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prayer.html
    • 664 days old (needed 5 days)
• f-irc (- to 1.36-1.1)
  • Migration status for f-irc (- to 1.36-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating f-irc would introduce bugs in testing: #997148
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/f-irc.html
    • 666 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
    • 666 days old (needed 5 days)
• ocaml-melt (- to 1.4.0-3)
  • Migration status for ocaml-melt (- to 1.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmelt-ocaml-dev/amd64 has unsatisfiable dependency
    • libmelt-ocaml-dev/arm64 has unsatisfiable dependency
    • libmelt-ocaml-dev/armel has unsatisfiable dependency
    • ocaml-melt/armel has unsatisfiable dependency
    • libmelt-ocaml-dev/armhf has unsatisfiable dependency
    • libmelt-ocaml-dev/i386 has unsatisfiable dependency
    • libmelt-ocaml-dev/mips64el has unsatisfiable dependency
    • ocaml-melt/mips64el has unsatisfiable dependency
    • libmelt-ocaml-dev/mipsel has unsatisfiable dependency
    • ocaml-melt/mipsel has unsatisfiable dependency
    • libmelt-ocaml-dev/ppc64el has unsatisfiable dependency
    • libmelt-ocaml-dev/s390x has unsatisfiable dependency
    • Updating ocaml-melt would introduce bugs in testing: #972261
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/ocaml-melt.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
    • 667 days old (needed 5 days)
• ifhp (- to 3.5.20-17)
  • Migration status for ifhp (- to 3.5.20-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ifhp would introduce bugs in testing: #984056
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifhp.html
    • 668 days old (needed 5 days)
• otags (- to 4.05.1-2)
  • Migration status for otags (- to 4.05.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • otags/armel has unsatisfiable dependency
    • otags/mips64el has unsatisfiable dependency
    • otags/mipsel has unsatisfiable dependency
    • Updating otags would introduce bugs in testing: #1002940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/otags.html
    • 668 days old (needed 5 days)
• apper (- to 1.0.0-3)
  • Migration status for apper (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apper would introduce bugs in testing: #1006306
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apper.html
    • 671 days old (needed 5 days)
• forked-daapd (- to 26.4+dfsg1-2)
  • Migration status for forked-daapd (- to 26.4+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating forked-daapd would introduce bugs in testing: #982034
    • autopkgtest for forked-daapd/26.4+dfsg1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forked-daapd.html
    • 672 days old (needed 5 days)
• oroborus (- to 2.0.20+nmu1)
  • Migration status for oroborus (- to 2.0.20+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oroborus would introduce bugs in testing: #999162
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oroborus.html
    • 673 days old (needed 5 days)
• apache-curator (- to 2.7.1-3)
  • Migration status for apache-curator (- to 2.7.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): apache-curator zookeeper (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apache-curator.html
    • 674 days old (needed 5 days)
• nvtv (- to 0.4.7-8.1)
  • Migration status for nvtv (- to 0.4.7-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvtv would introduce bugs in testing: #997339
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvtv.html
    • 674 days old (needed 5 days)
• gr-iio (- to 0.3-9)
  • Migration status for gr-iio (- to 0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gr-iio/amd64 has unsatisfiable dependency
    • gr-iio/arm64 has unsatisfiable dependency
    • gr-iio/armel has unsatisfiable dependency
    • gr-iio/armhf has unsatisfiable dependency
    • gr-iio/i386 has unsatisfiable dependency
    • gr-iio/mips64el has unsatisfiable dependency
    • gr-iio/mipsel has unsatisfiable dependency
    • gr-iio/ppc64el has unsatisfiable dependency
    • gr-iio/s390x has unsatisfiable dependency
    • Updating gr-iio would introduce bugs in testing: #1002091, #1004940
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gr-iio.html
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-iio -> libgnuradio-analog3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-iio -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-iio -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-iio -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/s390x
  • Additional info:
    • 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
    • 675 days old (needed 5 days)
• mldonkey (- to 3.1.7-2)
  • Migration status for mldonkey (- to 3.1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mldonkey-server/armel has unsatisfiable dependency
    • mldonkey-server/mips64el has unsatisfiable dependency
    • mldonkey-server/mipsel has unsatisfiable dependency
    • Updating mldonkey would introduce bugs in testing: #972211
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mldonkey.html
    • 676 days old (needed 5 days)
• haskell-blogliterately (- to 0.8.7-1)
  • Migration status for haskell-blogliterately (- to 0.8.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-blogliterately highlighting-kate (not considered)
    • Build-Depends-Indep: haskell-blogliterately highlighting-kate (not considered)
    • Depends: haskell-blogliterately highlighting-kate (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Depends: haskell-blogliterately haskell-haxr/amd64
    • Depends: haskell-blogliterately haskell-haxr/arm64
    • Depends: haskell-blogliterately haskell-haxr/armel
    • Depends: haskell-blogliterately haskell-haxr/armhf
    • Depends: haskell-blogliterately haskell-haxr/i386
    • Depends: haskell-blogliterately haskell-haxr/mips64el
    • Depends: haskell-blogliterately haskell-haxr/mipsel
    • Depends: haskell-blogliterately haskell-haxr/ppc64el
    • Depends: haskell-blogliterately haskell-haxr/s390x
    • Depends: haskell-blogliterately openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-blogliterately.html
    • 677 days old (needed 5 days)
• android-platform-frameworks-data-binding (- to 2.2.2-5)
  • Migration status for android-platform-frameworks-data-binding (- to 2.2.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): android-platform-frameworks-data-binding android-platform-tools-base (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): android-platform-frameworks-data-binding openjdk-8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-frameworks-data-binding.html
    • 680 days old (needed 5 days)
• mmorph (- to 2.3.4.2-17)
  • Migration status for mmorph (- to 2.3.4.2-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mmorph would introduce bugs in testing: #967990
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmorph.html
    • autopkgtest for mmorph/2.3.4.2-17: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 685 days old (needed 2 days)
• uuagc (- to 0.9.52.2-3)
  • Migration status for uuagc (- to 0.9.52.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uuagc would introduce bugs in testing: #965311
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uuagc.html
    • 685 days old (needed 5 days)
• ninvaders (- to 0.1.1-4)
  • Migration status for ninvaders (- to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ninvaders would introduce bugs in testing: #998969
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ninvaders.html
    • 686 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
    • 687 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/mipsel 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: #993015
    • Build-Depends(-Arch): kwin-effect-xrdesktop xrdesktop
  • 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 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
    • 687 days old (needed 5 days)
• php-horde-secret (- to 2.0.6-9)
  • Migration status for php-horde-secret (- to 2.0.6-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-secret php-horde-crypt-blowfish (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-secret.html
    • autopkgtest for php-horde-secret/2.0.6-9: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 688 days old (needed 2 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/effcee.html
    • autopkgtest for effcee/2019.1-1: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 689 days old (needed 5 days)
• php-horde-argv (- to 2.1.0-7)
  • Migration status for php-horde-argv (- to 2.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-argv would introduce bugs in testing: #1003649
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-argv.html
    • autopkgtest for php-horde-argv/2.1.0-7: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 689 days old (needed 5 days)
• php-horde-auth (- to 2.2.2-8)
  • Migration status for php-horde-auth (- to 2.2.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-auth would introduce bugs in testing: #1003651
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-auth.html
    • autopkgtest for php-horde-auth/2.2.2-8: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 689 days old (needed 5 days)
• php-horde-crypt-blowfish (- to 1.1.3-2)
  • Migration status for php-horde-crypt-blowfish (- to 1.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-crypt-blowfish would introduce bugs in testing: #1003666
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt-blowfish.html
    • autopkgtest for php-horde-crypt-blowfish/1.1.3-2: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 689 days old (needed 5 days)
• php-horde-data (- to 2.1.5-2)
  • Migration status for php-horde-data (- to 2.1.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-data would introduce bugs in testing: #1003667
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-data.html
    • autopkgtest for php-horde-data/2.1.5-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 689 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
    • 690 days old (needed 5 days)
• haskell-serialise (- to 0.2.3.0-2)
  • Migration status for haskell-serialise (- to 0.2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-serialise would introduce bugs in testing: #939323
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-serialise.html
    • 692 days old (needed 5 days)
• cicero (- to 0.7.2-6)
  • Migration status for cicero (- to 0.7.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cicero would introduce bugs in testing: #945625
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 695 days old (needed 5 days)
• umap-learn (- to 0.4.5+dfsg-2)
  • Migration status for umap-learn (- to 0.4.5+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umap-learn would introduce bugs in testing: #1002400
    • Build-Depends(-Arch): umap-learn numba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umap-learn.html
    • autopkgtest for umap-learn/0.4.5+dfsg-2: amd64: Pass, arm64: Pass, armhf: Not a regression, i386: Not a regression, ppc64el: Pass, s390x: Not a regression
    • 695 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: #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 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
    • 696 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)
    • 696 days old (needed 5 days)
• python-hug (- to 2.6.0-2)
  • Migration status for python-hug (- to 2.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-hug would introduce bugs in testing: #953258
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-hug.html
    • autopkgtest for python-hug/2.6.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • 697 days old (needed 5 days)
• golang-github-bifurcation-mint (- to 0.0~git20200214.93c820e-1)
  • Migration status for golang-github-bifurcation-mint (- to 0.0~git20200214.93c820e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-bifurcation-mint/0.0~git20200214.93c820e-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
    • 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-bifurcation-mint.html
    • 698 days old (needed 5 days)
• isakmpd (- to 20041012-10)
  • Migration status for isakmpd (- to 20041012-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating isakmpd would introduce bugs in testing: #970915
    • Depends: isakmpd openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/isakmpd.html
    • 698 days old (needed 5 days)
• debiman (- to 0.0~git20200217.fc82521-1)
  • Migration status for debiman (- to 0.0~git20200217.fc82521-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debiman would introduce bugs in testing: #983010
    • autopkgtest for debiman/0.0~git20200217.fc82521-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • debiman/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/armel has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/armhf has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/i386 has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.7-1
    • debiman/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.6-1
    • debiman/s390x has unsatisfiable Built-Using on golang-1.15 1.15.6-1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debiman.html
    • 699 days old (needed 5 days)
• keras (- to 2.3.1+dfsg-3)
  • Migration status for keras (- to 2.3.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating keras would introduce bugs in testing: #1009094, #997068
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keras.html
    • autopkgtest for keras/2.3.1+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 699 days old (needed 2 days)
• php-horde (- to 5.2.23+debian0-5)
  • Migration status for php-horde (- to 5.2.23+debian0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde php-horde-argv (not considered)
    • Invalidated by dependency
    • Depends: php-horde php-horde-auth
    • Depends: php-horde php-horde-core
    • Depends: php-horde php-horde-form
    • Depends: php-horde php-horde-rpc
    • Depends: php-horde php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • 703 days old (needed 5 days)
• ruby-jekyll-multiple-languages (- to 1.7.0+dfsg-1)
  • Migration status for ruby-jekyll-multiple-languages (- 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:
    • Depends: ruby-jekyll-multiple-languages jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-multiple-languages.html
    • autopkgtest for ruby-jekyll-multiple-languages/1.7.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 705 days old (needed 2 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-compress (not considered)
    • Invalidated by dependency
    • Depends: php-horde-whups php-horde
    • Depends: php-horde-whups php-horde-auth
    • Depends: php-horde-whups php-horde-core
    • Depends: php-horde-whups php-horde-form
    • Depends: php-horde-whups php-horde-mime-viewer
    • Depends: php-horde-whups php-horde-scheduler
    • Depends: php-horde-whups php-horde-text-filter
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
    • 706 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-mime-viewer (not considered)
    • Invalidated by dependency
    • Depends: php-horde-gollem php-horde
    • Depends: php-horde-gollem php-horde-auth
    • Depends: php-horde-gollem php-horde-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-gollem.html
    • 707 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
    • Depends: php-horde-trean php-horde-content
    • Depends: php-horde-trean php-horde-core
    • Depends: php-horde-trean php-horde-form
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
    • 707 days old (needed 5 days)
• golang-github-alangpierce-go-forceexport (- to 0.0~git20160317.8f1d694-2)
  • Migration status for golang-github-alangpierce-go-forceexport (- to 0.0~git20160317.8f1d694-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-alangpierce-go-forceexport would introduce bugs in testing: #997548
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alangpierce-go-forceexport.html
    • autopkgtest for golang-github-alangpierce-go-forceexport/0.0~git20160317.8f1d694-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 710 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-horde-auth (not considered)
    • Invalidated by dependency
    • Depends: php-horde-dav php-horde-core
    • Depends: php-horde-dav php-sabredav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
    • 710 days old (needed 5 days)
• php-horde-form (- to 2.0.20-2)
  • Migration status for php-horde-form (- to 2.0.20-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-form php-horde-core (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-form.html
    • 710 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-nag (not considered)
    • Invalidated by dependency
    • Depends: php-horde-groupware php-horde
    • Depends: php-horde-groupware php-horde-content
    • 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-timeobjects
    • Depends: php-horde-groupware php-horde-trean
    • Depends: php-horde-groupware php-horde-turba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-groupware.html
    • 710 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
    • 710 days old (needed 5 days)
• php-horde-rpc (- to 2.1.9-1)
  • Migration status for php-horde-rpc (- to 2.1.9-1): 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-core (not considered)
    • Invalidated by dependency
    • Depends: php-horde-rpc php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
    • 710 days old (needed 5 days)
• php-horde-scheduler (- to 2.0.3-6)
  • Migration status for php-horde-scheduler (- to 2.0.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-scheduler php-horde-core (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-scheduler.html
    • 710 days old (needed 5 days)
• php-horde-timeobjects (- to 2.1.4-6)
  • Migration status for php-horde-timeobjects (- to 2.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-timeobjects php-horde-core (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-timeobjects.html
    • 710 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-imp (not considered)
    • Invalidated by dependency
    • Depends: php-horde-webmail php-horde
    • Depends: php-horde-webmail php-horde-content
    • Depends: php-horde-webmail php-horde-gollem
    • 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-timeobjects
    • Depends: php-horde-webmail php-horde-trean
    • Depends: php-horde-webmail php-horde-turba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-webmail.html
    • 710 days old (needed 5 days)
• haskell-lambdabot-haskell-plugins (- to 5.3-3)
  • Migration status for haskell-lambdabot-haskell-plugins (- to 5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-lambdabot-haskell-plugins haskell-hoogle (not considered)
    • Build-Depends-Indep: haskell-lambdabot-haskell-plugins haskell-hoogle (not considered)
    • Depends: haskell-lambdabot-haskell-plugins haskell-hoogle (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-lambdabot-haskell-plugins.html
    • 711 days old (needed 5 days)
• prometheus-tplink-plug-exporter (- to 0.2.0+git20200622.cc4a731-2)
  • Migration status for prometheus-tplink-plug-exporter (- to 0.2.0+git20200622.cc4a731-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prometheus-tplink-plug-exporter would introduce bugs in testing: #1002282
    • prometheus-tplink-plug-exporter/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • prometheus-tplink-plug-exporter/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-tplink-plug-exporter.html
    • 711 days old (needed 5 days)
• gri (- to 2.12.27-1)
  • Migration status for gri (- to 2.12.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gri/amd64 has unsatisfiable dependency
    • gri/arm64 has unsatisfiable dependency
    • gri/armel has unsatisfiable dependency
    • gri/armhf has unsatisfiable dependency
    • gri/i386 has unsatisfiable dependency
    • gri/mips64el has unsatisfiable dependency
    • gri/mipsel has unsatisfiable dependency
    • gri/ppc64el has unsatisfiable dependency
    • gri/s390x has unsatisfiable dependency
    • Updating gri would introduce bugs in testing: #991057
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gri.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
    • 714 days old (needed 5 days)
• dpaste (- to 0.4.0-1)
  • Migration status for dpaste (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dpaste would introduce bugs in testing: #975501
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dpaste.html
    • 716 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
    • 717 days old (needed 5 days)
• haskell-gtk-sni-tray (- to 0.1.6.0-2)
  • Migration status for haskell-gtk-sni-tray (- to 0.1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gtk-sni-tray-dev/armhf has unsatisfiable dependency
    • libghc-gtk-sni-tray-prof/armhf has unsatisfiable dependency
    • Impossible Depends: haskell-gtk-sni-tray -> libffi7/3.3-6/armhf
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gi-dbusmenugtk3
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gi-gdkpixbuf
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gi-gtk
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gtk-strut
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gi-dbusmenugtk3
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gi-gdk
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gi-gdkpixbuf
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gi-gtk
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gtk-strut
    • Depends: haskell-gtk-sni-tray haskell-gi-dbusmenugtk3
    • Depends: haskell-gtk-sni-tray haskell-gi-gdk
    • Depends: haskell-gtk-sni-tray haskell-gi-gdkpixbuf
    • Depends: haskell-gtk-sni-tray haskell-gi-gtk
    • Depends: haskell-gtk-sni-tray haskell-gtk-strut
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gtk-sni-tray.html
    • uninstallable on arch armhf, not running autopkgtest there
    • 718 days old (needed 5 days)
• highlighting-kate (- to 0.6.4-6)
  • Migration status for highlighting-kate (- to 0.6.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating highlighting-kate would introduce bugs in testing: #963737
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/highlighting-kate.html
    • 718 days old (needed 5 days)
• python-pymzml (- to 2.4.7-3)
  • Migration status for python-pymzml (- to 2.4.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pymzml would introduce bugs in testing: #997417
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pymzml.html
    • 718 days old (needed 5 days)
• hexxagon (- to 1.0pl1-3.2)
  • Migration status for hexxagon (- to 1.0pl1-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hexxagon would introduce bugs in testing: #999025
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hexxagon.html
    • 723 days old (needed 5 days)
• cegui-mk2 (- to 0.8.7-9)
  • Migration status for cegui-mk2 (- to 0.8.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-libcegui-mk2-0.8.7/amd64 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/arm64 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/armel has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/armhf has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/i386 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/mips64el has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/mipsel has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/ppc64el has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): cegui-mk2 ogre-1.9
    • Depends: cegui-mk2 ogre-1.9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cegui-mk2.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
    • 726 days old (needed 5 days)
• haskell-gtk-strut (- to 0.1.3.0-2)
  • Migration status for haskell-gtk-strut (- to 0.1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gtk-strut-dev/armhf has unsatisfiable dependency
    • libghc-gtk-strut-prof/armhf has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gtk-strut haskell-gi-gdk
    • Build-Depends(-Arch): haskell-gtk-strut haskell-gi-gtk
    • Build-Depends-Indep: haskell-gtk-strut haskell-gi-gdk
    • Build-Depends-Indep: haskell-gtk-strut haskell-gi-gtk
    • Depends: haskell-gtk-strut haskell-gi-gdk
    • Depends: haskell-gtk-strut haskell-gi-gtk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gtk-strut.html
    • uninstallable on arch armhf, not running autopkgtest there
    • 727 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:
    • Updating lix would introduce bugs in testing: #999750
    • Impossible Depends: lix -> libphobos2-ldc-shared94/1:1.24.0-2/amd64
    • Impossible Depends: lix -> libphobos2-ldc-shared94/1:1.24.0-2/arm64
    • Impossible Depends: lix -> libphobos2-ldc-shared94/1:1.24.0-2/armhf
    • Impossible Depends: lix -> libphobos2-ldc-shared94/1:1.24.0-2/i386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lix.html
    • 729 days old (needed 5 days)
• php-log (- to 1.13.2-1)
  • Migration status for php-log (- to 1.13.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-log php-db (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-log.html
    • autopkgtest for php-log/1.13.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 730 days old (needed 2 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
    • 732 days old (needed 5 days)
• xul-ext-exteditor (- to 2.0.4-1)
  • Migration status for xul-ext-exteditor (- to 2.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xul-ext-exteditor would introduce bugs in testing: #981484
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/x/xul-ext-exteditor.html
  • Additional info:
    • 734 days old (needed 5 days)
• aegisub (- to 3.2.2+dfsg-6)
  • Migration status for aegisub (- to 3.2.2+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aegisub/amd64 has unsatisfiable dependency
    • aegisub/arm64 has unsatisfiable dependency
    • aegisub/armel has unsatisfiable dependency
    • aegisub/armhf has unsatisfiable dependency
    • aegisub/i386 has unsatisfiable dependency
    • aegisub/mips64el has unsatisfiable dependency
    • aegisub/mipsel has unsatisfiable dependency
    • aegisub/ppc64el has unsatisfiable dependency
    • aegisub/s390x has unsatisfiable dependency
    • Updating aegisub would introduce bugs in testing: #997098
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aegisub.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
    • 735 days old (needed 5 days)
• frogatto (- to 1.3.1+dfsg-5)
  • Migration status for frogatto (- to 1.3.1+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • frogatto/amd64 has unsatisfiable dependency
    • frogatto/arm64 has unsatisfiable dependency
    • frogatto/armel has unsatisfiable dependency
    • frogatto/armhf has unsatisfiable dependency
    • frogatto/i386 has unsatisfiable dependency
    • frogatto/mips64el has unsatisfiable dependency
    • frogatto/mipsel has unsatisfiable dependency
    • frogatto/ppc64el has unsatisfiable dependency
    • frogatto/s390x has unsatisfiable dependency
    • Updating frogatto would introduce bugs in testing: #1010804
  • 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 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
    • 735 days old (needed 5 days)
• kworkflow (- to 20191112-1.1)
  • Migration status for kworkflow (- to 20191112-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kworkflow would introduce bugs in testing: #980575
    • autopkgtest for kworkflow/20191112-1.1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kworkflow.html
    • 735 days old (needed 5 days)
• libghemical (- to 3.0.0-4.3)
  • Migration status for libghemical (- to 3.0.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libghemical mpqc (not considered)
    • Depends: libghemical mpqc (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libghemical.html
    • 738 days old (needed 5 days)
• opensurgsim (- to 0.7.0-11)
  • Migration status for opensurgsim (- to 0.7.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libopensurgsim/amd64 has unsatisfiable dependency
    • libopensurgsim/arm64 has unsatisfiable dependency
    • libopensurgsim/armel has unsatisfiable dependency
    • libopensurgsim/armhf has unsatisfiable dependency
    • libopensurgsim/i386 has unsatisfiable dependency
    • libopensurgsim/mips64el has unsatisfiable dependency
    • libopensurgsim/mipsel has unsatisfiable dependency
    • libopensurgsim/ppc64el has unsatisfiable dependency
    • libopensurgsim/s390x has unsatisfiable dependency
    • Updating opensurgsim would introduce bugs in testing: #997265
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensurgsim.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
    • 738 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: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy-loom.html
    • 741 days old (needed 5 days)
• xwatch (- to 2.11-16)
  • Migration status for xwatch (- to 2.11-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xwatch would introduce bugs in testing: #999056
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xwatch.html
    • 742 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/mipsel 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:
    • Piuparts tested OK - 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 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
    • 743 days old (needed 5 days)
• mccs (- to 1:1.1-9)
  • Migration status for mccs (- to 1:1.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mccs would introduce bugs in testing: #984229
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mccs.html
    • autopkgtest for mccs/1:1.1-9: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 744 days old (needed 2 days)
• tome (- to 2.41-ah~0.git.20200131-1)
  • Migration status for tome (- to 2.41-ah~0.git.20200131-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • tome/amd64 has unsatisfiable dependency
    • tome/arm64 has unsatisfiable dependency
    • tome/armel has unsatisfiable dependency
    • tome/armhf has unsatisfiable dependency
    • tome/i386 has unsatisfiable dependency
    • tome/mips64el has unsatisfiable dependency
    • tome/mipsel has unsatisfiable dependency
    • tome/ppc64el has unsatisfiable dependency
    • tome/s390x has unsatisfiable dependency
    • Updating tome would introduce bugs in testing: #966065
  • 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 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
    • 744 days old (needed 5 days)
• ruby-gnome (- to 3.4.3-1)
  • Migration status for ruby-gnome (- to 3.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gnome would introduce bugs in testing: #1000618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gnome.html
    • autopkgtest for ruby-gnome/3.4.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 745 days old (needed 2 days)
• rdist (- to 6.1.5-21)
  • Migration status for rdist (- to 6.1.5-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rdist would introduce bugs in testing: #962065
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdist.html
    • autopkgtest for rdist/6.1.5-21: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 748 days old (needed 2 days)
• g3data (- to 1:1.5.3-3)
  • Migration status for g3data (- to 1:1.5.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating g3data would introduce bugs in testing: #999267
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/g3data.html
    • 754 days old (needed 5 days)
• r-cran-gprofiler (- to 0.7.0-2)
  • Migration status for r-cran-gprofiler (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-gprofiler would introduce bugs in testing: #994212
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gprofiler.html
    • autopkgtest for r-cran-gprofiler/0.7.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 754 days old (needed 2 days)
• android-platform-tools-analytics-library (- to 2.2.2-3)
  • Migration status for android-platform-tools-analytics-library (- to 2.2.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): android-platform-tools-analytics-library android-platform-tools-base (not considered)
    • Depends: android-platform-tools-analytics-library android-platform-tools-base (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-tools-analytics-library.html
    • 756 days old (needed 5 days)
• android-sdk-helper (- to 0.2)
  • Migration status for android-sdk-helper (- to 0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-sdk-helper android-platform-tools-base (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-sdk-helper.html
    • 757 days old (needed 5 days)
• gost-crypto (- to 0.3.3-1)
  • Migration status for gost-crypto (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gost-crypto would introduce bugs in testing: #1005399
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gost-crypto.html
  • Additional info:
    • 757 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)
    • 758 days old (needed 5 days)
• d-itg (- to 2.8.1-r1023-4)
  • Migration status for d-itg (- to 2.8.1-r1023-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating d-itg would introduce bugs in testing: #984030
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/d-itg.html
    • 758 days old (needed 5 days)
• dmarcts-report-parser (- to 1.0+git20190809.1.bb5dd8b6-3)
  • Migration status for dmarcts-report-parser (- to 1.0+git20190809.1.bb5dd8b6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dmarcts-report-parser.html
    • 759 days old (needed 5 days)
• drmaa (- to 0.7.9-2)
  • Migration status for drmaa (- to 0.7.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for drmaa/0.7.9-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmaa.html
    • 759 days old (needed 5 days)
• gearhead2 (- to 0.701-2)
  • Migration status for gearhead2 (- to 0.701-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: gearhead2 openimageio (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gearhead2.html
    • 759 days old (needed 5 days)
• quickml (- to 0.7-6)
  • Migration status for quickml (- to 0.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickml would introduce bugs in testing: #999304
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickml.html
    • 760 days old (needed 5 days)
• netsend (- to 0.0~svnr250-1.4)
  • Migration status for netsend (- to 0.0~svnr250-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netsend would introduce bugs in testing: #1011647, #965747, #999046
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netsend.html
    • 761 days old (needed 5 days)
• rust-ncurses (- to 5.99.0-3)
  • Migration status for rust-ncurses (- to 5.99.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ncurses would introduce bugs in testing: #972100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ncurses.html
    • autopkgtest for rust-ncurses/5.99.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 761 days old (needed 2 days)
• esekeyd (- to 1.2.7-2)
  • Migration status for esekeyd (- to 1.2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating esekeyd would introduce bugs in testing: #999115
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch armhf binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Not built on buildd: upload info for arch mipsel binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esekeyd.html
    • 762 days old (needed 5 days)
• cpufreqd (- to 2.4.2-2.3)
  • Migration status for cpufreqd (- to 2.4.2-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpufreqd would introduce bugs in testing: #999096
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpufreqd.html
    • 766 days old (needed 5 days)
• cbmc (- to 5.12-5)
  • Migration status for cbmc (- to 5.12-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cbmc would introduce bugs in testing: #1004463, #984008
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cbmc.html
    • 767 days old (needed 5 days)
• wmxmms2 (- to 0.6+repack-3)
  • Migration status for wmxmms2 (- to 0.6+repack-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wmxmms2 xmms2 (not considered)
    • Depends: wmxmms2 xmms2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmxmms2.html
    • 768 days old (needed 5 days)
• ruby-jekyll-last-modified-at (- to 1.3.0-1)
  • Migration status for ruby-jekyll-last-modified-at (- to 1.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): ruby-jekyll-last-modified-at jekyll (not considered)
    • Depends: ruby-jekyll-last-modified-at jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-last-modified-at.html
    • autopkgtest for ruby-jekyll-last-modified-at/1.3.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 769 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:
    • Updating sipxtapi would introduce bugs in testing: #984331
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sipxtapi.html
    • 769 days old (needed 5 days)
• php-db (- to 1.10.0-1)
  • Migration status for php-db (- to 1.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-db would introduce bugs in testing: #1000596
    • autopkgtest for php-db/1.10.0-1: amd64: Not a regression, arm64: Not a regression, armhf: Regression ♻ (reference ♻), i386: Not a regression, ppc64el: Regression ♻ (reference ♻), s390x: Not a regression
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-db.html
    • 770 days old (needed 5 days)
• vzdump (- to 1.2.6-6)
  • Migration status for vzdump (- to 1.2.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vzdump/arm64 has unsatisfiable dependency
    • Depends: vzdump vzctl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vzdump.html
    • uninstallable on arch arm64, not running autopkgtest there
    • 773 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-asciidoc jekyll (not considered)
    • Depends: ruby-jekyll-asciidoc jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-asciidoc.html
    • autopkgtest for ruby-jekyll-asciidoc/3.0.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 779 days old (needed 2 days)
• rust-ogg (- to 0.7.0-1)
  • Migration status for rust-ogg (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-ogg+async-dev/amd64 has unsatisfiable dependency
    • librust-ogg+bytes-dev/amd64 has unsatisfiable dependency
    • librust-ogg+futures-dev/amd64 has unsatisfiable dependency
    • librust-ogg+async-dev/arm64 has unsatisfiable dependency
    • librust-ogg+bytes-dev/arm64 has unsatisfiable dependency
    • librust-ogg+futures-dev/arm64 has unsatisfiable dependency
    • librust-ogg+async-dev/armel has unsatisfiable dependency
    • librust-ogg+bytes-dev/armel has unsatisfiable dependency
    • librust-ogg+futures-dev/armel has unsatisfiable dependency
    • librust-ogg+async-dev/armhf has unsatisfiable dependency
    • librust-ogg+bytes-dev/armhf has unsatisfiable dependency
    • librust-ogg+futures-dev/armhf has unsatisfiable dependency
    • librust-ogg+async-dev/i386 has unsatisfiable dependency
    • librust-ogg+bytes-dev/i386 has unsatisfiable dependency
    • librust-ogg+futures-dev/i386 has unsatisfiable dependency
    • librust-ogg+async-dev/mips64el has unsatisfiable dependency
    • librust-ogg+bytes-dev/mips64el has unsatisfiable dependency
    • librust-ogg+futures-dev/mips64el has unsatisfiable dependency
    • librust-ogg+async-dev/mipsel has unsatisfiable dependency
    • librust-ogg+bytes-dev/mipsel has unsatisfiable dependency
    • librust-ogg+futures-dev/mipsel has unsatisfiable dependency
    • librust-ogg+async-dev/ppc64el has unsatisfiable dependency
    • librust-ogg+bytes-dev/ppc64el has unsatisfiable dependency
    • librust-ogg+futures-dev/ppc64el has unsatisfiable dependency
    • librust-ogg+async-dev/s390x has unsatisfiable dependency
    • librust-ogg+bytes-dev/s390x has unsatisfiable dependency
    • librust-ogg+futures-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-ogg.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
    • 779 days old (needed 5 days)
• rust-gstreamer (- to 0.14.5-2)
  • Migration status for rust-gstreamer (- to 0.14.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gstreamer+dox-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+futures-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+paste-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer+dox-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+futures-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+paste-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer+dox-dev/armel has unsatisfiable dependency
    • librust-gstreamer+futures-dev/armel has unsatisfiable dependency
    • librust-gstreamer+paste-dev/armel has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/armel has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/armel has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/armel has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/armel has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/armel has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/armel has unsatisfiable dependency
    • librust-gstreamer-dev/armel has unsatisfiable dependency
    • librust-gstreamer+dox-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+futures-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+paste-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-dev/armhf has unsatisfiable dependency
    • librust-gstreamer+dox-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+futures-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+paste-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-dev/i386 has unsatisfiable dependency
    • librust-gstreamer+dox-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+futures-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+paste-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer+dox-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+futures-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+paste-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer+dox-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+futures-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+paste-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer+dox-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+futures-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+paste-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+ser-de-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+subclassing-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+v1-10-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+v1-12-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+v1-14-dev/s390x has unsatisfiable dependency
    • librust-gstreamer+v1-16-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-dev/s390x has unsatisfiable dependency
    • Updating rust-gstreamer would introduce bugs in testing: #970104
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on amd64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on amd64: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on arm64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on arm64: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armel: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armel: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armhf: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on armhf: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on i386: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on i386: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on i386: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mips64el: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on mipsel: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-num-rational-0.2-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on s390x: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer unsatisfiable Build-Depends(-Arch) on s390x: librust-num-rational-0.2-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer.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
    • 780 days old (needed 5 days)
• rust-gstreamer-audio (- to 0.14.5-2)
  • Migration status for rust-gstreamer-audio (- to 0.14.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gstreamer-audio+dox-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-audio-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-audio-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/armel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/armel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/armel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/armel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/armel has unsatisfiable dependency
    • librust-gstreamer-audio-dev/armel has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-audio-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-audio-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-audio-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-audio-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-audio-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-audio+dox-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-audio+v1-10-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-audio+v1-12-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-audio+v1-14-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-audio+v1-16-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-audio-dev/s390x has unsatisfiable dependency
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-audio-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-audio-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-audio unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+v1-8-dev
    • Build-Depends(-Arch): rust-gstreamer-audio rust-gstreamer
    • Build-Depends(-Arch): rust-gstreamer-audio rust-gstreamer-base
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer-audio.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
    • 780 days old (needed 5 days)
• rust-gstreamer-base (- to 0.14.4-2)
  • Migration status for rust-gstreamer-base (- to 0.14.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gstreamer-base+dox-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base-dev/armel has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-base+dox-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-base+v1-10-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-base+v1-12-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-1-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-base+v1-14-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-base+v1-16-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-base-dev/s390x has unsatisfiable dependency
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-base unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+v1-8-dev
    • Build-Depends(-Arch): rust-gstreamer-base rust-gstreamer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer-base.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
    • 780 days old (needed 5 days)
• rust-gstreamer-video (- to 0.14.5-2)
  • Migration status for rust-gstreamer-video (- to 0.14.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gstreamer-video+dox-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-video-dev/amd64 has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-video-dev/arm64 has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/armel has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/armel has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/armel has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/armel has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/armel has unsatisfiable dependency
    • librust-gstreamer-video-dev/armel has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-video-dev/armhf has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-video-dev/i386 has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-video-dev/mips64el has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-video-dev/mipsel has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-video-dev/ppc64el has unsatisfiable dependency
    • librust-gstreamer-video+dox-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-video+v1-10-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-video+v1-12-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-video+v1-14-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-video+v1-16-dev/s390x has unsatisfiable dependency
    • librust-gstreamer-video-dev/s390x has unsatisfiable dependency
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on mipsel: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-video-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gobject-sys-0.9+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-base-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-base-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-sys-0.8+v1-8-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-video-sys-0.8+default-dev
    • rust-gstreamer-video unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-video-sys-0.8+v1-8-dev
    • Build-Depends(-Arch): rust-gstreamer-video rust-gstreamer
    • Build-Depends(-Arch): rust-gstreamer-video rust-gstreamer-base
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gstreamer-video.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
    • 780 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: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-librespot-protocol.html
    • 780 days old (needed 5 days)
• rust-libsodium-sys (- to 0.2.5-2)
  • Migration status for rust-libsodium-sys (- to 0.2.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-libsodium-sys/0.2.5-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libsodium-sys.html
    • 780 days old (needed 5 days)
• rust-xcb (- to 0.9.0-2)
  • Migration status for rust-xcb (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-xcb/0.9.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xcb.html
    • 780 days old (needed 5 days)
• gnome-shell-extension-xrdesktop (- to 0.14.0-3)
  • Migration status for gnome-shell-extension-xrdesktop (- to 0.14.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-xrdesktop would introduce bugs in testing: #993065
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-xrdesktop.html
    • 781 days old (needed 5 days)
• gnome-shell-xrdesktop (- to 3.36.1-2)
  • Migration status for gnome-shell-xrdesktop (- to 3.36.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-xrdesktop/amd64 has unsatisfiable dependency
    • gnome-shell-xrdesktop/arm64 has unsatisfiable dependency
    • gnome-shell-xrdesktop/armel has unsatisfiable dependency
    • gnome-shell-xrdesktop/armhf has unsatisfiable dependency
    • gnome-shell-xrdesktop/i386 has unsatisfiable dependency
    • gnome-shell-xrdesktop/mips64el has unsatisfiable dependency
    • gnome-shell-xrdesktop/mipsel has unsatisfiable dependency
    • gnome-shell-xrdesktop/ppc64el has unsatisfiable dependency
    • gnome-shell-xrdesktop/s390x has unsatisfiable dependency
    • Updating gnome-shell-xrdesktop would introduce bugs in testing: #1008471, #965277, #976372
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on amd64: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on amd64: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on arm64: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on arm64: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on armel: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on armel: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on armhf: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on armhf: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on i386: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on i386: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on mips64el: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on mips64el: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on mipsel: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on mipsel: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on ppc64el: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on ppc64el: libmutter-6-dev (>= 3.36.0)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on s390x: gir1.2-gweather-3.0 (>= 3.25.91)
    • gnome-shell-xrdesktop unsatisfiable Build-Depends(-Arch) on s390x: libmutter-6-dev (>= 3.36.0)
    • Build-Depends(-Arch): gnome-shell-xrdesktop xrdesktop
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-xrdesktop.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
    • 781 days old (needed 5 days)
• dropwatch (- to 1.5.3-1)
  • Migration status for dropwatch (- to 1.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dropwatch/amd64 has unsatisfiable dependency
    • dropwatch/arm64 has unsatisfiable dependency
    • dropwatch/armel has unsatisfiable dependency
    • dropwatch/armhf has unsatisfiable dependency
    • dropwatch/i386 has unsatisfiable dependency
    • dropwatch/mips64el has unsatisfiable dependency
    • dropwatch/mipsel has unsatisfiable dependency
    • dropwatch/ppc64el has unsatisfiable dependency
    • dropwatch/s390x has unsatisfiable dependency
    • Updating dropwatch would introduce bugs in testing: #949570, #964540
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dropwatch.html
  • Additional info:
    • 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
    • 782 days old (needed 5 days)
• pycallgraph (- to 1.1.3-1.2)
  • Migration status for pycallgraph (- to 1.1.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pycallgraph would introduce bugs in testing: #997631
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycallgraph.html
    • 782 days old (needed 5 days)
• rhc (- to 1.38.7-3)
  • Migration status for rhc (- to 1.38.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rhc would introduce bugs in testing: #908295
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rhc.html
    • 782 days old (needed 5 days)
• rust-aes-ctr (- to 0.3.0-2)
  • Migration status for rust-aes-ctr (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-aes-ctr-dev/amd64 has unsatisfiable dependency
    • librust-aes-ctr-dev/arm64 has unsatisfiable dependency
    • librust-aes-ctr-dev/armel has unsatisfiable dependency
    • librust-aes-ctr-dev/armhf has unsatisfiable dependency
    • librust-aes-ctr-dev/i386 has unsatisfiable dependency
    • librust-aes-ctr-dev/mips64el has unsatisfiable dependency
    • librust-aes-ctr-dev/mipsel has unsatisfiable dependency
    • librust-aes-ctr-dev/ppc64el has unsatisfiable dependency
    • librust-aes-ctr-dev/s390x has unsatisfiable dependency
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on amd64: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on arm64: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on armel: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on armhf: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on i386: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on mips64el: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on mipsel: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on ppc64el: librust-aes-soft-0.3+default-dev
    • rust-aes-ctr unsatisfiable Build-Depends(-Arch) on s390x: librust-aes-soft-0.3+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-aes-ctr.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
    • 782 days old (needed 5 days)
• rust-barrel (- to 0.6.5-2)
  • Migration status for rust-barrel (- to 0.6.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-barrel rust-diesel (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-barrel.html
    • autopkgtest for rust-barrel/0.6.5-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 782 days old (needed 2 days)
• rust-migrations-macros (- to 1.4.1-2)
  • Migration status for rust-migrations-macros (- to 1.4.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-migrations-macros rust-migrations-internals (not considered)
    • Depends: rust-migrations-macros rust-migrations-internals (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-migrations-macros.html
    • autopkgtest for rust-migrations-macros/1.4.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 782 days old (needed 5 days)
• rust-tokio-sync (- to 0.1.7-2)
  • Migration status for rust-tokio-sync (- to 0.1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-sync-dev/amd64 has unsatisfiable dependency
    • librust-tokio-sync-dev/arm64 has unsatisfiable dependency
    • librust-tokio-sync-dev/armel has unsatisfiable dependency
    • librust-tokio-sync-dev/armhf has unsatisfiable dependency
    • librust-tokio-sync-dev/i386 has unsatisfiable dependency
    • librust-tokio-sync-dev/mips64el has unsatisfiable dependency
    • librust-tokio-sync-dev/mipsel has unsatisfiable dependency
    • librust-tokio-sync-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-sync-dev/s390x has unsatisfiable dependency
    • Updating rust-tokio-sync would introduce bugs in testing: #998543
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-sync unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-sync.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
    • 782 days old (needed 5 days)
• rust-toml-edit (- to 0.1.5-2)
  • Migration status for rust-toml-edit (- to 0.1.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-toml-edit rust-combine (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-toml-edit.html
    • autopkgtest for rust-toml-edit/0.1.5-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 782 days old (needed 2 days)
• speedcrunch (- to 0.12.0-5)
  • Migration status for speedcrunch (- to 0.12.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating speedcrunch would introduce bugs in testing: #997366
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speedcrunch.html
    • 782 days old (needed 5 days)
• cloop (- to 3.14.1.3)
  • Migration status for cloop (- to 3.14.1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cloop would introduce bugs in testing: #1005413, #1005414
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cloop.html
    • 783 days old (needed 5 days)
• jekyll-theme-minima (- to 2.5.1-2)
  • Migration status for jekyll-theme-minima (- to 2.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): jekyll-theme-minima jekyll (not considered)
    • Depends: jekyll-theme-minima jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): jekyll-theme-minima ruby-jekyll-feed
    • Build-Depends(-Arch): jekyll-theme-minima ruby-jekyll-seo-tag
    • Depends: jekyll-theme-minima ruby-jekyll-feed
    • Depends: jekyll-theme-minima ruby-jekyll-seo-tag
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jekyll-theme-minima.html
    • autopkgtest for jekyll-theme-minima/2.5.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 783 days old (needed 5 days)
• open-build-service (- to 2.9.4-3)
  • Migration status for open-build-service (- to 2.9.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-build-service would introduce bugs in testing: #924233, #983784
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/open-build-service.html
    • autopkgtest for open-build-service/2.9.4-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • open-build-service unsatisfiable Build-Depends(-Arch) on amd64: python
    • Build-Depends(-Arch): open-build-service ruby-clockwork
    • Build-Depends(-Arch): open-build-service ruby-codemirror-rails
    • Build-Depends(-Arch): open-build-service ruby-flot-rails
    • Build-Depends(-Arch): open-build-service ruby-jquery-ui-rails
    • Build-Depends(-Arch): open-build-service ruby-riddle
    • Build-Depends(-Arch): open-build-service ruby-thinking-sphinx
    • Build-Depends(-Arch): open-build-service ruby-uglifier
    • Depends: open-build-service ruby-clockwork
    • Depends: open-build-service ruby-codemirror-rails
    • Depends: open-build-service ruby-flot-rails
    • Depends: open-build-service ruby-jquery-ui-rails
    • Depends: open-build-service ruby-riddle
    • Depends: open-build-service ruby-thinking-sphinx
    • Depends: open-build-service ruby-uglifier
  • Additional info:
    • 788 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 ♻ , arm64: Regression ♻ , ppc64el: Regression ♻
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mipsel
    • 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
    • 790 days old (needed 5 days)
• qnapi (- to 0.2.3-2)
  • Migration status for qnapi (- to 0.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qnapi would introduce bugs in testing: #997282
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qnapi.html
    • 790 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 790 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 790 days old (needed 5 days)
• ruby-redis-actionpack (- to 5.2.0-2)
  • Migration status for ruby-redis-actionpack (- to 5.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): ruby-redis-actionpack ruby-redis-store (not considered)
    • Depends: ruby-redis-actionpack ruby-redis-store (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-redis-actionpack ruby-redis-rack
    • Depends: ruby-redis-actionpack ruby-redis-rack
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-actionpack.html
    • autopkgtest for ruby-redis-actionpack/5.2.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 792 days old (needed 5 days)
• ruby-redis-rack (- to 2.1.2-4)
  • Migration status for ruby-redis-rack (- to 2.1.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-redis-rack ruby-redis-store (not considered)
    • Depends: ruby-redis-rack ruby-redis-store (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-rack.html
    • autopkgtest for ruby-redis-rack/2.1.2-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 792 days old (needed 2 days)
• labrea (- to 2.5-stable-3.1)
  • Migration status for labrea (- to 2.5-stable-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating labrea would introduce bugs in testing: #965615, #999220
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labrea.html
    • 793 days old (needed 5 days)
• google-authenticator (- to 20191231-2)
  • Migration status for google-authenticator (- to 20191231-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating google-authenticator would introduce bugs in testing: #1002239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/google-authenticator.html
    • 795 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/mipsel 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-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 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
    • 796 days old (needed 5 days)
• kfreebsd-10 (- to 10.3~svn300087+ds1-1)
  • Migration status for kfreebsd-10 (- to 10.3~svn300087+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kfreebsd-10 would introduce bugs in testing: #978513
    • Build-Depends(-Arch): kfreebsd-10 freebsd-buildutils
    • Build-Depends(-Arch): kfreebsd-10 freebsd-glue
    • Build-Depends(-Arch): kfreebsd-10 freebsd-libs
    • Build-Depends(-Arch): kfreebsd-10 gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kfreebsd-10.html
    • 799 days old (needed 5 days)
• pepper (- to 0.3.3-4)
  • Migration status for pepper (- to 0.3.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pepper would introduce bugs in testing: #984287
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pepper.html
    • 802 days old (needed 5 days)
• gr-gsm (- to 0.42.2.20200214-1)
  • Migration status for gr-gsm (- to 0.42.2.20200214-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gr-gsm/amd64 has unsatisfiable dependency
    • gr-gsm/arm64 has unsatisfiable dependency
    • gr-gsm/armel has unsatisfiable dependency
    • gr-gsm/armhf has unsatisfiable dependency
    • gr-gsm/i386 has unsatisfiable dependency
    • gr-gsm/mips64el has unsatisfiable dependency
    • gr-gsm/mipsel has unsatisfiable dependency
    • gr-gsm/ppc64el has unsatisfiable dependency
    • Updating gr-gsm would introduce bugs in testing: #1002113
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gr-gsm.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
    • 804 days old (needed 5 days)
• gramophone2 (- to 0.8.13a-3.1)
  • Migration status for gramophone2 (- to 0.8.13a-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gramophone2 would introduce bugs in testing: #965567, #966862
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gramophone2.html
    • 805 days old (needed 5 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:
    • Updating gcc-9-cross-mipsen would introduce bugs in testing: #946352, #963998
    • Impossible Depends: gcc-9-cross-mipsen -> libisl22/0.22.1-1/amd64
    • Impossible Depends: gcc-9-cross-mipsen -> libisl22/0.22.1-1/arm64
    • Impossible Depends: gcc-9-cross-mipsen -> libisl22/0.22.1-1/i386
    • Impossible Depends: gcc-9-cross-mipsen -> libisl22/0.22.1-1/mips64el
    • Impossible Depends: gcc-9-cross-mipsen -> libisl22/0.22.1-1/mipsel
    • Impossible Depends: gcc-9-cross-mipsen -> libisl22/0.22.1-1/ppc64el
    • Build-Depends(-Arch): gcc-9-cross-mipsen gcc-9
    • Built-Using: gcc-9-cross-mipsen gcc-9
    • Depends: gcc-9-cross-mipsen gcc-9
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross-mipsen.html
    • 807 days old (needed 5 days)
• apertium-mk-bg (- to 0.2.0~r49489-3)
  • Migration status for apertium-mk-bg (- to 0.2.0~r49489-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-mk-bg would introduce bugs in testing: #1005661
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-mk-bg.html
    • 808 days old (needed 5 days)
• ruby-grape-logging (- to 1.8.3-1)
  • Migration status for ruby-grape-logging (- to 1.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): ruby-grape-logging ruby-grape (not considered)
    • Depends: ruby-grape-logging ruby-grape (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape-logging.html
    • autopkgtest for ruby-grape-logging/1.8.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 809 days old (needed 2 days)
• apertium-is-sv (- to 0.1.0~r76450-3)
  • Migration status for apertium-is-sv (- to 0.1.0~r76450-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-is-sv would introduce bugs in testing: #1005659
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-is-sv.html
    • 810 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
    • 811 days old (needed 5 days)
• apertium-es-ast (- to 1.1.0~r51165-3)
  • Migration status for apertium-es-ast (- to 1.1.0~r51165-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-es-ast would introduce bugs in testing: #1005663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-es-ast.html
    • 813 days old (needed 5 days)
• pytds (- to 1.10.0-1)
  • Migration status for pytds (- to 1.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytds would introduce bugs in testing: #1002386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytds.html
    • autopkgtest for pytds/1.10.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 813 days old (needed 5 days)
• apertium-en-es (- to 0.8.0~r57502-5)
  • Migration status for apertium-en-es (- to 0.8.0~r57502-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-en-es would introduce bugs in testing: #1002244
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-en-es.html
    • 818 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:
    • Updating libneo4j-client would introduce bugs in testing: #984187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libneo4j-client.html
    • 819 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:
    • Updating mahimahi would introduce bugs in testing: #984228
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mahimahi.html
    • 824 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/mipsel 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 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
    • 826 days old (needed 5 days)
• ruby-jekyll-paginate-v2 (- to 3.0.0-1)
  • Migration status for ruby-jekyll-paginate-v2 (- to 3.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): ruby-jekyll-paginate-v2 jekyll (not considered)
    • Depends: ruby-jekyll-paginate-v2 jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-paginate-v2.html
    • autopkgtest for ruby-jekyll-paginate-v2/3.0.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 826 days old (needed 2 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 jekyll (not considered)
    • Depends: ruby-jekyll-mentions jekyll (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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 827 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
    • 827 days old (needed 5 days)
• kvmtool (- to 0.20170904-1.1)
  • Migration status for kvmtool (- to 0.20170904-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kvmtool would introduce bugs in testing: #1006290, #966893
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kvmtool.html
    • 828 days old (needed 5 days)
• freelan (- to 2.2-3)
  • Migration status for freelan (- to 2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freelan would introduce bugs in testing: #996285
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freelan.html
    • 830 days old (needed 5 days)
• ruby-ferret (- to 0.11.8.7-2)
  • Migration status for ruby-ferret (- to 0.11.8.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-ferret/amd64 has unsatisfiable dependency
    • ruby-ferret/arm64 has unsatisfiable dependency
    • ruby-ferret/armel has unsatisfiable dependency
    • ruby-ferret/armhf has unsatisfiable dependency
    • ruby-ferret/i386 has unsatisfiable dependency
    • ruby-ferret/mips64el has unsatisfiable dependency
    • ruby-ferret/mipsel has unsatisfiable dependency
    • ruby-ferret/ppc64el has unsatisfiable dependency
    • ruby-ferret/s390x has unsatisfiable dependency
    • Updating ruby-ferret would introduce bugs in testing: #996227
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-ferret.html
  • Additional info:
    • 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
    • 835 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: 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: 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: 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: 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: 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
    • 836 days old (needed 5 days)
• gtk-gnutella (- to 1.1.15-1)
  • Migration status for gtk-gnutella (- to 1.1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtk-gnutella would introduce bugs in testing: #956000
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-gnutella.html
    • 836 days old (needed 5 days)
• nant (- to 0.92~rc1+dfsg-7)
  • Migration status for nant (- to 0.92~rc1+dfsg-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: nant log4net (not considered)
    • Depends: nant log4net (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nant.html
    • 836 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/mipsel has unsatisfiable dependency
    • php-sass/ppc64el has unsatisfiable dependency
    • php-sass/s390x has unsatisfiable dependency
  • 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 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
    • 836 days old (needed 5 days)
• intercal (- to 30:0.30-3)
  • Migration status for intercal (- to 30:0.30-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intercal would introduce bugs in testing: #957366
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intercal.html
    • 837 days old (needed 5 days)
• haskell-taskell (- to 1.4.0.0-1)
  • Migration status for haskell-taskell (- to 1.4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-taskell-dev/amd64 has unsatisfiable dependency
    • libghc-taskell-doc/amd64 has unsatisfiable dependency
    • libghc-taskell-prof/amd64 has unsatisfiable dependency
    • libghc-taskell-dev/arm64 has unsatisfiable dependency
    • libghc-taskell-doc/arm64 has unsatisfiable dependency
    • libghc-taskell-prof/arm64 has unsatisfiable dependency
    • libghc-taskell-dev/armhf has unsatisfiable dependency
    • libghc-taskell-prof/armhf has unsatisfiable dependency
    • libghc-taskell-dev/i386 has unsatisfiable dependency
    • libghc-taskell-prof/i386 has unsatisfiable dependency
    • libghc-taskell-dev/ppc64el has unsatisfiable dependency
    • libghc-taskell-prof/ppc64el has unsatisfiable dependency
    • Updating haskell-taskell would introduce bugs in testing: #964917
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-brick-dev (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-brick-prof (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-http-client-dev (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-http-client-prof (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-prof (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-vty-dev (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-vty-prof (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-brick-dev (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-brick-prof (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-http-client-dev (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-http-client-prof (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-prof (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-vty-dev (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-vty-prof (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-brick-dev (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-brick-prof (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-http-client-dev (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-http-client-prof (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-prof (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-vty-dev (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-vty-prof (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-brick-dev (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-brick-prof (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-http-client-dev (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-http-client-prof (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-prof (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-vty-dev (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on i386: libghc-vty-prof (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-brick-dev (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-brick-prof (<< 0.48)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-http-client-dev (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-http-client-prof (<< 0.6)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-prof (<< 4.18)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vty-dev (<< 5.26)
    • haskell-taskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vty-prof (<< 5.26)
    • Not built on buildd: arch amd64 binaries uploaded by schizo
    • Not built on buildd: arch all binaries uploaded by schizo, a new source-only upload is needed to allow migration
    • Impossible Depends: haskell-taskell -> libffi7/3.3-6/amd64
    • Impossible Depends: haskell-taskell -> libffi7/3.3-6/arm64
    • Impossible Depends: haskell-taskell -> libffi7/3.3-6/armhf
    • Impossible Depends: haskell-taskell -> libffi7/3.3-6/i386
    • Impossible Depends: haskell-taskell -> libffi7/3.3-6/ppc64el
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-taskell.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 838 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: #942737
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mod-gnutls.html
    • 838 days old (needed 5 days)
• pt-websocket (- to 0.2-9)
  • Migration status for pt-websocket (- to 0.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pt-websocket would introduce bugs in testing: #997744
    • pt-websocket/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pt-websocket/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pt-websocket.html
    • 838 days old (needed 5 days)
• ruby-jekyll-redirect-from (- to 0.16.0-2)
  • Migration status for ruby-jekyll-redirect-from (- to 0.16.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-redirect-from jekyll (not considered)
    • Depends: ruby-jekyll-redirect-from jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-jekyll-redirect-from ruby-jekyll-sitemap
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-redirect-from.html
    • autopkgtest for ruby-jekyll-redirect-from/0.16.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 838 days old (needed 2 days)
• ruby-jekyll-sass-converter (- to 1.5.2-2)
  • Migration status for ruby-jekyll-sass-converter (- to 1.5.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-jekyll-sass-converter jekyll (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-sass-converter.html
    • autopkgtest for ruby-jekyll-sass-converter/1.5.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 838 days old (needed 2 days)
• ruby-jekyll-sitemap (- to 1.4.0-2)
  • Migration status for ruby-jekyll-sitemap (- to 1.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): ruby-jekyll-sitemap jekyll (not considered)
    • Depends: ruby-jekyll-sitemap jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-jekyll-sitemap ruby-jekyll-last-modified-at
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-sitemap.html
    • autopkgtest for ruby-jekyll-sitemap/1.4.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 838 days old (needed 2 days)
• sarg (- to 2.4.0-1)
  • Migration status for sarg (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sarg would introduce bugs in testing: #966848
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/i386
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/mips64el
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/ppc64el
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/s390x
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.59+dfsg-1+b1/amd64
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.59+dfsg-1+b1/arm64
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.59+dfsg-1+b1/armel
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.59+dfsg-1+b1/armhf
    • Impossible Depends: sarg -> libldap-2.4-2/2.4.59+dfsg-1+b1/mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sarg.html
    • 838 days old (needed 5 days)
• ruby-omniauth-github (- to 1.4.0-1)
  • Migration status for ruby-omniauth-github (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-github would introduce bugs in testing: #999715
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-github.html
    • autopkgtest for ruby-omniauth-github/1.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 839 days old (needed 2 days)
• gnome-packagekit (- to 3.32.0-2)
  • Migration status for gnome-packagekit (- to 3.32.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-packagekit would introduce bugs in testing: #1002237
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-packagekit.html
    • 841 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: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc.html
    • 842 days old (needed 5 days)
• casparcg-server (- to 2.2.0+dfsg-2.1)
  • Migration status for casparcg-server (- to 2.2.0+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating casparcg-server would introduce bugs in testing: #947518
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 847 days old (needed 5 days)
• php-mail (- to 1.4.1-1)
  • Migration status for php-mail (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mail would introduce bugs in testing: #1000653
    • autopkgtest for php-mail/1.4.1-1: amd64: Not a regression, arm64: Not a regression, armhf: Regression ♻ (reference ♻), i386: Not a regression, ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mail.html
    • 849 days old (needed 5 days)
• hol-light (- to 20190729-4)
  • Migration status for hol-light (- to 20190729-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hol-light/amd64 has unsatisfiable dependency
    • hol-light/arm64 has unsatisfiable dependency
    • hol-light/armel has unsatisfiable dependency
    • hol-light/armhf has unsatisfiable dependency
    • hol-light/i386 has unsatisfiable dependency
    • hol-light/mips64el has unsatisfiable dependency
    • hol-light/mipsel has unsatisfiable dependency
    • hol-light/ppc64el has unsatisfiable dependency
    • hol-light/s390x has unsatisfiable dependency
    • Updating hol-light would introduce bugs in testing: #1002983
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hol-light.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
    • 850 days old (needed 5 days)
• purple-matrix (- to 0.0.0+git20191228-1)
  • Migration status for purple-matrix (- to 0.0.0+git20191228-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating purple-matrix would introduce bugs in testing: #855541
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purple-matrix.html
    • 850 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
    • autopkgtest for ruby-google-cloud-translate/1.3.0-2: armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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
    • 852 days old (needed 5 days)
• ruby-heroku-deflater (- to 0.6.3-2)
  • Migration status for ruby-heroku-deflater (- to 0.6.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-heroku-deflater would introduce bugs in testing: #1002118
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-heroku-deflater.html
    • autopkgtest for ruby-heroku-deflater/0.6.3-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 852 days old (needed 5 days)
• viewmol (- to 2.4.1-26)
  • Migration status for viewmol (- to 2.4.1-26): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating viewmol would introduce bugs in testing: #938774, #967229
    • viewmol unsatisfiable Build-Depends(-Arch) on amd64: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on arm64: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on armel: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on armhf: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on i386: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on mips64el: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on mipsel: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on ppc64el: python-dev
    • viewmol unsatisfiable Build-Depends(-Arch) on s390x: python-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/viewmol.html
    • 852 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
    • 853 days old (needed 5 days)
• nomacs (- to 3.12.0+dfsg-3)
  • Migration status for nomacs (- to 3.12.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomacs would introduce bugs in testing: #974616
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomacs.html
    • 853 days old (needed 5 days)
• php-finder-facade (- to 1.2.3-1)
  • Migration status for php-finder-facade (- to 1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-finder-facade would introduce bugs in testing: #977801
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-finder-facade.html
    • autopkgtest for php-finder-facade/1.2.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 853 days old (needed 2 days)
• pynwb (- to 1.2.1-2)
  • Migration status for pynwb (- to 1.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pynwb would introduce bugs in testing: #978257
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynwb.html
    • autopkgtest for pynwb/1.2.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 853 days old (needed 5 days)
• ember (- to 0.8.0~snap1)
  • Migration status for ember (- to 0.8.0~snap1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ember/mips64el has unsatisfiable dependency
    • ember/mipsel has unsatisfiable dependency
    • Updating ember would introduce bugs in testing: #950926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ember.html
    • 854 days old (needed 5 days)
• flang (- to 20190329-5)
  • Migration status for flang (- to 20190329-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • flang-7/amd64 has unsatisfiable dependency
    • libflang0d-7/amd64 has unsatisfiable dependency
    • flang-7/arm64 has unsatisfiable dependency
    • libflang0d-7/arm64 has unsatisfiable dependency
    • flang-7/ppc64el has unsatisfiable dependency
    • libflang0d-7/ppc64el has unsatisfiable dependency
    • Updating flang would introduce bugs in testing: #947437, #957209
    • flang unsatisfiable Build-Depends(-Arch) on amd64: llvm-7
    • flang unsatisfiable Build-Depends(-Arch) on amd64: llvm-7-dev
    • flang unsatisfiable Build-Depends(-Arch) on amd64: libomp-7-dev
    • flang unsatisfiable Build-Depends(-Arch) on amd64: llvm-7-tools
    • flang unsatisfiable Build-Depends(-Arch) on arm64: llvm-7
    • flang unsatisfiable Build-Depends(-Arch) on arm64: llvm-7-dev
    • flang unsatisfiable Build-Depends(-Arch) on arm64: libomp-7-dev
    • flang unsatisfiable Build-Depends(-Arch) on arm64: llvm-7-tools
    • flang unsatisfiable Build-Depends(-Arch) on ppc64el: llvm-7
    • flang unsatisfiable Build-Depends(-Arch) on ppc64el: llvm-7-dev
    • flang unsatisfiable Build-Depends(-Arch) on ppc64el: libomp-7-dev
    • flang unsatisfiable Build-Depends(-Arch) on ppc64el: llvm-7-tools
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/flang.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
    • 857 days old (needed 5 days)
• vagrant-librarian-puppet (- to 0.9.2-2)
  • Migration status for vagrant-librarian-puppet (- to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vagrant-librarian-puppet would introduce bugs in testing: #978228
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-librarian-puppet.html
    • autopkgtest for vagrant-librarian-puppet/0.9.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 857 days old (needed 5 days)
• golang-github-xanzy-go-gitlab (- to 0.22.2-1)
  • Migration status for golang-github-xanzy-go-gitlab (- to 0.22.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-xanzy-go-gitlab would introduce bugs in testing: #953224
    • autopkgtest for golang-github-xanzy-go-gitlab/0.22.2-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by anarcat@koumbit.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-xanzy-go-gitlab.html
    • 859 days old (needed 5 days)
• libjpeg9 (- to 1:9d-1)
  • Migration status for libjpeg9 (- to 1:9d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libjpeg9 would introduce bugs in testing: #998986
    • 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
    • 859 days old (needed 5 days)
• xboxdrv (- to 0.8.8-2)
  • Migration status for xboxdrv (- to 0.8.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xboxdrv would introduce bugs in testing: #945748
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xboxdrv.html
    • 859 days old (needed 5 days)
• setbfree (- to 0.8.11-1)
  • Migration status for setbfree (- to 0.8.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating setbfree would introduce bugs in testing: #1008327
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/setbfree.html
    • 860 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-bindfs.html
    • 860 days old (needed 5 days)
• rsnapshot (- to 1.4.3-2)
  • Migration status for rsnapshot (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rsnapshot would introduce bugs in testing: #986709
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsnapshot.html
    • autopkgtest for rsnapshot/1.4.3-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 862 days old (needed 2 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: #997264
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seriousproton.html
    • 862 days old (needed 5 days)
• dicompyler (- to 0.4.2.0+git20200106.2643e0e-1)
  • Migration status for dicompyler (- to 0.4.2.0+git20200106.2643e0e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dicompyler would introduce bugs in testing: #985891
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dicompyler.html
    • 870 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 mpqc (not considered)
    • Depends: ghemical mpqc (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ghemical libghemical
    • Depends: ghemical libghemical
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghemical.html
    • 870 days old (needed 5 days)
• morse-simulator (- to 1.4-6)
  • Migration status for morse-simulator (- to 1.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-morse-simulator/amd64 has unsatisfiable dependency
    • python3-morse-simulator/arm64 has unsatisfiable dependency
    • python3-morse-simulator/armel has unsatisfiable dependency
    • python3-morse-simulator/armhf has unsatisfiable dependency
    • python3-morse-simulator/i386 has unsatisfiable dependency
    • python3-morse-simulator/mips64el has unsatisfiable dependency
    • python3-morse-simulator/mipsel has unsatisfiable dependency
    • python3-morse-simulator/ppc64el has unsatisfiable dependency
    • python3-morse-simulator/s390x has unsatisfiable dependency
    • Updating morse-simulator would introduce bugs in testing: #963651
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/morse-simulator.html
    • Depends: morse-simulator blender
  • Additional info:
    • 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
    • 872 days old (needed 5 days)
• polyml (- to 5.7.1-4)
  • Migration status for polyml (- to 5.7.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating polyml would introduce bugs in testing: #1007974
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • autopkgtest for polyml/5.7.1-4: amd64: Not a regression, arm64: Pass, armhf: Pass, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 873 days old (needed 5 days)
• lizardfs (- to 3.12.0+dfsg-4)
  • Migration status for lizardfs (- to 3.12.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lizardfs-cgi/amd64 has unsatisfiable dependency
    • lizardfs-cgiserv/amd64 has unsatisfiable dependency
    • lizardfs-cgi/arm64 has unsatisfiable dependency
    • lizardfs-cgiserv/arm64 has unsatisfiable dependency
    • lizardfs-cgiserv/armhf has unsatisfiable dependency
    • lizardfs-cgiserv/i386 has unsatisfiable dependency
    • lizardfs-cgiserv/mips64el has unsatisfiable dependency
    • lizardfs-cgiserv/ppc64el has unsatisfiable dependency
    • lizardfs-cgiserv/s390x has unsatisfiable dependency
    • Updating lizardfs would introduce bugs in testing: #1010542, #936955
    • missing build on armel
    • missing build on mipsel
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lizardfs.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 874 days old (needed 5 days)
• ruby-jekyll-github-metadata (- to 2.13.0-1)
  • Migration status for ruby-jekyll-github-metadata (- to 2.13.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-github-metadata jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-github-metadata.html
    • autopkgtest for ruby-jekyll-github-metadata/2.13.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 874 days old (needed 5 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
    • 875 days old (needed 5 days)
• hijra (- to 1.0-1)
  • Migration status for hijra (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hijra would introduce bugs in testing: #996063
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 875 days old (needed 5 days)
• gr-fcdproplus (- to 3.8~20190817-3)
  • Migration status for gr-fcdproplus (- to 3.8~20190817-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gr-fcdproplus/amd64 has unsatisfiable dependency
    • gr-fcdproplus/arm64 has unsatisfiable dependency
    • gr-fcdproplus/armel has unsatisfiable dependency
    • gr-fcdproplus/armhf has unsatisfiable dependency
    • gr-fcdproplus/i386 has unsatisfiable dependency
    • gr-fcdproplus/mips64el has unsatisfiable dependency
    • gr-fcdproplus/mipsel has unsatisfiable dependency
    • gr-fcdproplus/ppc64el has unsatisfiable dependency
    • gr-fcdproplus/s390x has unsatisfiable dependency
    • Updating gr-fcdproplus would introduce bugs in testing: #1002119
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-audio3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-blocks3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-fcdproplus -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/s390x
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gr-fcdproplus.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
    • 878 days old (needed 5 days)
• rust-sloppy-rfc4880 (- to 0.1.5-2)
  • Migration status for rust-sloppy-rfc4880 (- to 0.1.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-sloppy-rfc4880-dev/amd64 has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/arm64 has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/armel has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/armhf has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/i386 has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/mips64el has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/mipsel has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/ppc64el has unsatisfiable dependency
    • librust-sloppy-rfc4880-dev/s390x has unsatisfiable dependency
    • Updating rust-sloppy-rfc4880 would introduce bugs in testing: #974604
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on arm64: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on armel: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on armhf: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on i386: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on mips64el: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on mipsel: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • rust-sloppy-rfc4880 unsatisfiable Build-Depends(-Arch) on s390x: librust-base64-0.11+default-dev | librust-base64-0.10+default-dev
    • Build-Depends(-Arch): rust-sloppy-rfc4880 rust-sha-1
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-sloppy-rfc4880.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
    • 878 days old (needed 5 days)
• axtls (- to 2.1.5+ds-1)
  • Migration status for axtls (- to 2.1.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating axtls would introduce bugs in testing: #953326
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/axtls.html
    • autopkgtest for axtls/2.1.5+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 879 days old (needed 2 days)
• rust-cookie (- to 0.12.0-4)
  • Migration status for rust-cookie (- to 0.12.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cookie+base64-dev/amd64 has unsatisfiable dependency
    • librust-cookie+ring-dev/amd64 has unsatisfiable dependency
    • librust-cookie+secure-dev/amd64 has unsatisfiable dependency
    • librust-cookie+base64-dev/arm64 has unsatisfiable dependency
    • librust-cookie+ring-dev/arm64 has unsatisfiable dependency
    • librust-cookie+secure-dev/arm64 has unsatisfiable dependency
    • librust-cookie+base64-dev/armel has unsatisfiable dependency
    • librust-cookie+ring-dev/armel has unsatisfiable dependency
    • librust-cookie+secure-dev/armel has unsatisfiable dependency
    • librust-cookie+base64-dev/armhf has unsatisfiable dependency
    • librust-cookie+ring-dev/armhf has unsatisfiable dependency
    • librust-cookie+secure-dev/armhf has unsatisfiable dependency
    • librust-cookie+base64-dev/i386 has unsatisfiable dependency
    • librust-cookie+ring-dev/i386 has unsatisfiable dependency
    • librust-cookie+secure-dev/i386 has unsatisfiable dependency
    • librust-cookie+base64-dev/mips64el has unsatisfiable dependency
    • librust-cookie+ring-dev/mips64el has unsatisfiable dependency
    • librust-cookie+secure-dev/mips64el has unsatisfiable dependency
    • librust-cookie+base64-dev/mipsel has unsatisfiable dependency
    • librust-cookie+ring-dev/mipsel has unsatisfiable dependency
    • librust-cookie+secure-dev/mipsel has unsatisfiable dependency
    • librust-cookie+base64-dev/ppc64el has unsatisfiable dependency
    • librust-cookie+ring-dev/ppc64el has unsatisfiable dependency
    • librust-cookie+secure-dev/ppc64el has unsatisfiable dependency
    • librust-cookie+base64-dev/s390x has unsatisfiable dependency
    • librust-cookie+ring-dev/s390x has unsatisfiable dependency
    • librust-cookie+secure-dev/s390x has unsatisfiable dependency
    • Updating rust-cookie would introduce bugs in testing: #984919
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cookie.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
    • 884 days old (needed 5 days)
• rust-cssparser (- to 0.27.2-1)
  • Migration status for rust-cssparser (- to 0.27.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cssparser-dev/amd64 has unsatisfiable dependency
    • librust-cssparser-dev/arm64 has unsatisfiable dependency
    • librust-cssparser-dev/armel has unsatisfiable dependency
    • librust-cssparser-dev/armhf has unsatisfiable dependency
    • librust-cssparser-dev/i386 has unsatisfiable dependency
    • librust-cssparser-dev/mips64el has unsatisfiable dependency
    • librust-cssparser-dev/mipsel has unsatisfiable dependency
    • librust-cssparser-dev/ppc64el has unsatisfiable dependency
    • librust-cssparser-dev/s390x has unsatisfiable dependency
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on amd64: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on arm64: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on armel: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on armhf: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on i386: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on mips64el: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on mipsel: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+macros-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on s390x: librust-itoa-0.4+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+default-dev
    • rust-cssparser unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+macros-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cssparser.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
    • 884 days old (needed 5 days)
• cyphesis-cpp (- to 0.7.0~snap1)
  • Migration status for cyphesis-cpp (- to 0.7.0~snap1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cyphesis-cpp/mips64el has unsatisfiable dependency
    • cyphesis-cpp/mipsel has unsatisfiable dependency
    • Updating cyphesis-cpp would introduce bugs in testing: #948734
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cyphesis-cpp.html
  • Additional info:
    • 886 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 886 days old (needed 5 days)
• kopano-webapp-plugin-files (- to 2.1.5+dfsg1-2)
  • Migration status for kopano-webapp-plugin-files (- to 2.1.5+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kopano-webapp-plugin-files kopano-webapp (not considered)
    • Invalidated by dependency
    • Depends: kopano-webapp-plugin-files php-sabre-vobject
    • Depends: kopano-webapp-plugin-files php-sabredav
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kopano-webapp-plugin-files.html
    • 888 days old (needed 5 days)
• ruby-jekyll-compose (- to 0.12.0-4)
  • Migration status for ruby-jekyll-compose (- to 0.12.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-compose jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-compose.html
    • autopkgtest for ruby-jekyll-compose/0.12.0-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 888 days old (needed 5 days)
• chkservice (- to 0.3-1)
  • Migration status for chkservice (- to 0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chkservice would introduce bugs in testing: #984010, #988094
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chkservice.html
    • 890 days old (needed 5 days)
• rust-bcder (- to 0.4.1-1)
  • Migration status for rust-bcder (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-bcder-dev/amd64 has unsatisfiable dependency
    • librust-bcder-dev/arm64 has unsatisfiable dependency
    • librust-bcder-dev/armel has unsatisfiable dependency
    • librust-bcder-dev/armhf has unsatisfiable dependency
    • librust-bcder-dev/i386 has unsatisfiable dependency
    • librust-bcder-dev/mips64el has unsatisfiable dependency
    • librust-bcder-dev/mipsel has unsatisfiable dependency
    • librust-bcder-dev/ppc64el has unsatisfiable dependency
    • librust-bcder-dev/s390x has unsatisfiable dependency
    • Updating rust-bcder would introduce bugs in testing: #948632
    • rust-bcder unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on arm64: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on armel: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on armhf: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on i386: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on mips64el: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on mipsel: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on ppc64el: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • rust-bcder unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev
    • rust-bcder unsatisfiable Build-Depends(-Arch) on s390x: librust-smallvec-0.6+default-dev (>= 0.6.10-~~)
    • Not built on buildd: arch amd64 binaries uploaded by md
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-bcder.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
    • 890 days old (needed 5 days)
• redmine-plugin-local-avatars (- to 1.0.5-1)
  • Migration status for redmine-plugin-local-avatars (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine-plugin-local-avatars.html
  • Additional info:
    • 891 days old (needed 5 days)
• rust-clipboard (- to 0.5.0-2)
  • Migration status for rust-clipboard (- to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-clipboard/0.5.0-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Build-Depends(-Arch): rust-clipboard rust-x11-clipboard
    • Depends: rust-clipboard rust-x11-clipboard
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-clipboard.html
    • 893 days old (needed 5 days)
• rust-webbrowser (- to 0.5.2-2)
  • Migration status for rust-webbrowser (- to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-webbrowser/0.5.2-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-webbrowser.html
    • 893 days old (needed 5 days)
• dballe (- to 8.6-1)
  • Migration status for dballe (- to 8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-dballe/amd64 has unsatisfiable dependency
    • python3-dballe/arm64 has unsatisfiable dependency
    • python3-dballe/mips64el has unsatisfiable dependency
    • python3-dballe/ppc64el has unsatisfiable dependency
    • python3-dballe/s390x has unsatisfiable dependency
    • Updating dballe would introduce bugs in testing: #957123
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dballe.html
  • Additional info:
    • 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
    • 894 days old (needed 5 days)
• protobuf2 (- to 2.6.1-4)
  • Migration status for protobuf2 (- to 2.6.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating protobuf2 would introduce bugs in testing: #986070
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/protobuf2.html
    • 894 days old (needed 5 days)
• rust-pbkdf2 (- to 0.3.0-1)
  • Migration status for rust-pbkdf2 (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-pbkdf2+base64-dev/amd64 has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/amd64 has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/amd64 has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/amd64 has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/amd64 has unsatisfiable dependency
    • librust-pbkdf2-dev/amd64 has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/arm64 has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/arm64 has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/arm64 has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/arm64 has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/arm64 has unsatisfiable dependency
    • librust-pbkdf2-dev/arm64 has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/armel has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/armel has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/armel has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/armel has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/armel has unsatisfiable dependency
    • librust-pbkdf2-dev/armel has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/armhf has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/armhf has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/armhf has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/armhf has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/armhf has unsatisfiable dependency
    • librust-pbkdf2-dev/armhf has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/i386 has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/i386 has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/i386 has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/i386 has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/i386 has unsatisfiable dependency
    • librust-pbkdf2-dev/i386 has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/mips64el has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/mips64el has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/mips64el has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/mips64el has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/mips64el has unsatisfiable dependency
    • librust-pbkdf2-dev/mips64el has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/mipsel has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/mipsel has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/mipsel has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/mipsel has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/mipsel has unsatisfiable dependency
    • librust-pbkdf2-dev/mipsel has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/ppc64el has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/ppc64el has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/ppc64el has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/ppc64el has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/ppc64el has unsatisfiable dependency
    • librust-pbkdf2-dev/ppc64el has unsatisfiable dependency
    • librust-pbkdf2+base64-dev/s390x has unsatisfiable dependency
    • librust-pbkdf2+hmac-dev/s390x has unsatisfiable dependency
    • librust-pbkdf2+include-simple-dev/s390x has unsatisfiable dependency
    • librust-pbkdf2+rand-dev/s390x has unsatisfiable dependency
    • librust-pbkdf2+sha2-dev/s390x has unsatisfiable dependency
    • librust-pbkdf2-dev/s390x has unsatisfiable dependency
    • Updating rust-pbkdf2 would introduce bugs in testing: #974118
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on amd64: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on amd64: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on amd64: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on amd64: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on arm64: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on arm64: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on arm64: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on arm64: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on arm64: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armel: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armel: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armel: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armel: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armel: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armhf: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armhf: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armhf: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armhf: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on armhf: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on i386: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on i386: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on i386: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on i386: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on i386: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-sha2-0.8+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on s390x: librust-base64-0.10+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on s390x: librust-crypto-mac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on s390x: librust-hmac-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on s390x: librust-rand-0.7+default-dev
    • rust-pbkdf2 unsatisfiable Build-Depends(-Arch) on s390x: librust-sha2-0.8+default-dev
    • Not built on buildd: arch amd64 binaries uploaded by infinity0
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-pbkdf2.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
    • 894 days old (needed 5 days)
• rust-trust-dns-proto (- to 0.8.0-1)
  • Migration status for rust-trust-dns-proto (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-trust-dns-proto+mdns-dev/amd64 has unsatisfiable dependency
    • librust-trust-dns-proto-dev/amd64 has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/arm64 has unsatisfiable dependency
    • librust-trust-dns-proto-dev/arm64 has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/armel has unsatisfiable dependency
    • librust-trust-dns-proto-dev/armel has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/armhf has unsatisfiable dependency
    • librust-trust-dns-proto-dev/armhf has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/i386 has unsatisfiable dependency
    • librust-trust-dns-proto-dev/i386 has unsatisfiable dependency
    • librust-trust-dns-proto+dnssec-ring-dev/mips64el has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/mips64el has unsatisfiable dependency
    • librust-trust-dns-proto+ring-dev/mips64el has unsatisfiable dependency
    • librust-trust-dns-proto-dev/mips64el has unsatisfiable dependency
    • librust-trust-dns-proto+dnssec-ring-dev/mipsel has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/mipsel has unsatisfiable dependency
    • librust-trust-dns-proto+ring-dev/mipsel has unsatisfiable dependency
    • librust-trust-dns-proto-dev/mipsel has unsatisfiable dependency
    • librust-trust-dns-proto+dnssec-ring-dev/ppc64el has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/ppc64el has unsatisfiable dependency
    • librust-trust-dns-proto+ring-dev/ppc64el has unsatisfiable dependency
    • librust-trust-dns-proto-dev/ppc64el has unsatisfiable dependency
    • librust-trust-dns-proto+dnssec-ring-dev/s390x has unsatisfiable dependency
    • librust-trust-dns-proto+mdns-dev/s390x has unsatisfiable dependency
    • librust-trust-dns-proto+ring-dev/s390x has unsatisfiable dependency
    • librust-trust-dns-proto-dev/s390x has unsatisfiable dependency
    • Updating rust-trust-dns-proto would introduce bugs in testing: #974116
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on amd64: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on amd64: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on amd64: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on arm64: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on arm64: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on arm64: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on arm64: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armel: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armel: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armel: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armel: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armhf: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armhf: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armhf: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on armhf: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on i386: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on i386: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on i386: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on i386: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mips64el: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mips64el: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mips64el: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mips64el: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mipsel: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mipsel: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mipsel: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on mipsel: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on ppc64el: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on ppc64el: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on ppc64el: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on s390x: librust-enum-as-inner-0.3+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.28-~~)
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on s390x: librust-rand-0.7+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on s390x: librust-smallvec-0.6+default-dev
    • rust-trust-dns-proto unsatisfiable Build-Depends(-Arch) on s390x: librust-socket2-0.3+default-dev (>= 0.3.10-~~)
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
    • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-executor
    • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-io
    • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-reactor
    • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-tcp
    • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-timer
    • Build-Depends(-Arch): rust-trust-dns-proto rust-tokio-udp
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-trust-dns-proto.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
    • 895 days old (needed 5 days)
• ruby-jekyll-archives (- to 2.2.1-2)
  • Migration status for ruby-jekyll-archives (- to 2.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-archives jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-archives.html
    • autopkgtest for ruby-jekyll-archives/2.2.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 897 days old (needed 5 days)
• drawxtl (- to 5.5-5)
  • Migration status for drawxtl (- to 5.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drawxtl would introduce bugs in testing: #984039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drawxtl.html
    • 898 days old (needed 5 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
    • 901 days old (needed 5 days)
• php-fig-link-util (- to 1.1.0-1)
  • Migration status for php-fig-link-util (- to 1.1.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.1.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 901 days old (needed 2 days)
• sgml2x (- to 1.0.0-11.5)
  • Migration status for sgml2x (- to 1.0.0-11.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sgml2x would introduce bugs in testing: #965818, #999093
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sgml2x.html
    • 901 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 test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 903 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 904 days old (needed 2 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
    • 906 days old (needed 5 days)
• tntnet (- to 2.2.1-4)
  • Migration status for tntnet (- to 2.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): tntnet cxxtools (not considered)
    • Depends: tntnet cxxtools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: tntnet openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tntnet.html
    • 906 days old (needed 5 days)
• lifelines (- to 3.0.61-2.1)
  • Migration status for lifelines (- to 3.0.61-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lifelines would introduce bugs in testing: #670739
    • Build-Depends(-Arch): lifelines dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lifelines.html
    • 907 days old (needed 5 days)
• pathspider (- to 2.0.1-2.1)
  • Migration status for pathspider (- to 2.0.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pathspider would introduce bugs in testing: #906500
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pathspider.html
    • 908 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
    • 909 days old (needed 5 days)
• displaycal (- to 3.8.9.3-1)
  • Migration status for displaycal (- to 3.8.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • displaycal/amd64 has unsatisfiable dependency
    • displaycal/arm64 has unsatisfiable dependency
    • displaycal/armel has unsatisfiable dependency
    • displaycal/armhf has unsatisfiable dependency
    • displaycal/i386 has unsatisfiable dependency
    • displaycal/mips64el has unsatisfiable dependency
    • displaycal/mipsel has unsatisfiable dependency
    • displaycal/ppc64el has unsatisfiable dependency
    • displaycal/s390x has unsatisfiable dependency
    • Updating displaycal would introduce bugs in testing: #942988
    • displaycal unsatisfiable Build-Depends(-Arch) on amd64: python
    • displaycal unsatisfiable Build-Depends(-Arch) on arm64: python
    • displaycal unsatisfiable Build-Depends(-Arch) on armel: python
    • displaycal unsatisfiable Build-Depends(-Arch) on armhf: python
    • displaycal unsatisfiable Build-Depends(-Arch) on i386: python
    • displaycal unsatisfiable Build-Depends(-Arch) on mips64el: python
    • displaycal unsatisfiable Build-Depends(-Arch) on mipsel: python
    • displaycal unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • displaycal unsatisfiable Build-Depends(-Arch) on s390x: python
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/displaycal.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
    • 909 days old (needed 5 days)
• mountpy (- to 0.9)
  • Migration status for mountpy (- to 0.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mountpy would introduce bugs in testing: #965729, #999198
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mountpy.html
    • 912 days old (needed 5 days)
• emacs-jedi (- to 0.2.8-1)
  • Migration status for emacs-jedi (- to 0.2.8-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-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 913 days old (needed 2 days)
• funguloids (- to 1.06-14)
  • Migration status for funguloids (- to 1.06-14): 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
    • 913 days old (needed 5 days)
• itksnap (- to 3.6.0-5)
  • Migration status for itksnap (- to 3.6.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating itksnap would introduce bugs in testing: #1010549, #984068
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/i/itksnap.html
    • Build-Depends(-Arch): itksnap vtk6
  • Additional info:
    • 914 days old (needed 5 days)
• kopano-webapp (- to 3.5.14+dfsg1.orig-1)
  • Migration status for kopano-webapp (- to 3.5.14+dfsg1.orig-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/k/kopano-webapp.html
    • autopkgtest for kopano-webapp/3.5.14+dfsg1.orig-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Depends: kopano-webapp kopanocore
  • Additional info:
    • 915 days old (needed 5 days)
• ladish (- to 1+dfsg0-6)
  • Migration status for ladish (- to 1+dfsg0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ladish/amd64 has unsatisfiable dependency
    • ladish/arm64 has unsatisfiable dependency
    • ladish/armel has unsatisfiable dependency
    • ladish/armhf has unsatisfiable dependency
    • ladish/i386 has unsatisfiable dependency
    • ladish/mips64el has unsatisfiable dependency
    • ladish/mipsel has unsatisfiable dependency
    • ladish/ppc64el has unsatisfiable dependency
    • ladish/s390x has unsatisfiable dependency
    • Updating ladish would introduce bugs in testing: #936812
    • Build-Depends(-Arch): ladish flowcanvas
    • Depends: ladish flowcanvas
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/ladish.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
    • 916 days old (needed 5 days)
• lektor (- to 3.1.3-1)
  • Migration status for lektor (- to 3.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lektor would introduce bugs in testing: #1003566, #997323
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lektor.html
    • autopkgtest for lektor/3.1.3-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 917 days old (needed 5 days)
• incron (- to 0.5.12-2)
  • Migration status for incron (- to 0.5.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating incron would introduce bugs in testing: #947425
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/incron.html
    • 921 days old (needed 5 days)
• cpupower-gui (- to 0.7.2-2)
  • Migration status for cpupower-gui (- to 0.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpupower-gui would introduce bugs in testing: #1005618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpupower-gui.html
    • 922 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 922 days old (needed 2 days)
• zorp (- to 7.0.1~alpha2-3)
  • Migration status for zorp (- to 7.0.1~alpha2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libzorp-7.0/amd64 has unsatisfiable dependency
    • libzorp-dev/amd64 has unsatisfiable dependency
    • munin-plugins-zorp/amd64 has unsatisfiable dependency
    • nagios-plugins-zorp/amd64 has unsatisfiable dependency
    • zorp/amd64 has unsatisfiable dependency
    • zorp-modules/amd64 has unsatisfiable dependency
    • libzorp-7.0/arm64 has unsatisfiable dependency
    • libzorp-dev/arm64 has unsatisfiable dependency
    • munin-plugins-zorp/arm64 has unsatisfiable dependency
    • nagios-plugins-zorp/arm64 has unsatisfiable dependency
    • zorp/arm64 has unsatisfiable dependency
    • zorp-modules/arm64 has unsatisfiable dependency
    • libzorp-7.0/armel has unsatisfiable dependency
    • libzorp-dev/armel has unsatisfiable dependency
    • munin-plugins-zorp/armel has unsatisfiable dependency
    • nagios-plugins-zorp/armel has unsatisfiable dependency
    • zorp/armel has unsatisfiable dependency
    • zorp-modules/armel has unsatisfiable dependency
    • libzorp-7.0/armhf has unsatisfiable dependency
    • libzorp-dev/armhf has unsatisfiable dependency
    • munin-plugins-zorp/armhf has unsatisfiable dependency
    • nagios-plugins-zorp/armhf has unsatisfiable dependency
    • zorp/armhf has unsatisfiable dependency
    • zorp-modules/armhf has unsatisfiable dependency
    • libzorp-7.0/i386 has unsatisfiable dependency
    • libzorp-dev/i386 has unsatisfiable dependency
    • munin-plugins-zorp/i386 has unsatisfiable dependency
    • nagios-plugins-zorp/i386 has unsatisfiable dependency
    • zorp/i386 has unsatisfiable dependency
    • zorp-modules/i386 has unsatisfiable dependency
    • libzorp-7.0/mips64el has unsatisfiable dependency
    • libzorp-dev/mips64el has unsatisfiable dependency
    • munin-plugins-zorp/mips64el has unsatisfiable dependency
    • nagios-plugins-zorp/mips64el has unsatisfiable dependency
    • zorp/mips64el has unsatisfiable dependency
    • zorp-modules/mips64el has unsatisfiable dependency
    • libzorp-7.0/mipsel has unsatisfiable dependency
    • libzorp-dev/mipsel has unsatisfiable dependency
    • munin-plugins-zorp/mipsel has unsatisfiable dependency
    • nagios-plugins-zorp/mipsel has unsatisfiable dependency
    • zorp/mipsel has unsatisfiable dependency
    • zorp-modules/mipsel has unsatisfiable dependency
    • libzorp-7.0/ppc64el has unsatisfiable dependency
    • libzorp-dev/ppc64el has unsatisfiable dependency
    • munin-plugins-zorp/ppc64el has unsatisfiable dependency
    • nagios-plugins-zorp/ppc64el has unsatisfiable dependency
    • zorp/ppc64el has unsatisfiable dependency
    • zorp-modules/ppc64el has unsatisfiable dependency
    • libzorp-7.0/s390x has unsatisfiable dependency
    • libzorp-dev/s390x has unsatisfiable dependency
    • munin-plugins-zorp/s390x has unsatisfiable dependency
    • nagios-plugins-zorp/s390x has unsatisfiable dependency
    • zorp/s390x has unsatisfiable dependency
    • zorp-modules/s390x has unsatisfiable dependency
    • Updating zorp would introduce bugs in testing: #938921
    • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on amd64: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on amd64: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on arm64: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on arm64: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on armel: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on armel: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on armel: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on armel: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on armel: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on armel: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on armhf: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on armhf: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on i386: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on i386: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on i386: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on i386: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on i386: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on i386: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on mips64el: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on mips64el: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on mipsel: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on mipsel: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on ppc64el: python-netaddr
    • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-dev
    • zorp unsatisfiable Build-Depends(-Arch) on s390x: libzorpll-7.0-1-dev
    • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-dnspython
    • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-openssl (>= 0.10)
    • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-radix
    • zorp unsatisfiable Build-Depends(-Arch) on s390x: python-netaddr
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/z/zorp.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
    • 922 days old (needed 5 days)
• doscan (- to 0.3.3-1.1)
  • Migration status for doscan (- to 0.3.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating doscan would introduce bugs in testing: #984037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doscan.html
    • 932 days old (needed 5 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)
    • 936 days old (needed 5 days)
• ruby-omniauth-google-oauth2 (- to 0.6.0-2)
  • Migration status for ruby-omniauth-google-oauth2 (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-google-oauth2 would introduce bugs in testing: #999716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-google-oauth2.html
    • autopkgtest for ruby-omniauth-google-oauth2/0.6.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 937 days old (needed 2 days)
• rust-futures-cpupool (- to 0.1.8-2)
  • Migration status for rust-futures-cpupool (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-futures-cpupool+with-deprecated-dev/amd64 has unsatisfiable dependency
    • librust-futures-cpupool-dev/amd64 has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/arm64 has unsatisfiable dependency
    • librust-futures-cpupool-dev/arm64 has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/armel has unsatisfiable dependency
    • librust-futures-cpupool-dev/armel has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/armhf has unsatisfiable dependency
    • librust-futures-cpupool-dev/armhf has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/i386 has unsatisfiable dependency
    • librust-futures-cpupool-dev/i386 has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/mips64el has unsatisfiable dependency
    • librust-futures-cpupool-dev/mips64el has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/mipsel has unsatisfiable dependency
    • librust-futures-cpupool-dev/mipsel has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/ppc64el has unsatisfiable dependency
    • librust-futures-cpupool-dev/ppc64el has unsatisfiable dependency
    • librust-futures-cpupool+with-deprecated-dev/s390x has unsatisfiable dependency
    • librust-futures-cpupool-dev/s390x has unsatisfiable dependency
    • Updating rust-futures-cpupool would introduce bugs in testing: #997358
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+with-deprecated-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+use-std-dev
    • rust-futures-cpupool unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+with-deprecated-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-futures-cpupool.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
    • 937 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 ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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
    • 940 days old (needed 5 days)
• rust-tokio-io (- to 0.1.12-1)
  • Migration status for rust-tokio-io (- to 0.1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-io-dev/amd64 has unsatisfiable dependency
    • librust-tokio-io-dev/arm64 has unsatisfiable dependency
    • librust-tokio-io-dev/armel has unsatisfiable dependency
    • librust-tokio-io-dev/armhf has unsatisfiable dependency
    • librust-tokio-io-dev/i386 has unsatisfiable dependency
    • librust-tokio-io-dev/mips64el has unsatisfiable dependency
    • librust-tokio-io-dev/mipsel has unsatisfiable dependency
    • librust-tokio-io-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-io-dev/s390x has unsatisfiable dependency
    • Updating rust-tokio-io would introduce bugs in testing: #998570
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.18-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-tokio-io unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.18-~~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-io.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
    • 940 days old (needed 5 days)
• golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-2)
  • Migration status for golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-2): 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-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 942 days old (needed 2 days)
• rust-selectors (- to 0.21.0-1)
  • Migration status for rust-selectors (- to 0.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-selectors-dev/amd64 has unsatisfiable dependency
    • librust-selectors-dev/arm64 has unsatisfiable dependency
    • librust-selectors-dev/armel has unsatisfiable dependency
    • librust-selectors-dev/armhf has unsatisfiable dependency
    • librust-selectors-dev/i386 has unsatisfiable dependency
    • librust-selectors-dev/mips64el has unsatisfiable dependency
    • librust-selectors-dev/mipsel has unsatisfiable dependency
    • librust-selectors-dev/ppc64el has unsatisfiable dependency
    • librust-selectors-dev/s390x has unsatisfiable dependency
    • Updating rust-selectors would introduce bugs in testing: #951683
    • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on amd64: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on arm64: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armel: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on armhf: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on i386: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mips64el: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on mipsel: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on ppc64el: librust-smallvec-0.6+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-cssparser-0.25+default-dev
    • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-codegen-0.7+default-dev (>= 0.7.18-~~)
    • rust-selectors unsatisfiable Build-Depends(-Arch) on s390x: librust-smallvec-0.6+default-dev
    • Not built on buildd: arch amd64 binaries uploaded by sylvestre
    • Build-Depends(-Arch): rust-selectors rust-servo-arc
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-selectors.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
    • 942 days old (needed 5 days)
• ruby-jekyll-coffeescript (- to 1.2.2-2)
  • Migration status for ruby-jekyll-coffeescript (- to 1.2.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-coffeescript jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-coffeescript.html
    • autopkgtest for ruby-jekyll-coffeescript/1.2.2-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 943 days old (needed 5 days)
• ruby-jekyll-optional-front-matter (- to 0.3.2-1)
  • Migration status for ruby-jekyll-optional-front-matter (- to 0.3.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-optional-front-matter jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-optional-front-matter.html
    • autopkgtest for ruby-jekyll-optional-front-matter/0.3.2-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 943 days old (needed 5 days)
• ruby-jekyll-paginate (- to 1.1.0-3)
  • Migration status for ruby-jekyll-paginate (- to 1.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-jekyll-paginate jekyll (not considered)
    • Depends: ruby-jekyll-paginate jekyll (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-paginate.html
    • autopkgtest for ruby-jekyll-paginate/1.1.0-3: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 943 days old (needed 5 days)
• ruby-jekyll-relative-links (- to 0.6.1-1)
  • Migration status for ruby-jekyll-relative-links (- to 0.6.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-relative-links jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-relative-links.html
    • autopkgtest for ruby-jekyll-relative-links/0.6.1-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 943 days old (needed 5 days)
• ruby-jekyll-titles-from-headings (- to 0.5.3-1)
  • Migration status for ruby-jekyll-titles-from-headings (- to 0.5.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-titles-from-headings jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-titles-from-headings.html
    • autopkgtest for ruby-jekyll-titles-from-headings/0.5.3-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 943 days old (needed 5 days)
• rust-h2 (- to 0.1.26-1)
  • Migration status for rust-h2 (- to 0.1.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-h2-dev/amd64 has unsatisfiable dependency
    • librust-h2-dev/arm64 has unsatisfiable dependency
    • librust-h2-dev/armel has unsatisfiable dependency
    • librust-h2-dev/armhf has unsatisfiable dependency
    • librust-h2-dev/i386 has unsatisfiable dependency
    • librust-h2-dev/mips64el has unsatisfiable dependency
    • librust-h2-dev/mipsel has unsatisfiable dependency
    • librust-h2-dev/ppc64el has unsatisfiable dependency
    • librust-h2-dev/s390x has unsatisfiable dependency
    • Updating rust-h2 would introduce bugs in testing: #1009888
    • rust-h2 unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on amd64: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on arm64: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on armel: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on armhf: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on i386: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on mips64el: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on mipsel: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev (>= 0.4.7-~~)
    • rust-h2 unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev
    • rust-h2 unsatisfiable Build-Depends(-Arch) on s390x: librust-http-0.1+default-dev (>= 0.1.8-~~)
    • Build-Depends(-Arch): rust-h2 rust-tokio-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-h2.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
    • 945 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:
    • Updating gr-dab would introduce bugs in testing: #1002106
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-dab -> libgnuradio-filter3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-dab -> libgnuradio-pmt3.8.2/3.8.2.0-15+b1/s390x
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/amd64
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/arm64
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/armel
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/armhf
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/i386
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/mips64el
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/mipsel
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/ppc64el
    • Impossible Depends: gr-dab -> libgnuradio-runtime3.8.2/3.8.2.0-15+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gr-dab.html
    • autopkgtest for gr-dab/0.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 946 days old (needed 2 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsunit.html
    • 948 days old (needed 5 days)
• rust-jemalloc-sys (- to 0.3.2-2)
  • Migration status for rust-jemalloc-sys (- 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): rust-jemalloc-sys rust-fs-extra (not considered)
    • Depends: rust-jemalloc-sys rust-fs-extra (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-jemalloc-sys.html
    • autopkgtest for rust-jemalloc-sys/0.3.2-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 950 days old (needed 2 days)
• rust-combine (- to 3.8.1-1)
  • Migration status for rust-combine (- to 3.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-combine+combine-regex-1-dev/amd64 has unsatisfiable dependency
    • librust-combine+doc-dev/amd64 has unsatisfiable dependency
    • librust-combine+regex-dev/amd64 has unsatisfiable dependency
    • librust-combine+std-dev/amd64 has unsatisfiable dependency
    • librust-combine-dev/amd64 has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/arm64 has unsatisfiable dependency
    • librust-combine+doc-dev/arm64 has unsatisfiable dependency
    • librust-combine+regex-dev/arm64 has unsatisfiable dependency
    • librust-combine+std-dev/arm64 has unsatisfiable dependency
    • librust-combine-dev/arm64 has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/armel has unsatisfiable dependency
    • librust-combine+doc-dev/armel has unsatisfiable dependency
    • librust-combine+regex-dev/armel has unsatisfiable dependency
    • librust-combine+std-dev/armel has unsatisfiable dependency
    • librust-combine-dev/armel has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/armhf has unsatisfiable dependency
    • librust-combine+doc-dev/armhf has unsatisfiable dependency
    • librust-combine+regex-dev/armhf has unsatisfiable dependency
    • librust-combine+std-dev/armhf has unsatisfiable dependency
    • librust-combine-dev/armhf has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/i386 has unsatisfiable dependency
    • librust-combine+doc-dev/i386 has unsatisfiable dependency
    • librust-combine+regex-dev/i386 has unsatisfiable dependency
    • librust-combine+std-dev/i386 has unsatisfiable dependency
    • librust-combine-dev/i386 has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/mips64el has unsatisfiable dependency
    • librust-combine+doc-dev/mips64el has unsatisfiable dependency
    • librust-combine+regex-dev/mips64el has unsatisfiable dependency
    • librust-combine+std-dev/mips64el has unsatisfiable dependency
    • librust-combine-dev/mips64el has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/mipsel has unsatisfiable dependency
    • librust-combine+doc-dev/mipsel has unsatisfiable dependency
    • librust-combine+regex-dev/mipsel has unsatisfiable dependency
    • librust-combine+std-dev/mipsel has unsatisfiable dependency
    • librust-combine-dev/mipsel has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/ppc64el has unsatisfiable dependency
    • librust-combine+doc-dev/ppc64el has unsatisfiable dependency
    • librust-combine+regex-dev/ppc64el has unsatisfiable dependency
    • librust-combine+std-dev/ppc64el has unsatisfiable dependency
    • librust-combine-dev/ppc64el has unsatisfiable dependency
    • librust-combine+combine-regex-1-dev/s390x has unsatisfiable dependency
    • librust-combine+doc-dev/s390x has unsatisfiable dependency
    • librust-combine+regex-dev/s390x has unsatisfiable dependency
    • librust-combine+std-dev/s390x has unsatisfiable dependency
    • librust-combine-dev/s390x has unsatisfiable dependency
    • Updating rust-combine would introduce bugs in testing: #984914
    • rust-combine unsatisfiable Build-Depends(-Arch) on amd64: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on amd64: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on arm64: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on arm64: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on armel: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on armel: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on armhf: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on armhf: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on i386: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on i386: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on mips64el: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on mips64el: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on mipsel: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on mipsel: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ascii-0.9-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on s390x: librust-ascii-0.9+std-dev (>= 0.9.1-~~)
    • rust-combine unsatisfiable Build-Depends(-Arch) on s390x: librust-ascii-0.9-dev (>= 0.9.1-~~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-combine.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
    • 952 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
    • 953 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
    • 957 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gandi-cli.html
    • 957 days old (needed 5 days)
• sphinxcontrib-youtube (- to 1.0-1.1)
  • Migration status for sphinxcontrib-youtube (- to 1.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sphinxcontrib-youtube would introduce bugs in testing: #896348, #943690
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-youtube.html
    • 957 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
    • 962 days old (needed 5 days)
• python-defer (- to 1.0.6-2.1)
  • Migration status for python-defer (- to 1.0.6-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-defer would introduce bugs in testing: #997624
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-defer.html
    • 963 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
    • 965 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 966 days old (needed 2 days)
• rust-os-pipe (- to 0.9.1-1)
  • Migration status for rust-os-pipe (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-os-pipe/0.9.1-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-os-pipe.html
    • 966 days old (needed 5 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
    • 967 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
    • 971 days old (needed 5 days)
• python-libguess (- to 1.1-4)
  • Migration status for python-libguess (- to 1.1-4): 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
    • 971 days old (needed 5 days)
• flowcanvas (- to 0.7.1+dfsg0-0.5)
  • Migration status for flowcanvas (- to 0.7.1+dfsg0-0.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flowcanvas would introduce bugs in testing: #970406
    • flowcanvas unsatisfiable Build-Depends(-Arch) on amd64: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on arm64: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on armel: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on armhf: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on i386: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on mips64el: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on mipsel: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • flowcanvas unsatisfiable Build-Depends(-Arch) on s390x: python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flowcanvas.html
    • 972 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
    • 972 days old (needed 5 days)
• smlnj (- to 110.79-6)
  • Migration status for smlnj (- to 110.79-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smlnj would introduce bugs in testing: #998154
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlnj.html
    • 973 days old (needed 5 days)
• pyfg (- to 0.50-2)
  • Migration status for pyfg (- to 0.50-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfg would introduce bugs in testing: #960576
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfg.html
    • 978 days old (needed 5 days)
• gspiceui (- to 1.2.36+dfsg-1)
  • Migration status for gspiceui (- to 1.2.36+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gspiceui would introduce bugs in testing: #967915
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gspiceui.html
    • 979 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
    • 980 days old (needed 5 days)
• rust-hyper (- to 0.12.35-1)
  • Migration status for rust-hyper (- to 0.12.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-hyper+runtime-dev/amd64 has unsatisfiable dependency
    • librust-hyper+tokio-dev/amd64 has unsatisfiable dependency
    • librust-hyper-dev/amd64 has unsatisfiable dependency
    • librust-hyper+runtime-dev/arm64 has unsatisfiable dependency
    • librust-hyper+tokio-dev/arm64 has unsatisfiable dependency
    • librust-hyper-dev/arm64 has unsatisfiable dependency
    • librust-hyper+runtime-dev/armel has unsatisfiable dependency
    • librust-hyper+tokio-dev/armel has unsatisfiable dependency
    • librust-hyper-dev/armel has unsatisfiable dependency
    • librust-hyper+runtime-dev/armhf has unsatisfiable dependency
    • librust-hyper+tokio-dev/armhf has unsatisfiable dependency
    • librust-hyper-dev/armhf has unsatisfiable dependency
    • librust-hyper+runtime-dev/i386 has unsatisfiable dependency
    • librust-hyper+tokio-dev/i386 has unsatisfiable dependency
    • librust-hyper-dev/i386 has unsatisfiable dependency
    • librust-hyper+runtime-dev/mips64el has unsatisfiable dependency
    • librust-hyper+tokio-dev/mips64el has unsatisfiable dependency
    • librust-hyper-dev/mips64el has unsatisfiable dependency
    • librust-hyper+runtime-dev/mipsel has unsatisfiable dependency
    • librust-hyper+tokio-dev/mipsel has unsatisfiable dependency
    • librust-hyper-dev/mipsel has unsatisfiable dependency
    • librust-hyper+runtime-dev/ppc64el has unsatisfiable dependency
    • librust-hyper+tokio-dev/ppc64el has unsatisfiable dependency
    • librust-hyper-dev/ppc64el has unsatisfiable dependency
    • librust-hyper+runtime-dev/s390x has unsatisfiable dependency
    • librust-hyper+tokio-dev/s390x has unsatisfiable dependency
    • librust-hyper-dev/s390x has unsatisfiable dependency
    • Updating rust-hyper would introduce bugs in testing: #988729
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on amd64: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on arm64: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armel: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on armhf: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on i386: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mips64el: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on mipsel: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on ppc64el: librust-want-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev (>= 0.4.4-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-http-0.1+default-dev (>= 0.1.15-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-http-body-0.1+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-itoa-0.4+default-dev (>= 0.4.1-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-rustc-version-0.2+default-dev
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-tokio-0.1+rt-full-dev (>= 0.1.14-~~)
    • rust-hyper unsatisfiable Build-Depends(-Arch) on s390x: librust-want-0.2+default-dev
    • Build-Depends(-Arch): rust-hyper rust-futures-cpupool
    • Build-Depends(-Arch): rust-hyper rust-h2
    • Build-Depends(-Arch): rust-hyper rust-tokio-buf
    • Build-Depends(-Arch): rust-hyper rust-tokio-executor
    • Build-Depends(-Arch): rust-hyper rust-tokio-io
    • Build-Depends(-Arch): rust-hyper rust-tokio-reactor
    • Build-Depends(-Arch): rust-hyper rust-tokio-tcp
    • Build-Depends(-Arch): rust-hyper rust-tokio-threadpool
    • Build-Depends(-Arch): rust-hyper rust-tokio-timer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-hyper.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
    • 982 days old (needed 5 days)
• rust-hyper-tls (- to 0.3.2-2)
  • Migration status for rust-hyper-tls (- to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-hyper-tls+vendored-dev/amd64 has unsatisfiable dependency
    • librust-hyper-tls-dev/amd64 has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/arm64 has unsatisfiable dependency
    • librust-hyper-tls-dev/arm64 has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/armel has unsatisfiable dependency
    • librust-hyper-tls-dev/armel has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/armhf has unsatisfiable dependency
    • librust-hyper-tls-dev/armhf has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/i386 has unsatisfiable dependency
    • librust-hyper-tls-dev/i386 has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/mips64el has unsatisfiable dependency
    • librust-hyper-tls-dev/mips64el has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/mipsel has unsatisfiable dependency
    • librust-hyper-tls-dev/mipsel has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/ppc64el has unsatisfiable dependency
    • librust-hyper-tls-dev/ppc64el has unsatisfiable dependency
    • librust-hyper-tls+vendored-dev/s390x has unsatisfiable dependency
    • librust-hyper-tls-dev/s390x has unsatisfiable dependency
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev
    • rust-hyper-tls unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • Build-Depends(-Arch): rust-hyper-tls rust-hyper
    • Build-Depends(-Arch): rust-hyper-tls rust-tokio-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-hyper-tls.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
    • 982 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
    • 983 days old (needed 5 days)
• bst-external (- to 0.18.0-1)
  • Migration status for bst-external (- to 0.18.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bst-external would introduce bugs in testing: #941714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bst-external.html
    • 986 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-zcml.html
    • 988 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-multiauth.html
    • 991 days old (needed 5 days)
• cl-irc-logger (- to 0.9.4-3.1)
  • Migration status for cl-irc-logger (- to 0.9.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-irc-logger would introduce bugs in testing: #999079
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-irc-logger.html
    • 997 days old (needed 5 days)
• cl-lml (- to 2.5.7-4.1)
  • Migration status for cl-lml (- to 2.5.7-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-lml would introduce bugs in testing: #999045
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-lml.html
    • 997 days old (needed 5 days)
• cl-lml2 (- to 1.6.6-4.1)
  • Migration status for cl-lml2 (- to 1.6.6-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-lml2 would introduce bugs in testing: #998990
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-lml2.html
    • 997 days old (needed 5 days)
• cl-modlisp (- to 0.6-7.1)
  • Migration status for cl-modlisp (- to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-modlisp would introduce bugs in testing: #998947
    • Depends: cl-modlisp libapache2-mod-lisp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-modlisp.html
    • 997 days old (needed 5 days)
• cl-photo (- to 0.14-4.1)
  • Migration status for cl-photo (- to 0.14-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-photo would introduce bugs in testing: #999012
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-photo.html
    • 997 days old (needed 5 days)
• cl-pipes (- to 1.2.1-5.1)
  • Migration status for cl-pipes (- to 1.2.1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-pipes would introduce bugs in testing: #998994
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-pipes.html
    • 997 days old (needed 5 days)
• cl-pubmed (- to 2.1.3-5.1)
  • Migration status for cl-pubmed (- to 2.1.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-pubmed would introduce bugs in testing: #999331
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-pubmed.html
    • 997 days old (needed 5 days)
• cl-xlunit (- to 0.6.3-2.1)
  • Migration status for cl-xlunit (- to 0.6.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-xlunit would introduce bugs in testing: #998971
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-xlunit.html
    • 997 days old (needed 5 days)
• cl-xptest (- to 1.2.4-3.1)
  • Migration status for cl-xptest (- to 1.2.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-xptest would introduce bugs in testing: #998959
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-xptest.html
    • 997 days old (needed 5 days)
• qtads (- to 2.1.7-0.1)
  • Migration status for qtads (- to 2.1.7-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qtads would introduce bugs in testing: #984310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtads.html
    • 1001 days old (needed 5 days)
• python-slimmer (- to 0.1.30-8)
  • Migration status for python-slimmer (- to 0.1.30-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-slimmer would introduce bugs in testing: #997645
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-slimmer.html
    • autopkgtest for python-slimmer/0.1.30-8: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 1002 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
    • 1003 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/mipsel 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 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
    • 1003 days old (needed 5 days)
• libodb-qt (- to 2.4.0-3)
  • Migration status for libodb-qt (- to 2.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): libodb-qt libodb (not considered)
    • Depends: libodb-qt libodb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodb-qt.html
    • 1003 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:
    • Updating crypto-policies would introduce bugs in testing: #940017
    • 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
    • 1004 days old (needed 5 days)
• filler (- to 1.02-6.3)
  • Migration status for filler (- to 1.02-6.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating filler would introduce bugs in testing: #965521, #998958
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/filler.html
    • 1004 days old (needed 5 days)
• dcontainers (- to 0.8.0~alpha.16-1)
  • Migration status for dcontainers (- to 0.8.0~alpha.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dcontainers would introduce bugs in testing: #1001773
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dcontainers.html
    • 1005 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
    • 1005 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
    • 1006 days old (needed 5 days)
• charybdis (- to 4.1.2-1)
  • Migration status for charybdis (- to 4.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating charybdis would introduce bugs in testing: #978782, #981009
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/amd64
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/arm64
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/armel
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/armhf
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/i386
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/mips64el
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/mipsel
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/ppc64el
    • Impossible Depends: charybdis -> libmbedcrypto3/2.16.11-0.3/s390x
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/amd64
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/arm64
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/armel
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/armhf
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/i386
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/mips64el
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/mipsel
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/ppc64el
    • Impossible Depends: charybdis -> libmbedtls12/2.16.11-0.3/s390x
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/amd64
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/arm64
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/armel
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/armhf
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/i386
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/mips64el
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/mipsel
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/ppc64el
    • Impossible Depends: charybdis -> libmbedx509-0/2.16.11-0.3/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/charybdis.html
    • 1006 days old (needed 5 days)
• ocaml-reins (- to 0.1a-9)
  • Migration status for ocaml-reins (- to 0.1a-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libreins-ocaml-dev/amd64 has unsatisfiable dependency
    • libreins-ocaml-dev/arm64 has unsatisfiable dependency
    • libreins-ocaml-dev/armel has unsatisfiable dependency
    • libreins-ocaml-dev/armhf has unsatisfiable dependency
    • libreins-ocaml-dev/i386 has unsatisfiable dependency
    • libreins-ocaml-dev/mips64el has unsatisfiable dependency
    • libreins-ocaml-dev/mipsel has unsatisfiable dependency
    • libreins-ocaml-dev/ppc64el has unsatisfiable dependency
    • libreins-ocaml-dev/s390x has unsatisfiable dependency
    • Updating ocaml-reins would introduce bugs in testing: #971176
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/ocaml-reins.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
    • 1007 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1009 days old (needed 2 days)
• rawkit (- to 0.6.0-2)
  • Migration status for rawkit (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rawkit would introduce bugs in testing: #978079
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rawkit.html
    • 1011 days old (needed 5 days)
• ruby-omniauth-salesforce (- to 1.0.5-2)
  • Migration status for ruby-omniauth-salesforce (- to 1.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-salesforce would introduce bugs in testing: #999724
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-salesforce.html
    • autopkgtest for ruby-omniauth-salesforce/1.0.5-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1011 days old (needed 2 days)
• python-demjson (- to 2.2.4-5)
  • Migration status for python-demjson (- to 2.2.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-demjson would introduce bugs in testing: #997600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-demjson.html
    • 1018 days old (needed 5 days)
• rust-cookie-store (- to 0.8.0-1)
  • Migration status for rust-cookie-store (- to 0.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): rust-cookie-store rust-cookie (not considered)
    • Depends: rust-cookie-store rust-cookie (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cookie-store.html
    • 1018 days old (needed 5 days)
• rust-migrations-internals (- to 1.4.0-1)
  • Migration status for rust-migrations-internals (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-migrations-internals+barrel-dev/amd64 has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/arm64 has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/armel has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/armhf has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/i386 has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/mips64el has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/mipsel has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/ppc64el has unsatisfiable dependency
    • librust-migrations-internals+barrel-dev/s390x has unsatisfiable dependency
    • Updating rust-migrations-internals would introduce bugs in testing: #985262
    • Build-Depends(-Arch): rust-migrations-internals rust-diesel
    • Depends: rust-migrations-internals rust-diesel
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-migrations-internals.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
    • 1018 days old (needed 5 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: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydroffice.bag.html
    • 1019 days old (needed 5 days)
• php-doctrine-cache-bundle (- to 1.3.5+git-1)
  • Migration status for php-doctrine-cache-bundle (- to 1.3.5+git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-doctrine-cache-bundle/amd64 has unsatisfiable dependency
    • php-doctrine-cache-bundle/arm64 has unsatisfiable dependency
    • Updating php-doctrine-cache-bundle would introduce bugs in testing: #949016
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/php-doctrine-cache-bundle.html
    • autopkgtest for php-doctrine-cache-bundle/1.3.5+git-1: armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1020 days old (needed 5 days)
• libapache-mod-removeip (- to 1.0b-5.3)
  • Migration status for libapache-mod-removeip (- to 1.0b-5.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-mod-removeip would introduce bugs in testing: #998991
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-removeip.html
    • 1025 days old (needed 5 days)
• php-xml-htmlsax3 (- to 3.0.0+really3.0.0-4)
  • Migration status for php-xml-htmlsax3 (- to 3.0.0+really3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-xml-htmlsax3 would introduce bugs in testing: #1005383
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-xml-htmlsax3.html
    • 1025 days old (needed 5 days)
• dmtcp (- to 2.6.0-1)
  • Migration status for dmtcp (- to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dmtcp would introduce bugs in testing: #789292, #868928
    • dmtcp unsatisfiable Build-Depends(-Arch) on amd64: python
    • dmtcp unsatisfiable Build-Depends(-Arch) on armhf: python
    • dmtcp unsatisfiable Build-Depends(-Arch) on i386: python
    • Not built on buildd: arch amd64 binaries uploaded by yoh
    • missing build on armhf
    • missing build on i386
    • 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/d/dmtcp.html
    • 1026 days old (needed 5 days)
• hcloud-cli (- to 1.13.0-2)
  • Migration status for hcloud-cli (- to 1.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hcloud-cli would introduce bugs in testing: #1002264
    • autopkgtest for hcloud-cli/1.13.0-2: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Regression ♻ (reference ♻)
    • hcloud-cli/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/mips64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/mipsel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • hcloud-cli/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hcloud-cli.html
    • 1026 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
    • 1027 days old (needed 5 days)
• ruby-jekyll-avatar (- to 0.7.0-1)
  • Migration status for ruby-jekyll-avatar (- to 0.7.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ruby-jekyll-avatar jekyll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-avatar.html
    • autopkgtest for ruby-jekyll-avatar/0.7.0-1: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 1031 days old (needed 5 days)
• python-mailer (- to 0.8.1-4)
  • Migration status for python-mailer (- to 0.8.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-mailer would introduce bugs in testing: #997619
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mailer.html
    • autopkgtest for python-mailer/0.8.1-4: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 1032 days old (needed 5 days)
• cinfony (- to 1.2-4)
  • Migration status for cinfony (- to 1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-cinfony/amd64 has unsatisfiable dependency
    • python-cinfony/arm64 has unsatisfiable dependency
    • Updating cinfony would introduce bugs in testing: #1009281, #936303, #939065
    • autopkgtest for cinfony/1.2-4: armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python (>> 2.6.6-3~)
    • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-indigo
    • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-jpype
    • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-openbabel
    • cinfony unsatisfiable Build-Depends(-Arch) on amd64: python-rdkit
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cinfony.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1034 days old (needed 5 days)
• redmine-plugin-pretend (- to 0.0.2+git20130821-5)
  • Migration status for redmine-plugin-pretend (- to 0.0.2+git20130821-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine-plugin-pretend.html
  • Additional info:
    • 1036 days old (needed 5 days)
• rust-kamadak-exif (- to 0.3.1-2)
  • Migration status for rust-kamadak-exif (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-kamadak-exif would introduce bugs in testing: #985309
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-kamadak-exif.html
    • 1039 days old (needed 5 days)
• rust-libsqlite3-sys (- to 0.15.0-2)
  • Migration status for rust-libsqlite3-sys (- to 0.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-libsqlite3-sys+bindgen-dev/amd64 has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/amd64 has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/arm64 has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/arm64 has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/armel has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/armel has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/armhf has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/armhf has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/i386 has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/i386 has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/mips64el has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/mips64el has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/mipsel has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/mipsel has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/ppc64el has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/ppc64el has unsatisfiable dependency
    • librust-libsqlite3-sys+bindgen-dev/s390x has unsatisfiable dependency
    • librust-libsqlite3-sys+buildtime-bindgen-dev/s390x has unsatisfiable dependency
    • Updating rust-libsqlite3-sys would introduce bugs in testing: #984921
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-libsqlite3-sys.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
    • 1039 days old (needed 5 days)
• rust-tokio-buf (- to 0.1.1-2)
  • Migration status for rust-tokio-buf (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-buf+util-dev/amd64 has unsatisfiable dependency
    • librust-tokio-buf-dev/amd64 has unsatisfiable dependency
    • librust-tokio-buf+util-dev/arm64 has unsatisfiable dependency
    • librust-tokio-buf-dev/arm64 has unsatisfiable dependency
    • librust-tokio-buf+util-dev/armel has unsatisfiable dependency
    • librust-tokio-buf-dev/armel has unsatisfiable dependency
    • librust-tokio-buf+util-dev/armhf has unsatisfiable dependency
    • librust-tokio-buf-dev/armhf has unsatisfiable dependency
    • librust-tokio-buf+util-dev/i386 has unsatisfiable dependency
    • librust-tokio-buf-dev/i386 has unsatisfiable dependency
    • librust-tokio-buf+util-dev/mips64el has unsatisfiable dependency
    • librust-tokio-buf-dev/mips64el has unsatisfiable dependency
    • librust-tokio-buf+util-dev/mipsel has unsatisfiable dependency
    • librust-tokio-buf-dev/mipsel has unsatisfiable dependency
    • librust-tokio-buf+util-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-buf-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-buf+util-dev/s390x has unsatisfiable dependency
    • librust-tokio-buf-dev/s390x has unsatisfiable dependency
    • Updating rust-tokio-buf would introduce bugs in testing: #998552
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+either-dev (>= 0.4.10-~~)
    • rust-tokio-buf unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.23-~~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-buf.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
    • 1039 days old (needed 5 days)
• sandsifter (- to 1.04-1)
  • Migration status for sandsifter (- to 1.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sandsifter/amd64 has unsatisfiable dependency
    • sandsifter/i386 has unsatisfiable dependency
    • Updating sandsifter would introduce bugs in testing: #938432
    • sandsifter unsatisfiable Build-Depends(-Arch) on amd64: python (>= 2.7)
    • sandsifter unsatisfiable Build-Depends(-Arch) on i386: python (>= 2.7)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sandsifter.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • 1041 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: #997441
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squirrel3.html
    • 1045 days old (needed 5 days)
• dolphin-emu (- to 5.0+dfsg-6)
  • Migration status for dolphin-emu (- to 5.0+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dolphin-emu would introduce bugs in testing: #976530
    • Impossible Depends: dolphin-emu -> libmbedcrypto3/2.16.11-0.3/amd64
    • Impossible Depends: dolphin-emu -> libmbedcrypto3/2.16.11-0.3/arm64
    • Impossible Depends: dolphin-emu -> libmbedtls12/2.16.11-0.3/amd64
    • Impossible Depends: dolphin-emu -> libmbedtls12/2.16.11-0.3/arm64
    • Impossible Depends: dolphin-emu -> libmbedx509-0/2.16.11-0.3/amd64
    • Impossible Depends: dolphin-emu -> libmbedx509-0/2.16.11-0.3/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolphin-emu.html
    • 1046 days old (needed 5 days)
• django-pipeline (- to 1.6.14-3)
  • Migration status for django-pipeline (- to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-pipeline would introduce bugs in testing: #997302
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-pipeline.html
    • 1050 days old (needed 5 days)
• haskell-classy-prelude-yesod (- to 1.5.0-1)
  • Migration status for haskell-classy-prelude-yesod (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-classy-prelude-yesod would introduce bugs in testing: #912924
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-classy-prelude-yesod.html
    • 1050 days old (needed 5 days)
• librevisa (- to 0.0.20130812-2.2)
  • Migration status for librevisa (- to 0.0.20130812-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): librevisa vxi (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librevisa.html
    • 1052 days old (needed 5 days)
• mailavenger (- to 0.8.5-2)
  • Migration status for mailavenger (- to 0.8.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailavenger would introduce bugs in testing: #944658, #944693, #957514
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for mailavenger/0.8.5-2: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailavenger.html
    • 1056 days old (needed 5 days)
• rust-tokio-core (- to 0.1.17-2)
  • Migration status for rust-tokio-core (- to 0.1.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-core-dev/amd64 has unsatisfiable dependency
    • librust-tokio-core-dev/arm64 has unsatisfiable dependency
    • librust-tokio-core-dev/armel has unsatisfiable dependency
    • librust-tokio-core-dev/armhf has unsatisfiable dependency
    • librust-tokio-core-dev/i386 has unsatisfiable dependency
    • librust-tokio-core-dev/mips64el has unsatisfiable dependency
    • librust-tokio-core-dev/mipsel has unsatisfiable dependency
    • librust-tokio-core-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-core-dev/s390x has unsatisfiable dependency
    • Updating rust-tokio-core would introduce bugs in testing: #952137
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on amd64: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on amd64: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on arm64: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on arm64: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armel: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armel: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armhf: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on armhf: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on i386: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on i386: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mips64el: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mips64el: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mipsel: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on mipsel: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on ppc64el: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on s390x: librust-scoped-tls-0.1+default-dev
    • rust-tokio-core unsatisfiable Build-Depends(-Arch) on s390x: librust-tokio-0.1+default-dev (>= 0.1.5-~~)
    • Build-Depends(-Arch): rust-tokio-core rust-tokio-executor
    • Build-Depends(-Arch): rust-tokio-core rust-tokio-io
    • Build-Depends(-Arch): rust-tokio-core rust-tokio-reactor
    • Build-Depends(-Arch): rust-tokio-core rust-tokio-timer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-core.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
    • 1060 days old (needed 5 days)
• rust-tokio-current-thread (- to 0.1.6-1)
  • Migration status for rust-tokio-current-thread (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-current-thread-dev/amd64 has unsatisfiable dependency
    • librust-tokio-current-thread-dev/arm64 has unsatisfiable dependency
    • librust-tokio-current-thread-dev/armel has unsatisfiable dependency
    • librust-tokio-current-thread-dev/armhf has unsatisfiable dependency
    • librust-tokio-current-thread-dev/i386 has unsatisfiable dependency
    • librust-tokio-current-thread-dev/mips64el has unsatisfiable dependency
    • librust-tokio-current-thread-dev/mipsel has unsatisfiable dependency
    • librust-tokio-current-thread-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-current-thread-dev/s390x has unsatisfiable dependency
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-current-thread unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • Build-Depends(-Arch): rust-tokio-current-thread rust-tokio-executor
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-current-thread.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
    • 1061 days old (needed 5 days)
• rust-tokio-udp (- to 0.1.3-2)
  • Migration status for rust-tokio-udp (- to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-udp-dev/amd64 has unsatisfiable dependency
    • librust-tokio-udp-dev/arm64 has unsatisfiable dependency
    • librust-tokio-udp-dev/armel has unsatisfiable dependency
    • librust-tokio-udp-dev/armhf has unsatisfiable dependency
    • librust-tokio-udp-dev/i386 has unsatisfiable dependency
    • librust-tokio-udp-dev/mips64el has unsatisfiable dependency
    • librust-tokio-udp-dev/mipsel has unsatisfiable dependency
    • librust-tokio-udp-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-udp-dev/s390x has unsatisfiable dependency
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev
    • rust-tokio-udp unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.19-~~)
    • Build-Depends(-Arch): rust-tokio-udp rust-tokio-codec
    • Build-Depends(-Arch): rust-tokio-udp rust-tokio-io
    • Build-Depends(-Arch): rust-tokio-udp rust-tokio-reactor
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-udp.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
    • 1061 days old (needed 5 days)
• rust-tokio-uds (- to 0.2.5-1)
  • Migration status for rust-tokio-uds (- to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-uds-dev/amd64 has unsatisfiable dependency
    • librust-tokio-uds-dev/arm64 has unsatisfiable dependency
    • librust-tokio-uds-dev/armel has unsatisfiable dependency
    • librust-tokio-uds-dev/armhf has unsatisfiable dependency
    • librust-tokio-uds-dev/i386 has unsatisfiable dependency
    • librust-tokio-uds-dev/mips64el has unsatisfiable dependency
    • librust-tokio-uds-dev/mipsel has unsatisfiable dependency
    • librust-tokio-uds-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-uds-dev/s390x has unsatisfiable dependency
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev (>= 0.4.8-~~)
    • rust-tokio-uds unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • Build-Depends(-Arch): rust-tokio-uds rust-tokio-codec
    • Build-Depends(-Arch): rust-tokio-uds rust-tokio-io
    • Build-Depends(-Arch): rust-tokio-uds rust-tokio-reactor
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-uds.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
    • 1061 days old (needed 5 days)
• rust-tokio-fs (- to 0.1.6-1)
  • Migration status for rust-tokio-fs (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-fs-dev/amd64 has unsatisfiable dependency
    • librust-tokio-fs-dev/arm64 has unsatisfiable dependency
    • librust-tokio-fs-dev/armel has unsatisfiable dependency
    • librust-tokio-fs-dev/armhf has unsatisfiable dependency
    • librust-tokio-fs-dev/i386 has unsatisfiable dependency
    • librust-tokio-fs-dev/mips64el has unsatisfiable dependency
    • librust-tokio-fs-dev/mipsel has unsatisfiable dependency
    • librust-tokio-fs-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-fs-dev/s390x has unsatisfiable dependency
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • rust-tokio-fs unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.21-~~)
    • Build-Depends(-Arch): rust-tokio-fs rust-tokio-io
    • Build-Depends(-Arch): rust-tokio-fs rust-tokio-threadpool
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-fs.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
    • 1066 days old (needed 5 days)
• rust-bufstream (- to 0.1.4-1)
  • Migration status for rust-bufstream (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-bufstream+futures-dev/amd64 has unsatisfiable dependency
    • librust-bufstream+tokio-dev/amd64 has unsatisfiable dependency
    • librust-bufstream+futures-dev/arm64 has unsatisfiable dependency
    • librust-bufstream+tokio-dev/arm64 has unsatisfiable dependency
    • librust-bufstream+futures-dev/armel has unsatisfiable dependency
    • librust-bufstream+tokio-dev/armel has unsatisfiable dependency
    • librust-bufstream+futures-dev/armhf has unsatisfiable dependency
    • librust-bufstream+tokio-dev/armhf has unsatisfiable dependency
    • librust-bufstream+futures-dev/i386 has unsatisfiable dependency
    • librust-bufstream+tokio-dev/i386 has unsatisfiable dependency
    • librust-bufstream+futures-dev/mips64el has unsatisfiable dependency
    • librust-bufstream+tokio-dev/mips64el has unsatisfiable dependency
    • librust-bufstream+futures-dev/mipsel has unsatisfiable dependency
    • librust-bufstream+tokio-dev/mipsel has unsatisfiable dependency
    • librust-bufstream+futures-dev/ppc64el has unsatisfiable dependency
    • librust-bufstream+tokio-dev/ppc64el has unsatisfiable dependency
    • librust-bufstream+futures-dev/s390x has unsatisfiable dependency
    • librust-bufstream+tokio-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-bufstream.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
    • 1067 days old (needed 5 days)
• ytree (- to 1.99pl1-2)
  • Migration status for ytree (- to 1.99pl1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ytree would introduce bugs in testing: #995480
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ytree.html
    • autopkgtest for ytree/1.99pl1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1069 days old (needed 2 days)
• packagesearch (- to 2.7.11)
  • Migration status for packagesearch (- to 2.7.11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): packagesearch libwibble (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): packagesearch tagcoll2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packagesearch.html
    • 1072 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/mipsel 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
    • missing build on mipsel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluginhook.html
    • 1079 days old (needed 5 days)
• sl-modem (- to 2.9.11~20110321-16)
  • Migration status for sl-modem (- to 2.9.11~20110321-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sl-modem would introduce bugs in testing: #982685, #983650
    • sl-modem unsatisfiable Build-Depends(-Arch) on amd64: execstack
    • sl-modem unsatisfiable Build-Depends(-Arch) on i386: execstack
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1081 days old (needed 5 days)
• gcc-m68hc1x (- to 1:3.3.6+3.1+dfsg-3.1)
  • Migration status for gcc-m68hc1x (- to 1:3.3.6+3.1+dfsg-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-m68hc1x would introduce bugs in testing: #965542, #982703, #999057
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-m68hc1x.html
    • 1103 days old (needed 5 days)
• jruby (- to 9.1.17.0-3)
  • Migration status for jruby (- to 9.1.17.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jruby would introduce bugs in testing: #959600, #972230, #976477, #977979
    • Build-Depends(-Arch): jruby jruby-openssl
    • Build-Depends(-Arch): jruby ruby-psych
    • Depends: jruby ruby-psych
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jruby.html
    • 1109 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
    • 1115 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
    • 1116 days old (needed 5 days)
• ruby-omniauth-ldap (- to 2.1.1-1)
  • Migration status for ruby-omniauth-ldap (- to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-ldap would introduce bugs in testing: #999718
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-ldap.html
    • autopkgtest for ruby-omniauth-ldap/2.1.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1123 days old (needed 2 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
    • 1124 days old (needed 5 days)
• libodb-mysql (- to 2.4.0-5)
  • Migration status for libodb-mysql (- to 2.4.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libodb-mysql libodb (not considered)
    • Depends: libodb-mysql libodb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodb-mysql.html
    • 1127 days old (needed 5 days)
• nzbget (- to 21.0+dfsg-2)
  • Migration status for nzbget (- to 21.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nzbget would introduce bugs in testing: #1005717, #1007134
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nzbget.html
    • autopkgtest for nzbget/21.0+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1130 days old (needed 2 days)
• live-wrapper (- to 0.10)
  • Migration status for live-wrapper (- to 0.10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • live-wrapper/amd64 has unsatisfiable dependency
    • live-wrapper/arm64 has unsatisfiable dependency
    • Updating live-wrapper would introduce bugs in testing: #916716, #936954
    • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: python-apt
    • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: python-cliapp
    • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: python-requests
    • live-wrapper unsatisfiable Build-Depends(-Arch) on amd64: vmdebootstrap (>= 1.7-1+nmu1)
    • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, 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/l/live-wrapper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1137 days old (needed 5 days)
• gnu-smalltalk (- to 3.2.5-1.3)
  • Migration status for gnu-smalltalk (- to 3.2.5-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnu-smalltalk would introduce bugs in testing: #1002312
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnu-smalltalk.html
    • 1139 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, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1151 days old (needed 2 days)
• phamm (- to 0.6.8-1)
  • Migration status for phamm (- to 0.6.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phamm would introduce bugs in testing: #924731, #965772, #999208
    • Not built on buildd: arch all binaries uploaded by kobold, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phamm.html
    • 1171 days old (needed 5 days)
• human-icon-theme (- to 0.28.debian-6.1)
  • Migration status for human-icon-theme (- to 0.28.debian-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating human-icon-theme would introduce bugs in testing: #1002886
    • Depends: human-icon-theme tangerine-icon-theme
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1174 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
    • 1174 days old (needed 5 days)
• mono-basic (- to 4.0.1-3)
  • Migration status for mono-basic (- to 4.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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/m/mono-basic.html
    • 1193 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfr.html
    • autopkgtest for pyfr/1.5.0-3: amd64: Not a regression, arm64: Not a regression, armhf: Not a regression, i386: Not a regression, ppc64el: Not a regression, s390x: Not a regression
    • 1193 days old (needed 5 days)
• ruby-omniauth-azure-oauth2 (- to 0.0.10-1)
  • Migration status for ruby-omniauth-azure-oauth2 (- to 0.0.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-azure-oauth2 would introduce bugs in testing: #999712
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-azure-oauth2.html
    • autopkgtest for ruby-omniauth-azure-oauth2/0.0.10-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1194 days old (needed 2 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
    • 1200 days old (needed 5 days)
• validns (- to 0.8+git20160720-3.1)
  • Migration status for validns (- to 0.8+git20160720-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating validns would introduce bugs in testing: #1006583
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/validns.html
    • 1203 days old (needed 5 days)
• libappimage (- to 0.1.9+dfsg-1)
  • Migration status for libappimage (- to 0.1.9+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libappimage would introduce bugs in testing: #977192
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libappimage.html
    • autopkgtest for libappimage/0.1.9+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1209 days old (needed 2 days)
• cernlib (- to 20061220+dfsg3-4.4)
  • Migration status for cernlib (- to 20061220+dfsg3-4.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cernlib/amd64 has unsatisfiable dependency
    • cernlib/arm64 has unsatisfiable dependency
    • Updating cernlib would introduce bugs in testing: #957080, #965451
    • Depends: cernlib paw
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cernlib.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1211 days old (needed 5 days)
• mongo-tools (- to 3.4.14-4)
  • Migration status for mongo-tools (- to 3.4.14-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mongo-tools would introduce bugs in testing: #935286, #988021
    • mongo-tools/amd64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/arm64 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/armel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/armhf has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/i386 has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/mipsel has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/ppc64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • mongo-tools/s390x has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • Not built on buildd: arch amd64 binaries uploaded by apoikos@dmesg.gr
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-tools.html
    • 1215 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
    • 1216 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/diaspora.html
    • autopkgtest for diaspora/0.7.9.0+dfsg-4: armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by praveen, 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
    • 1218 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-trust-webcrypto.html
    • autopkgtest for node-trust-webcrypto/0.9.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1220 days old (needed 2 days)
• rust-tokio-async-await (- to 0.1.5-1)
  • Migration status for rust-tokio-async-await (- to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-async-await+async-await-preview-dev/amd64 has unsatisfiable dependency
    • librust-tokio-async-await-dev/amd64 has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/arm64 has unsatisfiable dependency
    • librust-tokio-async-await-dev/arm64 has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/armel has unsatisfiable dependency
    • librust-tokio-async-await-dev/armel has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/armhf has unsatisfiable dependency
    • librust-tokio-async-await-dev/armhf has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/i386 has unsatisfiable dependency
    • librust-tokio-async-await-dev/i386 has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/mips64el has unsatisfiable dependency
    • librust-tokio-async-await-dev/mips64el has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/mipsel has unsatisfiable dependency
    • librust-tokio-async-await-dev/mipsel has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-async-await-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-async-await+async-await-preview-dev/s390x has unsatisfiable dependency
    • librust-tokio-async-await-dev/s390x has unsatisfiable dependency
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • rust-tokio-async-await unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.23-~~)
    • Build-Depends(-Arch): rust-tokio-async-await rust-tokio-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-async-await.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
    • 1221 days old (needed 5 days)
• spellutils (- to 0.7-8)
  • Migration status for spellutils (- to 0.7-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spellutils would introduce bugs in testing: #978344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spellutils.html
    • 1222 days old (needed 5 days)
• simpleitk (- to 1.0.1-3)
  • Migration status for simpleitk (- to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsimpleitk1.0/amd64 has unsatisfiable dependency
    • python3-simpleitk/amd64 has unsatisfiable dependency
    • libsimpleitk1.0/i386 has unsatisfiable dependency
    • python3-simpleitk/i386 has unsatisfiable dependency
    • Updating simpleitk would introduce bugs in testing: #949355
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/simpleitk.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • 1228 days old (needed 5 days)
• emms (- to 5.1-1)
  • Migration status for emms (- to 5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emms would introduce bugs in testing: #997217
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emms.html
    • 1235 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/mipsel has unsatisfiable dependency
    • asterisk-espeak/ppc64el has unsatisfiable dependency
    • asterisk-espeak/s390x has unsatisfiable dependency
    • Updating asterisk-espeak would introduce bugs in testing: #947510
  • 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 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
    • 1237 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
    • 1239 days old (needed 5 days)
• ninix-aya (- to 5.0.9-1)
  • Migration status for ninix-aya (- to 5.0.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ninix-aya ruby-gnome (not considered)
    • Depends: ninix-aya ruby-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ninix-aya.html
    • 1239 days old (needed 5 days)
• fsl (- to 5.0.8-6)
  • Migration status for fsl (- to 5.0.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • fsl-5.0-core/amd64 has unsatisfiable dependency
    • fsl-5.0-core/arm64 has unsatisfiable dependency
    • fsl-5.0-core/armel has unsatisfiable dependency
    • fsl-5.0-core/armhf has unsatisfiable dependency
    • fsl-5.0-core/i386 has unsatisfiable dependency
    • fsl-5.0-core/mips64el has unsatisfiable dependency
    • fsl-5.0-core/mipsel has unsatisfiable dependency
    • fsl-5.0-core/ppc64el has unsatisfiable dependency
    • fsl-5.0-core/s390x has unsatisfiable dependency
    • Updating fsl would introduce bugs in testing: #936564, #966112
  • 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 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
    • 1242 days old (needed 5 days)
• gnome-phone-manager (- to 0.69-2.1)
  • Migration status for gnome-phone-manager (- to 0.69-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-phone-manager would introduce bugs in testing: #965563
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-phone-manager.html
    • 1243 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
    • 1244 days old (needed 5 days)
• tiptop (- to 2.3.1-4)
  • Migration status for tiptop (- to 2.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tiptop would introduce bugs in testing: #997182
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiptop.html
    • 1246 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
    • Build-Depends(-Arch): vibe.d diet-ng
    • Depends: vibe.d diet-ng
  • 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
    • 1246 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: #983648, #991003
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/k/kpatch.html
  • Additional info:
    • 1250 days old (needed 5 days)
• rust-nom-3 (- to 3.2.1-2)
  • Migration status for rust-nom-3 (- to 3.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-nom-3+compiler-error-dev/amd64 has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/amd64 has unsatisfiable dependency
    • librust-nom-3+nightly-dev/amd64 has unsatisfiable dependency
    • librust-nom-3+regex-dev/amd64 has unsatisfiable dependency
    • librust-nom-3+regexp-dev/amd64 has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/amd64 has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/arm64 has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/arm64 has unsatisfiable dependency
    • librust-nom-3+nightly-dev/arm64 has unsatisfiable dependency
    • librust-nom-3+regex-dev/arm64 has unsatisfiable dependency
    • librust-nom-3+regexp-dev/arm64 has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/arm64 has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/armel has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/armel has unsatisfiable dependency
    • librust-nom-3+nightly-dev/armel has unsatisfiable dependency
    • librust-nom-3+regex-dev/armel has unsatisfiable dependency
    • librust-nom-3+regexp-dev/armel has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/armel has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/armhf has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/armhf has unsatisfiable dependency
    • librust-nom-3+nightly-dev/armhf has unsatisfiable dependency
    • librust-nom-3+regex-dev/armhf has unsatisfiable dependency
    • librust-nom-3+regexp-dev/armhf has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/armhf has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/i386 has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/i386 has unsatisfiable dependency
    • librust-nom-3+nightly-dev/i386 has unsatisfiable dependency
    • librust-nom-3+regex-dev/i386 has unsatisfiable dependency
    • librust-nom-3+regexp-dev/i386 has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/i386 has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/mips64el has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/mips64el has unsatisfiable dependency
    • librust-nom-3+nightly-dev/mips64el has unsatisfiable dependency
    • librust-nom-3+regex-dev/mips64el has unsatisfiable dependency
    • librust-nom-3+regexp-dev/mips64el has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/mips64el has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/mipsel has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/mipsel has unsatisfiable dependency
    • librust-nom-3+nightly-dev/mipsel has unsatisfiable dependency
    • librust-nom-3+regex-dev/mipsel has unsatisfiable dependency
    • librust-nom-3+regexp-dev/mipsel has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/mipsel has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/ppc64el has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/ppc64el has unsatisfiable dependency
    • librust-nom-3+nightly-dev/ppc64el has unsatisfiable dependency
    • librust-nom-3+regex-dev/ppc64el has unsatisfiable dependency
    • librust-nom-3+regexp-dev/ppc64el has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/ppc64el has unsatisfiable dependency
    • librust-nom-3+compiler-error-dev/s390x has unsatisfiable dependency
    • librust-nom-3+lazy-static-dev/s390x has unsatisfiable dependency
    • librust-nom-3+nightly-dev/s390x has unsatisfiable dependency
    • librust-nom-3+regex-dev/s390x has unsatisfiable dependency
    • librust-nom-3+regexp-dev/s390x has unsatisfiable dependency
    • librust-nom-3+regexp-macros-dev/s390x has unsatisfiable dependency
    • Updating rust-nom-3 would introduce bugs in testing: #984771
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-nom-3.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
    • 1252 days old (needed 5 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
    • 1256 days old (needed 5 days)
• tangerine-icon-theme (- to 0.26.debian-5)
  • Migration status for tangerine-icon-theme (- to 0.26.debian-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tangerine-icon-theme would introduce bugs in testing: #1002885
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1260 days old (needed 5 days)
• vzctl (- to 4.9.4-6)
  • Migration status for vzctl (- to 4.9.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vzctl would introduce bugs in testing: #970916
    • Build-Depends(-Arch): vzctl ploop
    • Depends: vzctl vzquota
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vzctl.html
    • 1261 days old (needed 5 days)
• anjuta-extras (- to 3.26.0-5)
  • Migration status for anjuta-extras (- to 3.26.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating anjuta-extras would introduce bugs in testing: #997116
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anjuta-extras.html
    • 1265 days old (needed 5 days)
• rust-cargo-lichking (- to 0.7.0-1)
  • Migration status for rust-cargo-lichking (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cargo-lichking/amd64 has unsatisfiable dependency
    • cargo-lichking/arm64 has unsatisfiable dependency
    • cargo-lichking/armel has unsatisfiable dependency
    • cargo-lichking/armhf has unsatisfiable dependency
    • cargo-lichking/i386 has unsatisfiable dependency
    • cargo-lichking/mips64el has unsatisfiable dependency
    • cargo-lichking/mipsel has unsatisfiable dependency
    • cargo-lichking/ppc64el has unsatisfiable dependency
    • cargo-lichking/s390x has unsatisfiable dependency
    • Updating rust-cargo-lichking would introduce bugs in testing: #943306
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on amd64: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on arm64: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on armel: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on armhf: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on i386: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on mips64el: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on mipsel: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cargo-0.32+default-dev
    • rust-cargo-lichking unsatisfiable Build-Depends(-Arch) on s390x: librust-cargo-0.32+default-dev
    • Not built on buildd: arch amd64 binaries uploaded by kraai
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cargo-lichking.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
    • 1266 days old (needed 5 days)
• gtkhash (- to 1.2-1)
  • Migration status for gtkhash (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkhash would introduce bugs in testing: #978830
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkhash.html
    • 1267 days old (needed 5 days)
• freeture (- to 1.3.0-1)
  • Migration status for freeture (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freeture/amd64 has unsatisfiable dependency
    • freeture/arm64 has unsatisfiable dependency
    • freeture/armel has unsatisfiable dependency
    • freeture/armhf has unsatisfiable dependency
    • freeture/i386 has unsatisfiable dependency
    • freeture/mips64el has unsatisfiable dependency
    • freeture/mipsel has unsatisfiable dependency
    • freeture/ppc64el has unsatisfiable dependency
    • freeture/s390x has unsatisfiable dependency
    • Updating freeture would introduce bugs in testing: #922579
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/freeture.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
    • 1271 days old (needed 5 days)
• dsh (- to 0.25.10-1.4)
  • Migration status for dsh (- to 0.25.10-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dsh would introduce bugs in testing: #999207
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dsh.html
    • 1272 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 armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1272 days old (needed 5 days)
• vland (- to 0.8-1)
  • Migration status for vland (- to 0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vland/amd64 has unsatisfiable dependency
    • vland/arm64 has unsatisfiable dependency
    • Updating vland would introduce bugs in testing: #938790
    • Not built on buildd: arch all binaries uploaded by 93sam, 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/v/vland.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1276 days old (needed 5 days)
• python-thinc (- to 6.12.1-1)
  • Migration status for python-thinc (- to 6.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-thinc/amd64 has unsatisfiable dependency
    • python3-thinc/arm64 has unsatisfiable dependency
    • python3-thinc/armel has unsatisfiable dependency
    • python3-thinc/armhf has unsatisfiable dependency
    • python3-thinc/i386 has unsatisfiable dependency
    • python3-thinc/mips64el has unsatisfiable dependency
    • python3-thinc/mipsel has unsatisfiable dependency
    • python3-thinc/ppc64el has unsatisfiable dependency
    • python3-thinc/s390x has unsatisfiable dependency
    • Updating python-thinc would introduce bugs in testing: #947111
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-thinc.html
  • Additional info:
    • 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
    • 1283 days old (needed 5 days)
• rust-nodrop (- to 0.1.13-1)
  • Migration status for rust-nodrop (- to 0.1.13-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-nodrop rust-nodrop-union (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nodrop.html
    • 1286 days old (needed 5 days)
• apsfilter (- to 7.2.6-2)
  • Migration status for apsfilter (- to 7.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apsfilter would introduce bugs in testing: #965410, #999010
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apsfilter.html
    • 1287 days old (needed 5 days)
• golang-codegangsta-cli (- to 1.18.0-3)
  • Migration status for golang-codegangsta-cli (- to 1.18.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-codegangsta-cli would introduce bugs in testing: #1008411
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-codegangsta-cli.html
    • 1287 days old (needed 5 days)
• uima-as (- to 2.3.1-9)
  • Migration status for uima-as (- to 2.3.1-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): uima-as activemq (not considered)
    • Depends: uima-as activemq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uima-as.html
    • 1289 days old (needed 5 days)
• kmplayer (- to 1:0.12.0b-3)
  • Migration status for kmplayer (- to 1:0.12.0b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kmplayer would introduce bugs in testing: #997118
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmplayer.html
    • 1293 days old (needed 5 days)
• rust-servo-arc (- to 0.1.1-1)
  • Migration status for rust-servo-arc (- to 0.1.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-servo-arc rust-nodrop (not considered)
    • Depends: rust-servo-arc rust-nodrop (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-servo-arc.html
    • 1293 days old (needed 5 days)
• tangerine (- to 0.3.4-6.1)
  • Migration status for tangerine (- to 0.3.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): tangerine log4net (not considered)
    • Depends: tangerine log4net (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tangerine.html
    • 1300 days old (needed 5 days)
• django-test-without-migrations (- to 0.6-5)
  • Migration status for django-test-without-migrations (- to 0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-test-without-migrations would introduce bugs in testing: #915041
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-test-without-migrations.html
    • autopkgtest for django-test-without-migrations/0.6-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1306 days old (needed 2 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: #914801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/evqueue-core.html
  • Additional info:
    • 1306 days old (needed 5 days)
• icu-le-hb (- to 1.0.3+git180724-3)
  • Migration status for icu-le-hb (- to 1.0.3+git180724-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/amd64
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/arm64
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/armel
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/armhf
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/i386
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/mips64el
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/mipsel
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/ppc64el
    • Impossible Depends: icu-le-hb -> libicu67/67.1-7/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icu-le-hb.html
    • 1306 days old (needed 5 days)
• faumachine (- to 20180503-4)
  • Migration status for faumachine (- to 20180503-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating faumachine would introduce bugs in testing: #925676
    • faumachine unsatisfiable Build-Depends(-Arch) on amd64: python
    • Not built on buildd: arch amd64 binaries uploaded by fuddl
    • Not built on buildd: arch all binaries uploaded by fuddl, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/faumachine.html
    • 1308 days old (needed 5 days)
• squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3)
  • Migration status for squeak-plugins-scratch (- to 1.4.0.2~svn.r83-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squeak-plugins-scratch would introduce bugs in testing: #909352
    • Not built on buildd: arch amd64 binaries uploaded by miriam
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeak-plugins-scratch.html
    • 1310 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
    • 1311 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
    • 1313 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
    • 1314 days old (needed 5 days)
• rust-tokio-codec (- to 0.1.1-1)
  • Migration status for rust-tokio-codec (- to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tokio-codec-dev/amd64 has unsatisfiable dependency
    • librust-tokio-codec-dev/arm64 has unsatisfiable dependency
    • librust-tokio-codec-dev/armel has unsatisfiable dependency
    • librust-tokio-codec-dev/armhf has unsatisfiable dependency
    • librust-tokio-codec-dev/i386 has unsatisfiable dependency
    • librust-tokio-codec-dev/mips64el has unsatisfiable dependency
    • librust-tokio-codec-dev/mipsel has unsatisfiable dependency
    • librust-tokio-codec-dev/ppc64el has unsatisfiable dependency
    • librust-tokio-codec-dev/s390x has unsatisfiable dependency
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on amd64: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on amd64: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on arm64: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on arm64: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on armel: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on armel: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on armhf: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on armhf: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on i386: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on i386: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on mips64el: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on mips64el: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on mipsel: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on mipsel: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on ppc64el: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on ppc64el: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on s390x: librust-bytes-0.4+default-dev (>= 0.4.7~~)
    • rust-tokio-codec unsatisfiable Build-Depends(-Arch) on s390x: librust-futures-0.1+default-dev (>= 0.1.18~~)
    • Build-Depends(-Arch): rust-tokio-codec rust-tokio-io
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tokio-codec.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
    • 1318 days old (needed 5 days)
• gauche-gtk (- to 0.6+git20160927-3)
  • Migration status for gauche-gtk (- to 0.6+git20160927-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gauche-gtk/amd64 has unsatisfiable dependency
    • gauche-gtk/arm64 has unsatisfiable dependency
    • gauche-gtk/armel has unsatisfiable dependency
    • gauche-gtk/armhf has unsatisfiable dependency
    • gauche-gtk/i386 has unsatisfiable dependency
    • gauche-gtk/mips64el has unsatisfiable dependency
    • gauche-gtk/mipsel has unsatisfiable dependency
    • gauche-gtk/ppc64el has unsatisfiable dependency
    • gauche-gtk/s390x has unsatisfiable dependency
    • Updating gauche-gtk would introduce bugs in testing: #981928
    • Build-Depends(-Arch): gauche-gtk gauche
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gauche-gtk.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
    • 1327 days old (needed 5 days)
• florence (- to 0.6.3-1.2)
  • Migration status for florence (- to 0.6.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating florence would introduce bugs in testing: #947521
    • florence unsatisfiable Build-Depends(-Arch) on amd64: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on arm64: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on armel: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on armhf: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on i386: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on mips64el: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on mipsel: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on ppc64el: gnome-doc-utils
    • florence unsatisfiable Build-Depends(-Arch) on s390x: gnome-doc-utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/florence.html
    • 1328 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
    • 1328 days old (needed 5 days)
• ruby-omniauth-shibboleth (- to 1.3.0-1)
  • Migration status for ruby-omniauth-shibboleth (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-shibboleth would introduce bugs in testing: #999726
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-shibboleth.html
    • autopkgtest for ruby-omniauth-shibboleth/1.3.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1328 days old (needed 2 days)
• k3d (- to 0.8.0.6-8)
  • Migration status for k3d (- to 0.8.0.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • k3d/amd64 has unsatisfiable dependency
    • k3d/arm64 has unsatisfiable dependency
    • k3d/armel has unsatisfiable dependency
    • k3d/armhf has unsatisfiable dependency
    • k3d/i386 has unsatisfiable dependency
    • k3d/mips64el has unsatisfiable dependency
    • k3d/mipsel has unsatisfiable dependency
    • k3d/ppc64el has unsatisfiable dependency
    • k3d/s390x has unsatisfiable dependency
    • Updating k3d would introduce bugs in testing: #936777, #946228, #948127
    • k3d unsatisfiable Build-Depends(-Arch) on amd64: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on arm64: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on armel: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on armhf: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on i386: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on mips64el: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on mipsel: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on ppc64el: python-dev
    • k3d unsatisfiable Build-Depends(-Arch) on s390x: python-dev
    • Not built on buildd: arch all binaries uploaded by manuel.montezelo@gmail.com, 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/k/k3d.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
    • 1330 days old (needed 5 days)
• grokmirror (- to 1.0.0-1.1)
  • Migration status for grokmirror (- to 1.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grokmirror/amd64 has unsatisfiable dependency
    • grokmirror/arm64 has unsatisfiable dependency
    • Updating grokmirror would introduce bugs in testing: #936665
    • grokmirror unsatisfiable Build-Depends(-Arch) on amd64: python
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/grokmirror.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1338 days old (needed 5 days)
• rust-nodrop-union (- to 0.1.9-1)
  • Migration status for rust-nodrop-union (- to 0.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-nodrop-union would introduce bugs in testing: #952159
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nodrop-union.html
    • 1339 days old (needed 5 days)
• kannel-sqlbox (- to 0.7.2-5)
  • Migration status for kannel-sqlbox (- to 0.7.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kannel-sqlbox would introduce bugs in testing: #957397, #972128
    • Depends: kannel-sqlbox sqlite
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kannel-sqlbox.html
    • 1342 days old (needed 5 days)
• sqsh (- to 2.5.16.1-2)
  • Migration status for sqsh (- to 2.5.16.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqsh would introduce bugs in testing: #971136
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqsh.html
    • 1342 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:
    • Updating aws-shell would introduce bugs in testing: #944542
    • Not built on buildd: arch all binaries uploaded by takaki, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aws-shell.html
    • 1345 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
    • 1355 days old (needed 5 days)
• easyspice (- to 0.6.8-3)
  • Migration status for easyspice (- to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating easyspice would introduce bugs in testing: #967916
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1358 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
    • 1365 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: #905782
    • autopkgtest for bdfproxy/0.3.9-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdfproxy.html
    • 1368 days old (needed 5 days)
• j4-dmenu-desktop (- to 2.16-1)
  • Migration status for j4-dmenu-desktop (- to 2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating j4-dmenu-desktop would introduce bugs in testing: #972992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/j4-dmenu-desktop.html
    • 1368 days old (needed 5 days)
• gconf-editor (- to 3.0.1-6)
  • Migration status for gconf-editor (- to 3.0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gconf-editor would introduce bugs in testing: #947523
    • gconf-editor unsatisfiable Build-Depends(-Arch) on amd64: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on arm64: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on armel: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on armhf: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on i386: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on mips64el: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on mipsel: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on ppc64el: gnome-doc-utils
    • gconf-editor unsatisfiable Build-Depends(-Arch) on s390x: gnome-doc-utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gconf-editor.html
    • 1369 days old (needed 5 days)
• limereg (- to 1.4.1-4)
  • Migration status for limereg (- to 1.4.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • limereg/amd64 has unsatisfiable dependency
    • limereg/arm64 has unsatisfiable dependency
    • limereg/armel has unsatisfiable dependency
    • limereg/armhf has unsatisfiable dependency
    • limereg/i386 has unsatisfiable dependency
    • limereg/mips64el has unsatisfiable dependency
    • limereg/mipsel has unsatisfiable dependency
    • limereg/ppc64el has unsatisfiable dependency
    • limereg/s390x has unsatisfiable dependency
    • Updating limereg would introduce bugs in testing: #922584
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/limereg.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
    • 1372 days old (needed 5 days)
• crtmpserver (- to 1.0~dfsg-5.5)
  • Migration status for crtmpserver (- to 1.0~dfsg-5.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crtmpserver would introduce bugs in testing: #954903
    • Depends: crtmpserver openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crtmpserver.html
    • 1381 days old (needed 5 days)
• diet-ng (- to 1.5.0-1)
  • Migration status for diet-ng (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating diet-ng would introduce bugs in testing: #944626
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared86/1:1.16.0-1+b1/armhf
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared94/1:1.24.0-2/amd64
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared94/1:1.24.0-2/arm64
    • Impossible Depends: diet-ng -> libphobos2-ldc-shared94/1:1.24.0-2/i386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diet-ng.html
    • 1382 days old (needed 5 days)
• ruby-codemirror-rails (- to 5.16.0-1)
  • Migration status for ruby-codemirror-rails (- to 5.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-codemirror-rails would introduce bugs in testing: #964964
    • autopkgtest for ruby-codemirror-rails/5.16.0-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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-codemirror-rails.html
    • 1384 days old (needed 5 days)
• perl-doc-html (- to 5.26.0-4)
  • Migration status for perl-doc-html (- to 5.26.0-4): 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
    • 1385 days old (needed 5 days)
• undertaker (- to 1.6.1-4.2)
  • Migration status for undertaker (- to 1.6.1-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • undertaker/amd64 has unsatisfiable dependency
    • undertaker/arm64 has unsatisfiable dependency
    • undertaker/armel has unsatisfiable dependency
    • undertaker/armhf has unsatisfiable dependency
    • undertaker/i386 has unsatisfiable dependency
    • undertaker/mips64el has unsatisfiable dependency
    • undertaker/mipsel has unsatisfiable dependency
    • undertaker/ppc64el has unsatisfiable dependency
    • undertaker/s390x has unsatisfiable dependency
    • Updating undertaker would introduce bugs in testing: #938754
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/u/undertaker.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
    • 1385 days old (needed 5 days)
• sqlite (- to 2.8.17-15)
  • Migration status for sqlite (- to 2.8.17-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqlite would introduce bugs in testing: #607969
    • Not built on buildd: arch all binaries uploaded by gcs, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlite.html
    • 1389 days old (needed 5 days)
• vmtk (- to 1.3+dfsg-2.3)
  • Migration status for vmtk (- to 1.3+dfsg-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libvmtk1.3/amd64 has unsatisfiable dependency
    • python-vmtk/amd64 has unsatisfiable dependency
    • vmtk/amd64 has unsatisfiable dependency
    • vmtk/arm64 has unsatisfiable dependency
    • libvmtk1.3/i386 has unsatisfiable dependency
    • python-vmtk/i386 has unsatisfiable dependency
    • Updating vmtk would introduce bugs in testing: #938795
    • vmtk unsatisfiable Build-Depends(-Arch) on amd64: python-dev
    • vmtk unsatisfiable Build-Depends(-Arch) on amd64: python-vtk6
    • vmtk unsatisfiable Build-Depends(-Arch) on amd64: libvtkgdcm2-dev
    • vmtk unsatisfiable Build-Depends(-Arch) on amd64: libvtk6-java
    • vmtk unsatisfiable Build-Depends(-Arch) on i386: python-dev
    • vmtk unsatisfiable Build-Depends(-Arch) on i386: python-vtk6
    • vmtk unsatisfiable Build-Depends(-Arch) on i386: libvtkgdcm2-dev
    • vmtk unsatisfiable Build-Depends(-Arch) on i386: libvtk6-java
    • Build-Depends(-Arch): vmtk vtk6
  • 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
    • 1398 days old (needed 5 days)
• geda-gaf (- to 1:1.8.2-11)
  • Migration status for geda-gaf (- to 1:1.8.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • geda-gattrib/amd64 has unsatisfiable dependency
    • geda-gnetlist/amd64 has unsatisfiable dependency
    • geda-gschem/amd64 has unsatisfiable dependency
    • geda-gsymcheck/amd64 has unsatisfiable dependency
    • geda-utils/amd64 has unsatisfiable dependency
    • libgeda-dev/amd64 has unsatisfiable dependency
    • libgeda42/amd64 has unsatisfiable dependency
    • geda-gattrib/arm64 has unsatisfiable dependency
    • geda-gnetlist/arm64 has unsatisfiable dependency
    • geda-gschem/arm64 has unsatisfiable dependency
    • geda-gsymcheck/arm64 has unsatisfiable dependency
    • geda-utils/arm64 has unsatisfiable dependency
    • libgeda-dev/arm64 has unsatisfiable dependency
    • libgeda42/arm64 has unsatisfiable dependency
    • geda-gattrib/armel has unsatisfiable dependency
    • geda-gnetlist/armel has unsatisfiable dependency
    • geda-gschem/armel has unsatisfiable dependency
    • geda-gsymcheck/armel has unsatisfiable dependency
    • geda-utils/armel has unsatisfiable dependency
    • libgeda-dev/armel has unsatisfiable dependency
    • libgeda42/armel has unsatisfiable dependency
    • geda-gattrib/armhf has unsatisfiable dependency
    • geda-gnetlist/armhf has unsatisfiable dependency
    • geda-gschem/armhf has unsatisfiable dependency
    • geda-gsymcheck/armhf has unsatisfiable dependency
    • geda-utils/armhf has unsatisfiable dependency
    • libgeda-dev/armhf has unsatisfiable dependency
    • libgeda42/armhf has unsatisfiable dependency
    • geda-gattrib/i386 has unsatisfiable dependency
    • geda-gnetlist/i386 has unsatisfiable dependency
    • geda-gschem/i386 has unsatisfiable dependency
    • geda-gsymcheck/i386 has unsatisfiable dependency
    • geda-utils/i386 has unsatisfiable dependency
    • libgeda-dev/i386 has unsatisfiable dependency
    • libgeda42/i386 has unsatisfiable dependency
    • geda-gattrib/mips64el has unsatisfiable dependency
    • geda-gnetlist/mips64el has unsatisfiable dependency
    • geda-gschem/mips64el has unsatisfiable dependency
    • geda-gsymcheck/mips64el has unsatisfiable dependency
    • geda-utils/mips64el has unsatisfiable dependency
    • libgeda-dev/mips64el has unsatisfiable dependency
    • libgeda42/mips64el has unsatisfiable dependency
    • geda-gattrib/mipsel has unsatisfiable dependency
    • geda-gnetlist/mipsel has unsatisfiable dependency
    • geda-gschem/mipsel has unsatisfiable dependency
    • geda-gsymcheck/mipsel has unsatisfiable dependency
    • geda-utils/mipsel has unsatisfiable dependency
    • libgeda-dev/mipsel has unsatisfiable dependency
    • libgeda42/mipsel has unsatisfiable dependency
    • geda-gattrib/ppc64el has unsatisfiable dependency
    • geda-gnetlist/ppc64el has unsatisfiable dependency
    • geda-gschem/ppc64el has unsatisfiable dependency
    • geda-gsymcheck/ppc64el has unsatisfiable dependency
    • geda-utils/ppc64el has unsatisfiable dependency
    • libgeda-dev/ppc64el has unsatisfiable dependency
    • libgeda42/ppc64el has unsatisfiable dependency
    • geda-gattrib/s390x has unsatisfiable dependency
    • geda-gnetlist/s390x has unsatisfiable dependency
    • geda-gschem/s390x has unsatisfiable dependency
    • geda-gsymcheck/s390x has unsatisfiable dependency
    • geda-utils/s390x has unsatisfiable dependency
    • libgeda-dev/s390x has unsatisfiable dependency
    • libgeda42/s390x has unsatisfiable dependency
    • Updating geda-gaf would introduce bugs in testing: #885195, #936593, #966736
    • geda-gaf unsatisfiable Build-Depends(-Arch) on amd64: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on arm64: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on armel: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on armhf: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on i386: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on mips64el: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on mipsel: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on ppc64el: guile-2.0-dev
    • geda-gaf unsatisfiable Build-Depends(-Arch) on s390x: guile-2.0-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/geda-gaf.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
    • 1400 days old (needed 5 days)
• vzquota (- to 3.1-4)
  • Migration status for vzquota (- to 3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vzquota would introduce bugs in testing: #970917
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vzquota.html
    • 1406 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
    • 1412 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 mipsel
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 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
    • 1414 days old (needed 5 days)
• openscap-daemon (- to 0.1.10-3)
  • Migration status for openscap-daemon (- to 0.1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openscap-daemon/amd64 has unsatisfiable dependency
    • openscap-daemon/arm64 has unsatisfiable dependency
    • autopkgtest for openscap-daemon/0.1.10-3: armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
  • 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
    • 1416 days old (needed 5 days)
• libgit-objectstore-perl (- to 0.007-2)
  • Migration status for libgit-objectstore-perl (- to 0.007-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libgit-objectstore-perl libgit-raw-perl (not considered)
    • Depends: libgit-objectstore-perl libgit-raw-perl (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgit-objectstore-perl.html
    • autopkgtest for libgit-objectstore-perl/0.007-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1420 days old (needed 2 days)
• ladvd (- to 1.1.2-1)
  • Migration status for ladvd (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ladvd would introduce bugs in testing: #994677
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ladvd.html
    • 1426 days old (needed 5 days)
• drawtiming (- to 0.7.1-7)
  • Migration status for drawtiming (- to 0.7.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drawtiming would introduce bugs in testing: #984038
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drawtiming.html
    • 1427 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)
    • 1450 days old (needed 5 days)
• bino (- to 1.6.6-3)
  • Migration status for bino (- to 1.6.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bino would introduce bugs in testing: #983990
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bino.html
    • 1453 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: #984418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xqilla.html
    • 1455 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
    • 1465 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
    • 1466 days old (needed 5 days)
• php-cache-lite (- to 1.8.2-1)
  • Migration status for php-cache-lite (- to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-cache-lite would introduce bugs in testing: #940275, #941264
    • autopkgtest for php-cache-lite/1.8.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-cache-lite.html
    • 1480 days old (needed 5 days)
• ruby-omniauth-cas3 (- to 1.1.4-2)
  • Migration status for ruby-omniauth-cas3 (- to 1.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-cas3 would introduce bugs in testing: #999713
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-cas3.html
    • autopkgtest for ruby-omniauth-cas3/1.1.4-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1480 days old (needed 2 days)
• childsplay (- to 3.3-2)
  • Migration status for childsplay (- to 3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • childsplay/amd64 has unsatisfiable dependency
    • childsplay/arm64 has unsatisfiable dependency
    • Updating childsplay would introduce bugs in testing: #912485, #936298
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/childsplay.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1493 days old (needed 5 days)
• astk (- to 1.13.1-2.1)
  • Migration status for astk (- to 1.13.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • code-aster-run/amd64 has unsatisfiable dependency
    • code-aster-run/arm64 has unsatisfiable dependency
    • Updating astk would introduce bugs in testing: #936159
    • Not built on buildd: arch all binaries uploaded by sgolovan, 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/a/astk.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1505 days old (needed 5 days)
• netmaze (- to 0.81+jpg0.82-16)
  • Migration status for netmaze (- to 0.81+jpg0.82-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netmaze would introduce bugs in testing: #999062
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netmaze.html
    • 1507 days old (needed 5 days)
• ctioga2 (- to 0.14.1-2)
  • Migration status for ctioga2 (- to 0.14.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ctioga2 would introduce bugs in testing: #1008409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctioga2.html
    • autopkgtest for ctioga2/0.14.1-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results, s390x: No test results
    • 1517 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
    • 1517 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
    • 1518 days old (needed 5 days)
• cl-pg (- to 1:20061216-6)
  • Migration status for cl-pg (- to 1:20061216-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-pg would introduce bugs in testing: #998973
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-pg.html
    • 1525 days old (needed 5 days)
• condor (- to 8.6.8~dfsg.1-2)
  • Migration status for condor (- to 8.6.8~dfsg.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • htcondor/amd64 has unsatisfiable dependency
    • htcondor/arm64 has unsatisfiable dependency
    • htcondor/armel has unsatisfiable dependency
    • htcondor/armhf has unsatisfiable dependency
    • htcondor/i386 has unsatisfiable dependency
    • htcondor/mips64el has unsatisfiable dependency
    • htcondor/mipsel has unsatisfiable dependency
    • htcondor/ppc64el has unsatisfiable dependency
    • htcondor/s390x has unsatisfiable dependency
    • Updating condor would introduce bugs in testing: #1002540, #1008634, #925657, #963777, #966726, #995838
    • condor unsatisfiable Build-Depends(-Arch) on amd64: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on arm64: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on armel: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on armhf: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on i386: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on mips64el: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on mipsel: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on ppc64el: python-dev
    • condor unsatisfiable Build-Depends(-Arch) on s390x: python-dev
    • Not built on buildd: arch all binaries uploaded by mih, 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/c/condor.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
    • 1527 days old (needed 5 days)
• phpunit-dbunit (- to 4.0.0-2)
  • Migration status for phpunit-dbunit (- to 4.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpunit-dbunit/amd64 has unsatisfiable dependency
    • phpunit-dbunit/arm64 has unsatisfiable dependency
    • Updating phpunit-dbunit would introduce bugs in testing: #935639
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/phpunit-dbunit.html
    • autopkgtest for phpunit-dbunit/4.0.0-2: armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1534 days old (needed 5 days)
• ruby-omniauth-saml (- to 1.10.0-1)
  • Migration status for ruby-omniauth-saml (- to 1.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-saml would introduce bugs in testing: #999725
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-saml.html
    • autopkgtest for ruby-omniauth-saml/1.10.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1536 days old (needed 2 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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
    • 1537 days old (needed 5 days)
• pluxml (- to 5.6-1)
  • Migration status for pluxml (- to 5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pluxml would introduce bugs in testing: #1008264
    • Not built on buildd: arch all binaries uploaded by tanguy+debian@ortolo.eu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluxml.html
    • 1542 days old (needed 5 days)
• bindgraph (- to 0.2a-6)
  • Migration status for bindgraph (- to 0.2a-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bindgraph would introduce bugs in testing: #806946, #931756
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bindgraph.html
    • 1548 days old (needed 5 days)
• sicherboot (- to 0.1.5)
  • Migration status for sicherboot (- to 0.1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sicherboot would introduce bugs in testing: #1012626, #901610
    • Not built on buildd: arch all binaries uploaded by jak, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sicherboot.html
    • 1548 days old (needed 5 days)
• verdigris (- to 1.0-1)
  • Migration status for verdigris (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verdigris would introduce bugs in testing: #952157
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verdigris.html
    • 1555 days old (needed 5 days)
• phing (- to 2.16.1-1)
  • Migration status for phing (- to 2.16.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phing would introduce bugs in testing: #978457
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phing.html
    • 1556 days old (needed 5 days)
• funny-manpages (- to 2.3-1)
  • Migration status for funny-manpages (- to 2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating funny-manpages would introduce bugs in testing: #737395
    • Not built on buildd: arch all binaries uploaded by mattia@mapreri.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/funny-manpages.html
    • 1560 days old (needed 5 days)
• android-platform-tools-base (- to 2.2.2-3)
  • Migration status for android-platform-tools-base (- to 2.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-tools-base would introduce bugs in testing: #894284, #994093
    • Not built on buildd: arch all binaries uploaded by eighthave, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): android-platform-tools-base android-platform-frameworks-data-binding
    • Build-Depends(-Arch): android-platform-tools-base android-platform-tools-analytics-library
    • Depends: android-platform-tools-base android-platform-frameworks-data-binding
    • Depends: android-platform-tools-base android-platform-tools-analytics-library
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-tools-base.html
    • 1563 days old (needed 5 days)
• ruby-redis-rails (- to 5.0.2-3)
  • Migration status for ruby-redis-rails (- to 5.0.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-store (not considered)
    • Depends: ruby-redis-rails ruby-redis-store (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-actionpack
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-activesupport
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-rack
    • Depends: ruby-redis-rails ruby-redis-actionpack
    • Depends: ruby-redis-rails ruby-redis-activesupport
    • Depends: ruby-redis-rails ruby-redis-rack
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-rails.html
    • autopkgtest for ruby-redis-rails/5.0.2-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1567 days old (needed 2 days)
• ffdiaporama (- to 2.1+dfsg-1)
  • Migration status for ffdiaporama (- to 2.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ffdiaporama would introduce bugs in testing: #997138
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ffdiaporama.html
    • 1569 days old (needed 5 days)
• ruby-rack-mount (- to 0.8.3-3)
  • Migration status for ruby-rack-mount (- to 0.8.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rack-mount would introduce bugs in testing: #1004654
    • autopkgtest for ruby-rack-mount/0.8.3-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rack-mount.html
    • 1571 days old (needed 5 days)
• golang-openldap (- to 0.2-2)
  • Migration status for golang-openldap (- to 0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-openldap would introduce bugs in testing: #1007217, #1010679
    • Impossible Depends: golang-openldap -> libldap-2.4-2/2.4.59+dfsg-1+b1/amd64
    • Impossible Depends: golang-openldap -> libldap-2.4-2/2.4.59+dfsg-1+b1/arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-openldap.html
    • 1582 days old (needed 5 days)
• golang-go-dbus (- to 1~bzr20150122-3)
  • Migration status for golang-go-dbus (- to 1~bzr20150122-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-go-dbus would introduce bugs in testing: #952299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-go-dbus.html
    • 1583 days old (needed 5 days)
• golang-glide (- to 0.13.1-3)
  • Migration status for golang-glide (- to 0.13.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-glide golang-codegangsta-cli (not considered)
    • Built-Using: golang-glide golang-codegangsta-cli (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-glide.html
    • autopkgtest for golang-glide/0.13.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1586 days old (needed 2 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
    • 1587 days old (needed 5 days)
• pd-py (- to 0.2.2+git20170625.1.88fc77a-2)
  • Migration status for pd-py (- to 0.2.2+git20170625.1.88fc77a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pd-py/amd64 has unsatisfiable dependency
    • pd-py/arm64 has unsatisfiable dependency
    • pd-py/armel has unsatisfiable dependency
    • pd-py/armhf has unsatisfiable dependency
    • pd-py/i386 has unsatisfiable dependency
    • pd-py/mips64el has unsatisfiable dependency
    • pd-py/mipsel has unsatisfiable dependency
    • pd-py/ppc64el has unsatisfiable dependency
    • pd-py/s390x has unsatisfiable dependency
    • Updating pd-py would introduce bugs in testing: #937266
    • pd-py unsatisfiable Build-Depends(-Arch) on amd64: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on amd64: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on arm64: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on arm64: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on armel: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on armel: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on armhf: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on armhf: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on i386: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on i386: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on mips64el: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on mips64el: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on mipsel: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on mipsel: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on ppc64el: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on ppc64el: python-numpy
    • pd-py unsatisfiable Build-Depends(-Arch) on s390x: python-dev
    • pd-py unsatisfiable Build-Depends(-Arch) on s390x: python-numpy
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pd-py.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
    • 1587 days old (needed 5 days)
• gnuboy (- to 1.0.3-7.1)
  • Migration status for gnuboy (- to 1.0.3-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnuboy would introduce bugs in testing: #998967
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1608 days old (needed 5 days)
• xpuzzles (- to 7.7.1-1.1)
  • Migration status for xpuzzles (- to 7.7.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xpuzzles would introduce bugs in testing: #999086
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpuzzles.html
    • 1608 days old (needed 5 days)
• ipkungfu (- to 0.6.1-6.2)
  • Migration status for ipkungfu (- to 0.6.1-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ipkungfu would introduce bugs in testing: #863263, #965599, #999202
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipkungfu.html
    • 1611 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
    • 1613 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/mipsel 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/boinc-app-eah-brp.html
    • 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 mipsel: 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:
    • 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
    • 1614 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debirf.html
    • 1614 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
    • 1620 days old (needed 5 days)
• patchage (- to 1.0.0~dfsg0-0.2)
  • Migration status for patchage (- to 1.0.0~dfsg0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating patchage would introduce bugs in testing: #967195, #992247
    • patchage unsatisfiable Build-Depends(-Arch) on amd64: python
    • patchage unsatisfiable Build-Depends(-Arch) on arm64: python
    • patchage unsatisfiable Build-Depends(-Arch) on armel: python
    • patchage unsatisfiable Build-Depends(-Arch) on armhf: python
    • patchage unsatisfiable Build-Depends(-Arch) on i386: python
    • patchage unsatisfiable Build-Depends(-Arch) on mips64el: python
    • patchage unsatisfiable Build-Depends(-Arch) on mipsel: python
    • patchage unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • patchage unsatisfiable Build-Depends(-Arch) on s390x: python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patchage.html
    • 1620 days old (needed 5 days)
• postnews (- to 0.7-1)
  • Migration status for postnews (- to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • postnews/amd64 has unsatisfiable dependency
    • postnews/arm64 has unsatisfiable dependency
    • Updating postnews would introduce bugs in testing: #937312
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/postnews.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1624 days old (needed 5 days)
• restbed (- to 4.0~dfsg1-5)
  • Migration status for restbed (- to 4.0~dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating restbed would introduce bugs in testing: #957758
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restbed.html
    • 1625 days old (needed 5 days)
• snowballz (- to 0.9.5.1-5)
  • Migration status for snowballz (- to 0.9.5.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • snowballz/amd64 has unsatisfiable dependency
    • snowballz/arm64 has unsatisfiable dependency
    • Updating snowballz would introduce bugs in testing: #938509
    • snowballz unsatisfiable Build-Depends(-Arch) on amd64: python (>= 2.6.6-3~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/snowballz.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1634 days old (needed 5 days)
• falcon (- to 1.8.8-1)
  • Migration status for falcon (- to 1.8.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • falcon/amd64 has unsatisfiable dependency
    • falcon/arm64 has unsatisfiable dependency
    • falcon/mips64el has unsatisfiable dependency
    • falcon/ppc64el has unsatisfiable dependency
    • falcon/s390x has unsatisfiable dependency
    • Updating falcon would introduce bugs in testing: #902132, #936503
    • falcon unsatisfiable Build-Depends(-Arch) on amd64: python-networkx (>= 1.7)
    • falcon unsatisfiable Build-Depends(-Arch) on amd64: python-nose
    • falcon unsatisfiable Build-Depends(-Arch) on amd64: python-pytest
    • falcon unsatisfiable Build-Depends(-Arch) on arm64: python-networkx (>= 1.7)
    • falcon unsatisfiable Build-Depends(-Arch) on arm64: python-nose
    • falcon unsatisfiable Build-Depends(-Arch) on arm64: python-pytest
    • falcon unsatisfiable Build-Depends(-Arch) on mips64el: python-networkx (>= 1.7)
    • falcon unsatisfiable Build-Depends(-Arch) on mips64el: python-nose
    • falcon unsatisfiable Build-Depends(-Arch) on mips64el: python-pytest
    • falcon unsatisfiable Build-Depends(-Arch) on ppc64el: python-networkx (>= 1.7)
    • falcon unsatisfiable Build-Depends(-Arch) on ppc64el: python-nose
    • falcon unsatisfiable Build-Depends(-Arch) on ppc64el: python-pytest
    • falcon unsatisfiable Build-Depends(-Arch) on s390x: python-networkx (>= 1.7)
    • falcon unsatisfiable Build-Depends(-Arch) on s390x: python-nose
    • falcon unsatisfiable Build-Depends(-Arch) on s390x: python-pytest
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/falcon.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
    • 1638 days old (needed 5 days)
• libmagpie-perl (- to 1.163200-1)
  • Migration status for libmagpie-perl (- to 1.163200-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): libmagpie-perl libkiokux-model-perl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmagpie-perl.html
    • 1648 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
    • 1655 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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
    • 1670 days old (needed 5 days)
• grpn (- to 1.4.1-1)
  • Migration status for grpn (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grpn would introduce bugs in testing: #999170
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grpn.html
    • 1672 days old (needed 5 days)
• gerstensaft (- to 0.3-4.2)
  • Migration status for gerstensaft (- to 0.3-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gerstensaft would introduce bugs in testing: #999035
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gerstensaft.html
    • 1674 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
    • 1689 days old (needed 5 days)
• yecht (- to 1.1-3)
  • Migration status for yecht (- to 1.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): yecht jruby (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yecht.html
    • 1690 days old (needed 5 days)
• net-telnet-cisco (- to 1.10-5.3)
  • Migration status for net-telnet-cisco (- to 1.10-5.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating net-telnet-cisco would introduce bugs in testing: #999285
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/net-telnet-cisco.html
    • 1705 days old (needed 5 days)
• libwibble (- to 1.1-2)
  • Migration status for libwibble (- to 1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libwibble would introduce bugs in testing: #984211
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwibble.html
    • 1725 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): urweb mlton (not considered)
    • Invalidated by build-dependency
    • Depends: urweb openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
    • 1727 days old (needed 5 days)
• i8c (- to 0.0.6-1)
  • Migration status for i8c (- to 0.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): i8c libi8x (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i8c.html
    • 1734 days old (needed 5 days)
• libi8x (- to 0.0.5-1)
  • Migration status for libi8x (- to 0.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-libi8x/amd64 has unsatisfiable dependency
    • python3-libi8x/arm64 has unsatisfiable dependency
    • python3-libi8x/armel has unsatisfiable dependency
    • python3-libi8x/armhf has unsatisfiable dependency
    • python3-libi8x/i386 has unsatisfiable dependency
    • python3-libi8x/mips64el has unsatisfiable dependency
    • python3-libi8x/mipsel has unsatisfiable dependency
    • python3-libi8x/ppc64el has unsatisfiable dependency
    • Updating libi8x would introduce bugs in testing: #875373, #918519
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libi/libi8x.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
    • 1734 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:
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2+b1/mips64el
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/amd64
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/arm64
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/armel
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/armhf
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/i386
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/mipsel
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/ppc64el
    • Impossible Depends: opengrm-ngram -> libfst8/1.6.3-2/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opengrm-ngram.html
    • 1739 days old (needed 5 days)
• cgilib (- to 0.6-1.1)
  • Migration status for cgilib (- to 0.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cgilib would introduce bugs in testing: #998933
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cgilib.html
    • 1742 days old (needed 5 days)
• shush (- to 1.2.3-5)
  • Migration status for shush (- to 1.2.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shush would introduce bugs in testing: #1003543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • 1753 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-3)
  • Migration status for libjpeg6b (- to 1:6b2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libjpeg6b would introduce bugs in testing: #999306
    • Not built on buildd: arch amd64 binaries uploaded by ballombe
    • 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/libjpeg6b.html
    • 1764 days old (needed 5 days)
• sbt (- to 0.13.13-2)
  • Migration status for sbt (- to 0.13.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sbt would introduce bugs in testing: #894540, #915504
    • Not built on buildd: arch all binaries uploaded by tmancill, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbt.html
    • 1764 days old (needed 5 days)
• phpunit-git (- to 2.1.4-1)
  • Migration status for phpunit-git (- to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phpunit-git would introduce bugs in testing: #935384
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpunit-git.html
    • 1771 days old (needed 5 days)
• ruby-omniauth-twitter (- to 1.4.0-1)
  • Migration status for ruby-omniauth-twitter (- to 1.4.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-omniauth-twitter ruby-omniauth-oauth (not considered)
    • Depends: ruby-omniauth-twitter ruby-omniauth-oauth (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-twitter.html
    • autopkgtest for ruby-omniauth-twitter/1.4.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1787 days old (needed 2 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
    • 1794 days old (needed 5 days)
• xdeb (- to 0.6.7)
  • Migration status for xdeb (- to 0.6.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xdeb/amd64 has unsatisfiable dependency
    • xdeb/arm64 has unsatisfiable dependency
    • Updating xdeb would introduce bugs in testing: #943266
    • xdeb unsatisfiable Build-Depends-Indep on amd64: python (>= 2.7)
    • xdeb unsatisfiable Build-Depends-Indep on amd64: python-debian (>= 0.1.15~)
    • xdeb unsatisfiable Build-Depends-Indep on amd64: python-apt (>= 0.7.91)
    • Not built on buildd: arch all binaries uploaded by lool, 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/x/xdeb.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1796 days old (needed 5 days)
• squishyball (- to 0.1~svn19085-5)
  • Migration status for squishyball (- to 0.1~svn19085-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squishyball would introduce bugs in testing: #997288
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squishyball.html
    • 1797 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
    • 1799 days old (needed 5 days)
• quickroute-gps (- to 2.4-15)
  • Migration status for quickroute-gps (- to 2.4-15): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): quickroute-gps log4net (not considered)
    • Depends: quickroute-gps log4net (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickroute-gps.html
    • 1803 days old (needed 5 days)
• stymulator (- to 0.21a~dfsg-2)
  • Migration status for stymulator (- to 0.21a~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stymulator would introduce bugs in testing: #999080
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stymulator.html
    • 1810 days old (needed 5 days)
• camping (- to 2.1.580-1.1)
  • Migration status for camping (- to 2.1.580-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating camping would introduce bugs in testing: #915837
    • Not built on buildd: arch all binaries uploaded by debian.axhn@manchmal.in-ulm.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camping.html
    • 1856 days old (needed 5 days)
• dhcpdump (- to 1.8-2.2)
  • Migration status for dhcpdump (- to 1.8-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dhcpdump would introduce bugs in testing: #999183
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhcpdump.html
    • 1880 days old (needed 5 days)
• libibtk (- to 0.0.14-12.1)
  • Migration status for libibtk (- to 0.0.14-12.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libibtk would introduce bugs in testing: #965644, #999106
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libibtk.html
    • 1896 days old (needed 5 days)
• mclibs (- to 20061220+dfsg3-3.1)
  • Migration status for mclibs (- to 20061220+dfsg3-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cernlib-montecarlo/arm64 has unsatisfiable dependency
    • Updating mclibs would introduce bugs in testing: #957522, #965715
    • Build-Depends(-Arch): mclibs cernlib
    • Depends: mclibs cernlib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mclibs.html
    • uninstallable on arch arm64, not running autopkgtest there
    • 1898 days old (needed 5 days)
• scim-canna (- to 1.0.0-4.3)
  • Migration status for scim-canna (- to 1.0.0-4.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scim-canna would introduce bugs in testing: #1005984, #998928
    • Build-Depends(-Arch): scim-canna dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scim-canna.html
    • 1906 days old (needed 5 days)
• xfce4-equake-plugin (- to 1.3.8.1-2)
  • Migration status for xfce4-equake-plugin (- to 1.3.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xfce4-equake-plugin/amd64 has unsatisfiable dependency
    • xfce4-equake-plugin/arm64 has unsatisfiable dependency
    • xfce4-equake-plugin/armel has unsatisfiable dependency
    • xfce4-equake-plugin/armhf has unsatisfiable dependency
    • xfce4-equake-plugin/i386 has unsatisfiable dependency
    • xfce4-equake-plugin/mips64el has unsatisfiable dependency
    • xfce4-equake-plugin/mipsel has unsatisfiable dependency
    • xfce4-equake-plugin/ppc64el has unsatisfiable dependency
    • xfce4-equake-plugin/s390x has unsatisfiable dependency
    • Updating xfce4-equake-plugin would introduce bugs in testing: #978237
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/x/xfce4-equake-plugin.html
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on amd64: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on amd64: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on arm64: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on arm64: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on armel: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on armel: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on armhf: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on armhf: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on i386: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on i386: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on mips64el: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on mips64el: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on mipsel: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on mipsel: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on ppc64el: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on ppc64el: xfce4-panel-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on s390x: libxfce4ui-1-dev
    • xfce4-equake-plugin unsatisfiable Build-Depends(-Arch) on s390x: xfce4-panel-dev
  • Additional info:
    • 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
    • 1910 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
  • 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
    • 1920 days old (needed 5 days)
• python-django-push-notifications (- to 1.4.1-1)
  • Migration status for python-django-push-notifications (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-push-notifications would introduce bugs in testing: #917677
    • 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-push-notifications.html
    • 1925 days old (needed 5 days)
• lockdown (- to 0.2)
  • Migration status for lockdown (- to 0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lockdown would introduce bugs in testing: #958587
    • Not built on buildd: arch all binaries uploaded by taggart, a new source-only upload is needed to allow migration
    • Impossible Build-Depends(-Arch): lockdown -> dh-systemd/13.2.1/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lockdown.html
    • 1928 days old (needed 5 days)
• dh-kpatches (- to 0.99.36+nmu4)
  • Migration status for dh-kpatches (- to 0.99.36+nmu4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dh-kpatches would introduce bugs in testing: #876892, #999276
    • dh-kpatches unsatisfiable Build-Depends-Indep on amd64: nowebm
    • Not built on buildd: arch all binaries uploaded by lamby, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: dh-kpatches sgml2x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-kpatches.html
    • 1930 days old (needed 5 days)
• freebsd-buildutils (- to 10.3~svn296373-7)
  • Migration status for freebsd-buildutils (- to 10.3~svn296373-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freebsd-buildutils would introduce bugs in testing: #957230
    • 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-buildutils freebsd-glue
    • Build-Depends(-Arch): freebsd-buildutils freebsd-libs
    • 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
    • 1943 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:
    • Updating freebsd-libs would introduce bugs in testing: #964698
    • 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
    • 1953 days old (needed 5 days)
• clblas (- to 2.12-1)
  • Migration status for clblas (- to 2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clblas would introduce bugs in testing: #949767
    • clblas unsatisfiable Build-Depends(-Arch) on amd64: python
    • clblas unsatisfiable Build-Depends(-Arch) on arm64: python
    • clblas unsatisfiable Build-Depends(-Arch) on armel: python
    • clblas unsatisfiable Build-Depends(-Arch) on armhf: python
    • clblas unsatisfiable Build-Depends(-Arch) on i386: python
    • clblas unsatisfiable Build-Depends(-Arch) on mips64el: python
    • clblas unsatisfiable Build-Depends(-Arch) on mipsel: python
    • clblas unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • clblas unsatisfiable Build-Depends(-Arch) on s390x: python
    • 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/c/clblas.html
    • autopkgtest for clblas/2.12-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1962 days old (needed 2 days)
• ketchup (- to 1.0.1+git20111228+e1c62066-2)
  • Migration status for ketchup (- to 1.0.1+git20111228+e1c62066-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ketchup/amd64 has unsatisfiable dependency
    • ketchup/arm64 has unsatisfiable dependency
    • Updating ketchup would introduce bugs in testing: #936785
    • ketchup unsatisfiable Build-Depends(-Arch) on amd64: python (>= 2.6.6-3~)
    • Not built on buildd: arch all binaries uploaded by johfel@gmx.de, 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/k/ketchup.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1964 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
    • 1965 days old (needed 5 days)
• neard (- to 0.16-0.1)
  • Migration status for neard (- to 0.16-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • neard-tools/amd64 has unsatisfiable dependency
    • neard-tools/arm64 has unsatisfiable dependency
    • neard-tools/armel has unsatisfiable dependency
    • neard-tools/armhf has unsatisfiable dependency
    • neard-tools/i386 has unsatisfiable dependency
    • neard-tools/mips64el has unsatisfiable dependency
    • neard-tools/mipsel has unsatisfiable dependency
    • neard-tools/ppc64el has unsatisfiable dependency
    • neard-tools/s390x has unsatisfiable dependency
    • Updating neard would introduce bugs in testing: #937125
    • neard unsatisfiable Build-Depends(-Arch) on amd64: python
    • neard unsatisfiable Build-Depends(-Arch) on arm64: python
    • neard unsatisfiable Build-Depends(-Arch) on armel: python
    • neard unsatisfiable Build-Depends(-Arch) on armhf: python
    • neard unsatisfiable Build-Depends(-Arch) on i386: python
    • neard unsatisfiable Build-Depends(-Arch) on mips64el: python
    • neard unsatisfiable Build-Depends(-Arch) on mipsel: python
    • neard unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • neard unsatisfiable Build-Depends(-Arch) on s390x: python
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/neard.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
    • 1969 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
    • Build-Depends(-Arch): bookkeeper zookeeper
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookkeeper.html
    • 1971 days old (needed 5 days)
• tty-clock (- to 2.3-1)
  • Migration status for tty-clock (- to 2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tty-clock would introduce bugs in testing: #997179
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tty-clock.html
    • 1973 days old (needed 5 days)
• binutils-msp430 (- to 2.22~msp20120406-5.1)
  • Migration status for binutils-msp430 (- to 2.22~msp20120406-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-msp430 would introduce bugs in testing: #853329, #965439, #998996
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-msp430.html
    • 1974 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
    • 1974 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
    • 1974 days old (needed 5 days)
• gpsim-doc (- to 0.22.0-2.1)
  • Migration status for gpsim-doc (- to 0.22.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpsim-doc would introduce bugs in testing: #999299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpsim-doc.html
    • 1974 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
    • 1974 days old (needed 5 days)
• sapphire (- to 0.15.8-9.1)
  • Migration status for sapphire (- to 0.15.8-9.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sapphire would introduce bugs in testing: #999133
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sapphire.html
    • 1974 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gli.html
    • 1975 days old (needed 5 days)
• vmm (- to 0.6.2-2)
  • Migration status for vmm (- to 0.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vmm/amd64 has unsatisfiable dependency
    • vmm/arm64 has unsatisfiable dependency
    • Updating vmm would introduce bugs in testing: #938794
    • vmm unsatisfiable Build-Depends(-Arch) on amd64: python
    • vmm unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx
    • Not built on buildd: arch all binaries uploaded by madduck, 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/v/vmm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 1977 days old (needed 5 days)
• mytop (- to 1.9.1-4)
  • Migration status for mytop (- to 1.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mytop would introduce bugs in testing: #863596
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mytop.html
    • 1978 days old (needed 5 days)
• fsprotect (- to 1.0.7)
  • Migration status for fsprotect (- to 1.0.7): 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
    • 1979 days old (needed 5 days)
• ion (- to 3.2.1+dfsg-1.1)
  • Migration status for ion (- to 3.2.1+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ion would introduce bugs in testing: #853456
    • Not built on buildd: arch amd64 binaries uploaded by glaubitz@physik.fu-berlin.de
    • Not built on buildd: arch all binaries uploaded by glaubitz@physik.fu-berlin.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ion.html
    • 1979 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/mipsel has unsatisfiable dependency
    • rdup/ppc64el has unsatisfiable dependency
    • rdup/s390x has unsatisfiable dependency
    • Updating rdup would introduce bugs in testing: #941101
  • 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 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
    • 1979 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
    • 1984 days old (needed 5 days)
• sredird (- to 2.2.1-2)
  • Migration status for sredird (- to 2.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sredird would introduce bugs in testing: #999137
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sredird.html
    • 1988 days old (needed 5 days)
• niceshaper (- to 1.2.4-1)
  • Migration status for niceshaper (- to 1.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating niceshaper would introduce bugs in testing: #958605
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/amd64
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/arm64
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/armel
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/armhf
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/i386
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/mips64el
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/mipsel
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/ppc64el
    • Impossible Build-Depends(-Arch): niceshaper -> dh-systemd/13.2.1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/niceshaper.html
    • 1991 days old (needed 5 days)
• hashcash (- to 1.21-2)
  • Migration status for hashcash (- to 1.21-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hashcash would introduce bugs in testing: #999030
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hashcash.html
    • 1993 days old (needed 5 days)
• petri-foo (- to 0.1.87-4)
  • Migration status for petri-foo (- to 0.1.87-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating petri-foo would introduce bugs in testing: #980023
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/petri-foo.html
    • 1994 days old (needed 5 days)
• dpkg-sig (- to 0.13.1+nmu4)
  • Migration status for dpkg-sig (- to 0.13.1+nmu4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dpkg-sig would introduce bugs in testing: #995113
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dpkg-sig.html
    • 1996 days old (needed 5 days)
• gnuift (- to 0.1.14+ds-1)
  • Migration status for gnuift (- to 0.1.14+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnuift would introduce bugs in testing: #897761, #906032
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuift.html
    • 1998 days old (needed 5 days)
• libmail-verify-perl (- to 0.02-5.1)
  • Migration status for libmail-verify-perl (- to 0.02-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libmail-verify-perl would introduce bugs in testing: #999148
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmail-verify-perl.html
    • 1999 days old (needed 5 days)
• lua-luaossl (- to 20161214-1)
  • Migration status for lua-luaossl (- to 20161214-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lua-luaossl would introduce bugs in testing: #1005697
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-luaossl.html
    • 2003 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:
    • Removal request by ginggs
    • Trying to remove package, not update it
    • autopkgtest for ruby-uglifier/2.7.2+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-uglifier.html
    • 2005 days old (needed 5 days)
• scalapack-doc (- to 1.5-11)
  • Migration status for scalapack-doc (- to 1.5-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scalapack-doc would introduce bugs in testing: #1003525, #965810
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scalapack-doc.html
    • 2008 days old (needed 5 days)
• aribas (- to 1.64-6)
  • Migration status for aribas (- to 1.64-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aribas would introduce bugs in testing: #1001653
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aribas.html
    • autopkgtest for aribas/1.64-6: amd64: Pass, arm64: Pass, armhf: Pass, i386: Not a regression, ppc64el: Pass, s390x: Pass
    • 2009 days old (needed 5 days)
• tagcoll2 (- to 2.0.14-2)
  • Migration status for tagcoll2 (- to 2.0.14-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tagcoll2 libwibble (not considered)
    • Depends: tagcoll2 libwibble (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tagcoll2.html
    • 2016 days old (needed 5 days)
• tasque (- to 0.1.12-4.1)
  • Migration status for tasque (- to 0.1.12-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tasque notify-sharp (not considered)
    • Depends: tasque notify-sharp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tasque.html
    • 2016 days old (needed 5 days)
• debget (- to 1.6+nmu4)
  • Migration status for debget (- to 1.6+nmu4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debget would introduce bugs in testing: #816393, #999257
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debget.html
    • 2017 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
    • 2018 days old (needed 5 days)
• guacamole-client (- to 0.9.9+dfsg-1)
  • Migration status for guacamole-client (- to 0.9.9+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • guacamole/amd64 has unsatisfiable dependency
    • guacamole/arm64 has unsatisfiable dependency
    • Updating guacamole-client would introduce bugs in testing: #891798, #926275, #926276
    • guacamole-client unsatisfiable Build-Depends(-Arch) on amd64: libangular-maven-plugin-java
    • Not built on buildd: arch all binaries uploaded by nik@naturalnet.de, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): guacamole-client minify-maven-plugin
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/guacamole-client.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 2019 days old (needed 5 days)
• php-xml-rpc2 (- to 1.1.3-0.1)
  • Migration status for php-xml-rpc2 (- to 1.1.3-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ondrej, a new source-only upload is needed to allow migration
    • Depends: php-xml-rpc2 php-cache-lite
    • Depends: php-xml-rpc2 php-http-request2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-xml-rpc2.html
    • 2019 days old (needed 5 days)
• tntdb (- to 1.3-4)
  • Migration status for tntdb (- to 1.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tntdb cxxtools (not considered)
    • Depends: tntdb cxxtools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tntdb.html
    • 2029 days old (needed 5 days)
• phpsysinfo (- to 3.2.5-3)
  • Migration status for phpsysinfo (- to 3.2.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phpsysinfo would introduce bugs in testing: #1010244, #965776
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpsysinfo.html
    • 2032 days old (needed 5 days)
• genparse (- to 0.9.2-1)
  • Migration status for genparse (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating genparse would introduce bugs in testing: #984149
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genparse.html
    • 2034 days old (needed 5 days)
• kismet (- to 2016.07.R1-1)
  • Migration status for kismet (- to 2016.07.R1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kismet would introduce bugs in testing: #954636
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kismet.html
    • 2035 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
    • 2037 days old (needed 5 days)
• zyn (- to 1+git.20100609+dfsg0-4)
  • Migration status for zyn (- to 1+git.20100609+dfsg0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zyn would introduce bugs in testing: #964696, #967236
    • zyn unsatisfiable Build-Depends(-Arch) on amd64: python
    • zyn unsatisfiable Build-Depends(-Arch) on arm64: python
    • zyn unsatisfiable Build-Depends(-Arch) on armel: python
    • zyn unsatisfiable Build-Depends(-Arch) on armhf: python
    • zyn unsatisfiable Build-Depends(-Arch) on i386: python
    • zyn unsatisfiable Build-Depends(-Arch) on mips64el: python
    • zyn unsatisfiable Build-Depends(-Arch) on mipsel: python
    • zyn unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • zyn unsatisfiable Build-Depends(-Arch) on s390x: python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zyn.html
    • 2038 days old (needed 5 days)
• debdry (- to 0.2.2-1)
  • Migration status for debdry (- to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debdry would introduce bugs in testing: #954560
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debdry.html
    • 2055 days old (needed 5 days)
• python-passfd (- to 0.2-3)
  • Migration status for python-passfd (- to 0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-passfd/amd64 has unsatisfiable dependency
    • python-passfd/arm64 has unsatisfiable dependency
    • python-passfd/armel has unsatisfiable dependency
    • python-passfd/armhf has unsatisfiable dependency
    • python-passfd/i386 has unsatisfiable dependency
    • python-passfd/mips64el has unsatisfiable dependency
    • python-passfd/mipsel has unsatisfiable dependency
    • python-passfd/ppc64el has unsatisfiable dependency
    • python-passfd/s390x has unsatisfiable dependency
    • Updating python-passfd would introduce bugs in testing: #938001
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-passfd.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
    • 2055 days old (needed 5 days)
• python-unshare (- to 0.2-1)
  • Migration status for python-unshare (- to 0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-unshare/amd64 has unsatisfiable dependency
    • python-unshare/arm64 has unsatisfiable dependency
    • python-unshare/armel has unsatisfiable dependency
    • python-unshare/armhf has unsatisfiable dependency
    • python-unshare/i386 has unsatisfiable dependency
    • python-unshare/mips64el has unsatisfiable dependency
    • python-unshare/mipsel has unsatisfiable dependency
    • python-unshare/ppc64el has unsatisfiable dependency
    • python-unshare/s390x has unsatisfiable dependency
    • Updating python-unshare would introduce bugs in testing: #938241
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-unshare.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
    • 2055 days old (needed 5 days)
• iptstate (- to 2.2.6-1)
  • Migration status for iptstate (- to 2.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iptstate would introduce bugs in testing: #994193
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptstate.html
    • 2069 days old (needed 5 days)
• rtpproxy (- to 1.2.1-2.2)
  • Migration status for rtpproxy (- to 1.2.1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rtpproxy would introduce bugs in testing: #874070, #979747
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rtpproxy.html
    • 2078 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
    • 2082 days old (needed 5 days)
• field3d (- to 1.7.2-1)
  • Migration status for field3d (- to 1.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating field3d would introduce bugs in testing: #939660
    • autopkgtest for field3d/1.7.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by mfv.debian@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/field3d.html
    • 2090 days old (needed 5 days)
• linux-wlan-ng (- to 0.2.9+dfsg-6)
  • Migration status for linux-wlan-ng (- to 0.2.9+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linux-wlan-ng would introduce bugs in testing: #991900
    • Not built on buildd: arch amd64 binaries uploaded by gareuselesinge
    • Not built on buildd: arch all binaries uploaded by gareuselesinge, a new source-only upload is needed to allow migration
    • Not touching package due to block request by jcristau (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-wlan-ng.html
    • 2097 days old (needed 5 days)
• lvtk (- to 1.2.0~dfsg0-2)
  • Migration status for lvtk (- to 1.2.0~dfsg0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lvtk would introduce bugs in testing: #967166
    • lvtk unsatisfiable Build-Depends(-Arch) on amd64: python
    • lvtk unsatisfiable Build-Depends(-Arch) on arm64: python
    • lvtk unsatisfiable Build-Depends(-Arch) on armel: python
    • lvtk unsatisfiable Build-Depends(-Arch) on armhf: python
    • lvtk unsatisfiable Build-Depends(-Arch) on i386: python
    • lvtk unsatisfiable Build-Depends(-Arch) on mips64el: python
    • lvtk unsatisfiable Build-Depends(-Arch) on mipsel: python
    • lvtk unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • lvtk unsatisfiable Build-Depends(-Arch) on s390x: python
    • Not built on buildd: arch all binaries uploaded by mira.mikes@seznam.cz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lvtk.html
    • 2101 days old (needed 5 days)
• haskell-doc (- to 20061128)
  • Migration status for haskell-doc (- to 20061128): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-doc haskell98-tutorial (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-doc.html
    • 2115 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Build-Depends(-Arch): arrayfire clblas
    • Depends: arrayfire clblas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arrayfire.html
    • 2124 days old (needed 5 days)
• pcb2gcode (- to 1.1.4-git20120902-1.1)
  • Migration status for pcb2gcode (- to 1.1.4-git20120902-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcb2gcode would introduce bugs in testing: #984286
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb2gcode.html
    • 2129 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:
    • Updating ecere-sdk would introduce bugs in testing: #898832, #995050
    • Impossible Depends: ecere-sdk -> libffi6/3.2.1-9/i386
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/amd64
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/arm64
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/armel
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/armhf
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/mips64el
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/mipsel
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/ppc64el
    • Impossible Depends: ecere-sdk -> libffi7/3.3-6/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecere-sdk.html
    • 2135 days old (needed 5 days)
• blcr (- to 0.8.5-2.3)
  • Migration status for blcr (- to 0.8.5-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating blcr would introduce bugs in testing: #876908, #877238, #965438
    • Build-Depends(-Arch): blcr dh-kpatches
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blcr.html
    • 2136 days old (needed 5 days)
• projectreactor (- to 2.0.8-1)
  • Migration status for projectreactor (- to 2.0.8-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/p/projectreactor.html
    • 2137 days old (needed 5 days)
• accelio (- to 1.7-2)
  • Migration status for accelio (- to 1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating accelio would introduce bugs in testing: #853298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/accelio.html
    • 2147 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:
    • Updating xorp would introduce bugs in testing: #947586, #958600
    • Impossible Build-Depends(-Arch): xorp -> dh-systemd/13.2.1/amd64
    • Impossible Build-Depends(-Arch): xorp -> dh-systemd/13.2.1/i386
    • Impossible Build-Depends(-Arch): xorp -> dh-systemd/13.2.1/ppc64el
    • Impossible Build-Depends(-Arch): xorp -> dh-systemd/13.2.1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xorp.html
    • 2148 days old (needed 5 days)
• ruby-virtus (- to 1.0.5-3)
  • Migration status for ruby-virtus (- to 1.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): ruby-virtus ruby-axiom-types (not considered)
    • Depends: ruby-virtus ruby-axiom-types (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-virtus.html
    • autopkgtest for ruby-virtus/1.0.5-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2151 days old (needed 2 days)
• tcpcrypt (- to 0.5-1)
  • Migration status for tcpcrypt (- to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcpcrypt would introduce bugs in testing: #958623
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/amd64
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/arm64
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/armel
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/armhf
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/i386
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/mips64el
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/mipsel
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/ppc64el
    • Impossible Build-Depends(-Arch): tcpcrypt -> dh-systemd/13.2.1/s390x
    • Depends: tcpcrypt openssl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcpcrypt.html
    • 2156 days old (needed 5 days)
• dircproxy (- to 1.0.5-6)
  • Migration status for dircproxy (- to 1.0.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dircproxy would introduce bugs in testing: #999031
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dircproxy.html
    • 2167 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: #953967
    • autopkgtest for grip/4.2.0-3: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grip.html
    • 2167 days old (needed 5 days)
• ipfm (- to 0.11.5-4.2)
  • Migration status for ipfm (- to 0.11.5-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ipfm would introduce bugs in testing: #999164
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipfm.html
    • 2174 days old (needed 5 days)
• leaktracer (- to 2.4-6)
  • Migration status for leaktracer (- to 2.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leaktracer would introduce bugs in testing: #998951
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leaktracer.html
    • 2178 days old (needed 5 days)
• libretro-snes9x (- to 1.53+git20160522-1)
  • Migration status for libretro-snes9x (- to 1.53+git20160522-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-snes9x would introduce bugs in testing: #998228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2181 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
    • 2188 days old (needed 5 days)
• icheck (- to 0.9.7-6.3)
  • Migration status for icheck (- to 0.9.7-6.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating icheck would introduce bugs in testing: #999090
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icheck.html
    • 2192 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/mipsel has unsatisfiable dependency
    • libelektra4-python/mipsel has unsatisfiable dependency
    • python3-elektra/mipsel 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 mipsel: 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 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
    • 2198 days old (needed 5 days)
• genesisplusgx (- to 1.7.4+git20160410-1)
  • Migration status for genesisplusgx (- to 1.7.4+git20160410-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating genesisplusgx would introduce bugs in testing: #966108
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2202 days old (needed 5 days)
• ctfutils (- to 10.3~svn297264-2)
  • Migration status for ctfutils (- to 10.3~svn297264-2): 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
    • 2204 days old (needed 5 days)
• autofill-forms (- to 1.1.3-1)
  • Migration status for autofill-forms (- to 1.1.3-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
    • 2205 days old (needed 5 days)
• php-patchwork-utf8 (- to 1.3.1-1)
  • Migration status for php-patchwork-utf8 (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-patchwork-utf8 would introduce bugs in testing: #935246
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-patchwork-utf8.html
    • 2212 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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
    • 2212 days old (needed 5 days)
• graxxia (- to 1.0~20150714-2)
  • Migration status for graxxia (- to 1.0~20150714-2): 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/g/graxxia.html
    • 2213 days old (needed 5 days)
• tldp (- to 0.7.13-1)
  • Migration status for tldp (- to 0.7.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tldp would introduce bugs in testing: #867261
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): tldp sgml2x
    • Depends: tldp sgml2x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tldp.html
    • 2218 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
    • 2219 days old (needed 5 days)
• libblkmaker (- to 0.5.3-1)
  • Migration status for libblkmaker (- to 0.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libblkmaker would introduce bugs in testing: #858377, #899568
    • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libblkmaker.html
    • 2245 days old (needed 5 days)
• fizmo (- to 0.7.10-2)
  • Migration status for fizmo (- to 0.7.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fizmo would introduce bugs in testing: #877015
    • Not built on buildd: arch all binaries uploaded by pmatthaei, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fizmo.html
    • 2247 days old (needed 5 days)
• php-services-weather (- to 1.4.7-4)
  • Migration status for php-services-weather (- to 1.4.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sathieu, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): php-services-weather php-db
    • Depends: php-services-weather php-http-request
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-services-weather.html
    • 2256 days old (needed 5 days)
• php-numbers-words (- to 0.18.1-2)
  • Migration status for php-numbers-words (- to 0.18.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-numbers-words would introduce bugs in testing: #882901
    • autopkgtest for php-numbers-words/0.18.1-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-numbers-words.html
    • 2271 days old (needed 5 days)
• hidrd (- to 0.2.0-12)
  • Migration status for hidrd (- to 0.2.0-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hidrd would introduce bugs in testing: #822379, #853443
    • Not built on buildd: arch amd64 binaries uploaded by klee@mit.edu
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • missing build on armel
    • missing build on armhf
    • missing build on ppc64el
    • missing build on s390x
    • 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/h/hidrd.html
    • 2275 days old (needed 5 days)
• php-http-request2 (- to 2.3.0-1)
  • Migration status for php-http-request2 (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-http-request2 would introduce bugs in testing: #882910
    • autopkgtest for php-http-request2/2.3.0-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-request2.html
    • 2275 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-uri.html
    • 2275 days old (needed 5 days)
• ruby-omniauth-remote-user (- to 0.1.3-1)
  • Migration status for ruby-omniauth-remote-user (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-remote-user would introduce bugs in testing: #959557, #999723
    • autopkgtest for ruby-omniauth-remote-user/0.1.3-1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by christian@hofstaedtler.name, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-remote-user.html
    • 2280 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • 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
    • 2281 days old (needed 5 days)
• edgar (- to 1.23-1)
  • Migration status for edgar (- to 1.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating edgar would introduce bugs in testing: #832116
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edgar.html
    • 2282 days old (needed 5 days)
• php-http-request (- to 1.4.4-5)
  • Migration status for php-http-request (- to 1.4.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-http-request would introduce bugs in testing: #860336
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-request.html
    • 2287 days old (needed 5 days)
• freebsd-glue (- to 0.2.22)
  • Migration status for freebsd-glue (- to 0.2.22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freebsd-glue would introduce bugs in testing: #964661
    • Build-Depends(-Arch): freebsd-glue freebsd-buildutils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-glue.html
    • 2288 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 ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-event.html
    • 2289 days old (needed 5 days)
• ruby-omniauth-tumblr (- to 1.2-1)
  • Migration status for ruby-omniauth-tumblr (- to 1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-omniauth-tumblr ruby-omniauth-oauth (not considered)
    • Depends: ruby-omniauth-tumblr ruby-omniauth-oauth (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-tumblr.html
    • 2289 days old (needed 5 days)
• ikvm (- to 8.1.5717.0+ds-1)
  • Migration status for ikvm (- to 8.1.5717.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ikvm would introduce bugs in testing: #806624, #894353
    • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by directhex
    • Build-Depends(-Arch): ikvm nant
    • Build-Depends-Indep: ikvm openjdk-8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ikvm.html
    • 2303 days old (needed 5 days)
• doc-linux-fr (- to 2013.01-3)
  • Migration status for doc-linux-fr (- to 2013.01-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating doc-linux-fr would introduce bugs in testing: #880786, #906953, #910813
    • doc-linux-fr unsatisfiable Build-Depends-Indep on amd64: lynx-cur
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doc-linux-fr.html
    • 2312 days old (needed 5 days)
• obexpushd (- to 0.11.2-1.1)
  • Migration status for obexpushd (- to 0.11.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obexpushd would introduce bugs in testing: #906496
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obexpushd.html
    • 2314 days old (needed 5 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
    • 2322 days old (needed 5 days)
• icmpush (- to 2.2-6.1)
  • Migration status for icmpush (- to 2.2-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating icmpush would introduce bugs in testing: #999158
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icmpush.html
    • 2338 days old (needed 5 days)
• tetradraw (- to 2.0.3-9)
  • Migration status for tetradraw (- to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tetradraw would introduce bugs in testing: #716386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tetradraw.html
    • 2343 days old (needed 5 days)
• cduce (- to 0.6.0-5)
  • Migration status for cduce (- to 0.6.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cduce/amd64 has unsatisfiable dependency
    • cduce/arm64 has unsatisfiable dependency
    • cduce/armel has unsatisfiable dependency
    • cduce/armhf has unsatisfiable dependency
    • cduce/i386 has unsatisfiable dependency
    • Updating cduce would introduce bugs in testing: #878983
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cduce.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
    • 2361 days old (needed 5 days)
• libapache-mod-auth-radius (- to 1.5.8-1.3)
  • Migration status for libapache-mod-auth-radius (- to 1.5.8-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-mod-auth-radius would introduce bugs in testing: #965623, #998925
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-auth-radius.html
    • 2362 days old (needed 5 days)
• git-notifier (- to 1:0.6-25-1)
  • Migration status for git-notifier (- to 1:0.6-25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • git-notifier/amd64 has unsatisfiable dependency
    • git-notifier/arm64 has unsatisfiable dependency
    • Updating git-notifier would introduce bugs in testing: #945677
    • Not built on buildd: arch all binaries uploaded by edmonds, 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/g/git-notifier.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 2365 days old (needed 5 days)
• libdjconsole (- to 0.1.3-3)
  • Migration status for libdjconsole (- to 0.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdjconsole would introduce bugs in testing: #984100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdjconsole.html
    • 2368 days old (needed 5 days)
• dvcs-autosync (- to 0.5+nmu1)
  • Migration status for dvcs-autosync (- to 0.5+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dvcs-autosync/amd64 has unsatisfiable dependency
    • dvcs-autosync/arm64 has unsatisfiable dependency
    • Updating dvcs-autosync would introduce bugs in testing: #936459
    • dvcs-autosync unsatisfiable Build-Depends(-Arch) on amd64: python
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dvcs-autosync.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 2370 days old (needed 5 days)
• npgsql (- to 2.2.7+dfsg3-1)
  • Migration status for npgsql (- to 2.2.7+dfsg3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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/n/npgsql.html
    • 2372 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:
    • Updating fsharp would introduce bugs in testing: #905449
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/fsharp.html
    • autopkgtest for fsharp/4.0.0.4+dfsg2-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
    • 2374 days old (needed 5 days)
• sockjs-client (- to 0.3.4+dfsg-2)
  • Migration status for sockjs-client (- to 0.3.4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sockjs-client would introduce bugs in testing: #979958
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sockjs-client.html
    • 2377 days old (needed 5 days)
• monobristol (- to 0.60.3-3)
  • Migration status for monobristol (- to 0.60.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating monobristol would introduce bugs in testing: #881911
    • 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/m/monobristol.html
    • 2397 days old (needed 5 days)
• mod-gearman (- to 1.5.5-1)
  • Migration status for mod-gearman (- to 1.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mod-gearman-tools/amd64 has unsatisfiable dependency
    • mod-gearman-worker/amd64 has unsatisfiable dependency
    • mod-gearman-tools/arm64 has unsatisfiable dependency
    • mod-gearman-worker/arm64 has unsatisfiable dependency
    • mod-gearman-tools/armel has unsatisfiable dependency
    • mod-gearman-worker/armel has unsatisfiable dependency
    • mod-gearman-tools/armhf has unsatisfiable dependency
    • mod-gearman-worker/armhf has unsatisfiable dependency
    • mod-gearman-tools/i386 has unsatisfiable dependency
    • mod-gearman-worker/i386 has unsatisfiable dependency
    • mod-gearman-tools/mips64el has unsatisfiable dependency
    • mod-gearman-worker/mips64el has unsatisfiable dependency
    • mod-gearman-tools/mipsel has unsatisfiable dependency
    • mod-gearman-worker/mipsel has unsatisfiable dependency
    • mod-gearman-tools/ppc64el has unsatisfiable dependency
    • mod-gearman-worker/ppc64el has unsatisfiable dependency
    • mod-gearman-tools/s390x has unsatisfiable dependency
    • mod-gearman-worker/s390x has unsatisfiable dependency
    • Updating mod-gearman would introduce bugs in testing: #957557, #958618, #967856
    • Not built on buildd: arch all binaries uploaded by bzed, a new source-only upload is needed to allow migration
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/amd64
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/arm64
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/armel
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/armhf
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/i386
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/mips64el
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/mipsel
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/ppc64el
    • Impossible Build-Depends(-Arch): mod-gearman -> dh-systemd/13.2.1/s390x
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mod-gearman.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
    • 2410 days old (needed 5 days)
• dhis-mx-sendmail-engine (- to 5.0-3)
  • Migration status for dhis-mx-sendmail-engine (- to 5.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dhis-mx-sendmail-engine dhis-server (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhis-mx-sendmail-engine.html
    • 2448 days old (needed 5 days)
• vdr-plugin-infosatepg (- to 0.0.12-6)
  • Migration status for vdr-plugin-infosatepg (- to 0.0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vdr-plugin-infosatepg/amd64 has unsatisfiable dependency
    • vdr-plugin-infosatepg/arm64 has unsatisfiable dependency
    • vdr-plugin-infosatepg/armel has unsatisfiable dependency
    • vdr-plugin-infosatepg/armhf has unsatisfiable dependency
    • vdr-plugin-infosatepg/i386 has unsatisfiable dependency
    • vdr-plugin-infosatepg/mips64el has unsatisfiable dependency
    • vdr-plugin-infosatepg/mipsel has unsatisfiable dependency
    • vdr-plugin-infosatepg/ppc64el has unsatisfiable dependency
    • vdr-plugin-infosatepg/s390x has unsatisfiable dependency
    • Updating vdr-plugin-infosatepg would introduce bugs in testing: #872487
    • Not built on buildd: arch amd64 binaries uploaded by etobi
    • 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/v/vdr-plugin-infosatepg.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
    • 2453 days old (needed 5 days)
• vdr-plugin-remoteosd (- to 1.0.0-5)
  • Migration status for vdr-plugin-remoteosd (- to 1.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vdr-plugin-remoteosd/amd64 has unsatisfiable dependency
    • vdr-plugin-remoteosd/arm64 has unsatisfiable dependency
    • vdr-plugin-remoteosd/armel has unsatisfiable dependency
    • vdr-plugin-remoteosd/armhf has unsatisfiable dependency
    • vdr-plugin-remoteosd/i386 has unsatisfiable dependency
    • vdr-plugin-remoteosd/mips64el has unsatisfiable dependency
    • vdr-plugin-remoteosd/mipsel has unsatisfiable dependency
    • vdr-plugin-remoteosd/ppc64el has unsatisfiable dependency
    • vdr-plugin-remoteosd/s390x has unsatisfiable dependency
    • Updating vdr-plugin-remoteosd would introduce bugs in testing: #872495
    • Not built on buildd: arch amd64 binaries uploaded by etobi
    • 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/v/vdr-plugin-remoteosd.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
    • 2453 days old (needed 5 days)
• wmdate (- to 0.7-4.1)
  • Migration status for wmdate (- to 0.7-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmdate would introduce bugs in testing: #965879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmdate.html
    • 2467 days old (needed 5 days)
• cutter (- to 1.04-1)
  • Migration status for cutter (- to 1.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cutter would introduce bugs in testing: #446343
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cutter.html
    • 2474 days old (needed 5 days)
• juman (- to 7.0-3.4)
  • Migration status for juman (- to 7.0-3.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating juman would introduce bugs in testing: #957392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/juman.html
    • 2475 days old (needed 5 days)
• tagcloud (- to 1.4-1.2)
  • Migration status for tagcloud (- to 1.4-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tagcloud would introduce bugs in testing: #999296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tagcloud.html
    • 2475 days old (needed 5 days)
• vcheck (- to 1.2.1-7.1)
  • Migration status for vcheck (- to 1.2.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vcheck would introduce bugs in testing: #965861
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vcheck.html
    • 2475 days old (needed 5 days)
• yapra (- to 0.1.2-7.1)
  • Migration status for yapra (- to 0.1.2-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yapra would introduce bugs in testing: #965908
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yapra.html
    • 2484 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
    • 2489 days old (needed 5 days)
• opennebula-context (- to 4.14.0-1)
  • Migration status for opennebula-context (- to 4.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opennebula-context would introduce bugs in testing: #899908
    • Not built on buildd: arch all binaries uploaded by onlyjob@member.fsf.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opennebula-context.html
    • 2489 days old (needed 5 days)
• slurm (- to 0.4.3-2)
  • Migration status for slurm (- to 0.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slurm would introduce bugs in testing: #993874
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slurm.html
    • 2489 days old (needed 5 days)
• smtm (- to 1.6.11)
  • Migration status for smtm (- to 1.6.11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smtm would introduce bugs in testing: #965825
    • Not built on buildd: arch all binaries uploaded by edd, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: smtm finance-yahooquote
    • Depends: smtm finance-yahooquote
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smtm.html
    • 2490 days old (needed 5 days)
• lua-apr (- to 0.23.2.dfsg-4)
  • Migration status for lua-apr (- to 0.23.2.dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lua-apr would introduce bugs in testing: #935271
    • Not built on buildd: arch amd64 binaries uploaded by gareuselesinge
    • Not built on buildd: arch all binaries uploaded by gareuselesinge, a new source-only upload is needed to allow migration
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/armel
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/i386
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/mipsel
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.57+dfsg-3+deb11u1/s390x
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.59+dfsg-1+b1/amd64
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.59+dfsg-1+b1/arm64
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.59+dfsg-1+b1/armhf
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.59+dfsg-1+b1/mips64el
    • Impossible Depends: lua-apr -> libldap-2.4-2/2.4.59+dfsg-1+b1/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-apr.html
    • 2492 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
    • 2500 days old (needed 5 days)
• mrtg-rrd (- to 0.7-5.1)
  • Migration status for mrtg-rrd (- to 0.7-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mrtg-rrd would introduce bugs in testing: #799097, #965734
    • Not built on buildd: arch all binaries uploaded by dmn, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrtg-rrd.html
    • 2505 days old (needed 5 days)
• hunt (- to 1.5-6.1)
  • Migration status for hunt (- to 1.5-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hunt would introduce bugs in testing: #965588, #998955
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hunt.html
    • 2512 days old (needed 5 days)
• angband-audio (- to 1:3.1.0-1)
  • Migration status for angband-audio (- to 1:3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating angband-audio would introduce bugs in testing: #793668
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2514 days old (needed 5 days)
• mz (- to 0.40-1.1)
  • Migration status for mz (- to 0.40-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mz would introduce bugs in testing: #957573, #961969
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mz.html
    • 2514 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yap.html
    • uninstallable on arch i386, not running autopkgtest there
    • autopkgtest for yap/6.2.2-6: amd64: Pass, arm64: Pass, armhf: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2523 days old (needed 2 days)
• cgminer (- to 4.9.2-1)
  • Migration status for cgminer (- to 4.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cgminer would introduce bugs in testing: #899467, #900929, #987939
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cgminer.html
    • 2542 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
    • 2557 days old (needed 5 days)
• libcolor-calc-perl (- to 1.074-2)
  • Migration status for libcolor-calc-perl (- to 1.074-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcolor-calc-perl would introduce bugs in testing: #961147
    • autopkgtest for libcolor-calc-perl/1.074-2: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
    • Not built on buildd: arch all binaries uploaded by ntyni, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcolor-calc-perl.html
    • 2566 days old (needed 5 days)
• libodb-boost (- to 2.4.0-1)
  • Migration status for libodb-boost (- to 2.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libodb-boost libodb (not considered)
    • Depends: libodb-boost libodb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodb-boost.html
    • 2572 days old (needed 5 days)
• libodb (- to 2.4.0-1)
  • Migration status for libodb (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libodb would introduce bugs in testing: #984189
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodb.html
    • 2573 days old (needed 5 days)
• libodb-pgsql (- to 2.4.0-1)
  • Migration status for libodb-pgsql (- to 2.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libodb-pgsql libodb (not considered)
    • Depends: libodb-pgsql libodb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodb-pgsql.html
    • 2573 days old (needed 5 days)
• libodb-sqlite (- to 2.4.0-1)
  • Migration status for libodb-sqlite (- to 2.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libodb-sqlite libodb (not considered)
    • Depends: libodb-sqlite libodb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodb-sqlite.html
    • 2573 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
    • 2598 days old (needed 5 days)
• finance-yahooquote (- to 0.25)
  • Migration status for finance-yahooquote (- to 0.25): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating finance-yahooquote would introduce bugs in testing: #882305
    • Not built on buildd: arch all binaries uploaded by edd, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/finance-yahooquote.html
    • 2599 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
    • 2701 days old (needed 5 days)
• libwebcam (- to 0.2.4-1.1)
  • Migration status for libwebcam (- to 0.2.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libwebcam would introduce bugs in testing: #733094
    • Not built on buildd: arch all binaries uploaded by kraai, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwebcam.html
    • 2749 days old (needed 5 days)
• el-get (- to 3.1-1.1)
  • Migration status for el-get (- to 3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating el-get would introduce bugs in testing: #912364, #916857
    • Not built on buildd: arch all binaries uploaded by eriberto, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/el-get.html
    • 2757 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
    • 2785 days old (needed 5 days)
• srg (- to 1.3.6-2)
  • Migration status for srg (- to 1.3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating srg would introduce bugs in testing: #846449, #912072, #965828
    • Not built on buildd: arch amd64 binaries uploaded by mattb
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • Not built on buildd: arch ppc64el binaries uploaded by aba
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/srg.html
    • 2787 days old (needed 5 days)
• jack-tools (- to 20131226-1)
  • Migration status for jack-tools (- to 20131226-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jack-tools would introduce bugs in testing: #965600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jack-tools.html
    • 2795 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
    • 2804 days old (needed 5 days)
• googleearth-package (- to 1.2.2)
  • Migration status for googleearth-package (- to 1.2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating googleearth-package would introduce bugs in testing: #881580
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2806 days old (needed 5 days)
• fl-cow (- to 0.6-4.2)
  • Migration status for fl-cow (- to 0.6-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fl-cow would introduce bugs in testing: #999039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fl-cow.html
    • 2818 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
    • 2832 days old (needed 5 days)
• smbc (- to 1.2.2-4)
  • Migration status for smbc (- to 1.2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smbc would introduce bugs in testing: #957817, #965824, #999004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smbc.html
    • 2846 days old (needed 5 days)
• primesense-nite-nonfree (- to 0.1.1)
  • Migration status for primesense-nite-nonfree (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating primesense-nite-nonfree would introduce bugs in testing: #1002887, #771187
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2894 days old (needed 5 days)
• python-neuroshare (- to 0.9.2-1)
  • Migration status for python-neuroshare (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-neuroshare/amd64 has unsatisfiable dependency
    • python-neuroshare/arm64 has unsatisfiable dependency
    • python-neuroshare/armel has unsatisfiable dependency
    • python-neuroshare/armhf has unsatisfiable dependency
    • python-neuroshare/i386 has unsatisfiable dependency
    • python-neuroshare/mips64el has unsatisfiable dependency
    • python-neuroshare/mipsel has unsatisfiable dependency
    • python-neuroshare/ppc64el has unsatisfiable dependency
    • python-neuroshare/s390x has unsatisfiable dependency
    • Updating python-neuroshare would introduce bugs in testing: #937945
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on amd64: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on amd64: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on amd64: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on arm64: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on arm64: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on arm64: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on armel: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on armel: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on armel: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on armhf: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on armhf: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on armhf: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on i386: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on i386: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on i386: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on mips64el: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on mips64el: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on mips64el: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on mipsel: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on mipsel: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on mipsel: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on ppc64el: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on ppc64el: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on ppc64el: python-sphinx (>= 1.0.7+dfsg)
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on s390x: python-numpy
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on s390x: python-h5py
    • python-neuroshare unsatisfiable Build-Depends(-Arch) on s390x: python-sphinx (>= 1.0.7+dfsg)
    • Not built on buildd: arch all binaries uploaded by mih, 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/p/python-neuroshare.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
    • 2894 days old (needed 5 days)
• ez-ipupdate (- to 3.0.11b8-13.4.1)
  • Migration status for ez-ipupdate (- to 3.0.11b8-13.4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ez-ipupdate would introduce bugs in testing: #965512, #999270
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ez-ipupdate.html
    • 2901 days old (needed 5 days)
• minisapserver (- to 0.3.6-1.1)
  • Migration status for minisapserver (- to 0.3.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating minisapserver would introduce bugs in testing: #999123
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minisapserver.html
    • 2901 days old (needed 5 days)
• liblip (- to 2.0.0-1.2)
  • Migration status for liblip (- to 2.0.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liblip would introduce bugs in testing: #999142
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblip.html
    • 2904 days old (needed 5 days)
• redmine-recaptcha (- to 0.1.0+git20121018-3)
  • Migration status for redmine-recaptcha (- to 0.1.0+git20121018-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redmine-recaptcha would introduce bugs in testing: #830916, #876621, #925269
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine-recaptcha.html
    • Not built on buildd: arch all binaries uploaded by ender, a new source-only upload is needed to allow migration
  • Additional info:
    • 2923 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)
    • 2934 days old (needed 5 days)
• guessnet (- to 0.56)
  • Migration status for guessnet (- to 0.56): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guessnet would introduce bugs in testing: #984163
    • Build-Depends(-Arch): guessnet libwibble
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guessnet.html
    • 2951 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
    • 2958 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
    • 2964 days old (needed 5 days)
• libdispatch (- to 0~svn197-3.3)
  • Migration status for libdispatch (- to 0~svn197-3.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libdispatch libkqueue (not considered)
    • Depends: libdispatch libkqueue (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): libdispatch libpthread-workqueue
    • Depends: libdispatch libpthread-workqueue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdispatch.html
    • 3003 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
    • 3016 days old (needed 5 days)
• towitoko (- to 2.0.7-9)
  • Migration status for towitoko (- to 2.0.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating towitoko would introduce bugs in testing: #903937, #903940, #999058
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/towitoko.html
    • 3054 days old (needed 5 days)
• pd-aubio (- to 0.4-1)
  • Migration status for pd-aubio (- to 0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pd-aubio would introduce bugs in testing: #967193
    • pd-aubio unsatisfiable Build-Depends(-Arch) on amd64: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on arm64: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on armel: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on armhf: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on i386: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on mips64el: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on mipsel: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • pd-aubio unsatisfiable Build-Depends(-Arch) on s390x: python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pd-aubio.html
    • 3082 days old (needed 5 days)
• libapache2-mod-ruid2 (- to 0.9.8-3)
  • Migration status for libapache2-mod-ruid2 (- to 0.9.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-ruid2 would introduce bugs in testing: #866395
    • Not built on buildd: arch amd64 binaries uploaded by kobold
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-ruid2.html
    • 3119 days old (needed 5 days)
• tclgeoip (- to 0.2-1.1)
  • Migration status for tclgeoip (- to 0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tclgeoip would introduce bugs in testing: #965840, #999097
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tclgeoip.html
    • 3147 days old (needed 5 days)
• gpaint (- to 0.3.3-6.1)
  • Migration status for gpaint (- to 0.3.3-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpaint would introduce bugs in testing: #967144
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpaint.html
    • 3148 days old (needed 5 days)
• sortsmill-tools (- to 0.4-2)
  • Migration status for sortsmill-tools (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sortsmill-tools/amd64 has unsatisfiable dependency
    • sortsmill-tools/arm64 has unsatisfiable dependency
    • Updating sortsmill-tools would introduce bugs in testing: #938516
    • sortsmill-tools unsatisfiable Build-Depends(-Arch) on amd64: python (>= 2.6.6-3~)
    • Not built on buildd: arch all binaries uploaded by pabs, 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/s/sortsmill-tools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 3180 days old (needed 5 days)
• jcal (- to 0.4.1-2)
  • Migration status for jcal (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jcal would introduce bugs in testing: #965603
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jcal.html
    • 3188 days old (needed 5 days)
• kytea (- to 0.4.6+dfsg-2)
  • Migration status for kytea (- to 0.4.6+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libkytea0/amd64 has unsatisfiable dependency
    • libkytea0/arm64 has unsatisfiable dependency
    • libkytea0/armel has unsatisfiable dependency
    • libkytea0/armhf has unsatisfiable dependency
    • libkytea0/i386 has unsatisfiable dependency
    • libkytea0/mips64el has unsatisfiable dependency
    • libkytea0/mipsel has unsatisfiable dependency
    • libkytea0/ppc64el has unsatisfiable dependency
    • libkytea0/s390x has unsatisfiable dependency
    • Updating kytea would introduce bugs in testing: #799805
    • Not built on buildd: arch amd64 binaries uploaded by osamu
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kytea.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
    • 3190 days old (needed 5 days)
• perlrdf (- to 0.004-3)
  • Migration status for perlrdf (- to 0.004-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perlrdf.html
    • 3206 days old (needed 5 days)
• drac (- to 1.12-8)
  • Migration status for drac (- to 1.12-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drac would introduce bugs in testing: #965495, #997205, #999151
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drac.html
    • 3215 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)
    • 3219 days old (needed 5 days)
• vish (- to 0.0.20130812-1)
  • Migration status for vish (- to 0.0.20130812-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vish librevisa (not considered)
    • Depends: vish librevisa (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vish.html
    • 3224 days old (needed 5 days)
• pms (- to 0.42-1)
  • Migration status for pms (- to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pms would introduce bugs in testing: #996905
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pms.html
    • 3225 days old (needed 5 days)
• libapache2-mod-lisp (- to 1.3.1-1.3)
  • Migration status for libapache2-mod-lisp (- to 1.3.1-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-lisp would introduce bugs in testing: #965624, #999213
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-lisp.html
    • 3254 days old (needed 5 days)
• edb (- to 1.31-3)
  • Migration status for edb (- to 1.31-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating edb would introduce bugs in testing: #840748, #904010
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/edb.html
    • edb unsatisfiable Build-Depends-Indep on amd64: emacs24 | emacs-snapshot
    • Not built on buildd: arch all binaries uploaded by tats, a new source-only upload is needed to allow migration
  • Additional info:
    • 3265 days old (needed 5 days)
• dvbsnoop (- to 1.4.50-5)
  • Migration status for dvbsnoop (- to 1.4.50-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvbsnoop would introduce bugs in testing: #1005986, #965497
    • Build-Depends(-Arch): dvbsnoop dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvbsnoop.html
    • 3287 days old (needed 5 days)
• myodbc (- to 5.1.10-3)
  • Migration status for myodbc (- to 5.1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmyodbc/amd64 has unsatisfiable dependency
    • libmyodbc/arm64 has unsatisfiable dependency
    • libmyodbc/armel has unsatisfiable dependency
    • libmyodbc/armhf has unsatisfiable dependency
    • libmyodbc/i386 has unsatisfiable dependency
    • libmyodbc/mips64el has unsatisfiable dependency
    • libmyodbc/mipsel has unsatisfiable dependency
    • libmyodbc/ppc64el has unsatisfiable dependency
    • libmyodbc/s390x has unsatisfiable dependency
    • Updating myodbc would introduce bugs in testing: #835166, #841561, #849630, #852457, #868882
    • myodbc unsatisfiable Build-Depends(-Arch) on armel: libmysqlclient-dev (>= 5.5.17)
    • myodbc unsatisfiable Build-Depends(-Arch) on mipsel: libmysqlclient-dev (>= 5.5.17)
    • Not built on buildd: arch amd64 binaries uploaded by vorlon
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
    • Build-Depends(-Arch): myodbc mysql-8.0
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/myodbc.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
    • 3300 days old (needed 5 days)
• libkiokux-model-perl (- to 0.02-1)
  • Migration status for libkiokux-model-perl (- to 0.02-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by js, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkiokux-model-perl.html
    • 3312 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
    • 3322 days old (needed 5 days)
• looptools (- to 2.8-1)
  • Migration status for looptools (- to 2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating looptools would introduce bugs in testing: #957501
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/looptools.html
    • 3323 days old (needed 5 days)
• thp (- to 0.4.6-10)
  • Migration status for thp (- to 0.4.6-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating thp would introduce bugs in testing: #831952, #999222
    • Not built on buildd: arch all binaries uploaded by jfs, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thp.html
    • 3330 days old (needed 5 days)
• gxmms2 (- to 0.7.1-3)
  • Migration status for gxmms2 (- to 0.7.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gxmms2 xmms2 (not considered)
    • Depends: gxmms2 xmms2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gxmms2.html
    • 3368 days old (needed 5 days)
• sa-learn-cyrus (- to 0.3.5-1.1)
  • Migration status for sa-learn-cyrus (- to 0.3.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sa-learn-cyrus/amd64 has unsatisfiable dependency
    • sa-learn-cyrus/arm64 has unsatisfiable dependency
    • Updating sa-learn-cyrus would introduce bugs in testing: #830596
    • Not built on buildd: arch all binaries uploaded by gregoa, 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/s/sa-learn-cyrus.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 3383 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
    • Build-Depends(-Arch): xmms2-scrobbler xmms2
    • Depends: xmms2-scrobbler xmms2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2-scrobbler.html
    • 3385 days old (needed 5 days)
• vxi (- to 0.0.20121221-2)
  • Migration status for vxi (- to 0.0.20121221-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vxi would introduce bugs in testing: #997277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vxi.html
    • 3458 days old (needed 5 days)
• drbdlinks (- to 1.22-1)
  • Migration status for drbdlinks (- to 1.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • drbdlinks/amd64 has unsatisfiable dependency
    • drbdlinks/arm64 has unsatisfiable dependency
    • Updating drbdlinks would introduce bugs in testing: #945663, #965500
    • Not built on buildd: arch all binaries uploaded by thierry, 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/drbdlinks.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 3515 days old (needed 5 days)
• leave (- to 1.12-2.1)
  • Migration status for leave (- to 1.12-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leave would introduce bugs in testing: #999259
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leave.html
    • 3523 days old (needed 5 days)
• scim-skk (- to 0.5.2-7.2)
  • Migration status for scim-skk (- to 0.5.2-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scim-skk would introduce bugs in testing: #1005985, #998953
    • Build-Depends(-Arch): scim-skk dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scim-skk.html
    • 3573 days old (needed 5 days)
• masqmail (- to 0.3.4-1)
  • Migration status for masqmail (- to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating masqmail would introduce bugs in testing: #678493
    • Not built on buildd: arch amd64 binaries uploaded by jhr
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/masqmail.html
    • 3643 days old (needed 5 days)
• farpd (- to 0.2-11)
  • Migration status for farpd (- to 0.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating farpd would introduce bugs in testing: #998942
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/farpd.html
    • 3644 days old (needed 5 days)
• w3cam (- to 0.7.2-6.2)
  • Migration status for w3cam (- to 0.7.2-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3cam would introduce bugs in testing: #999081
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3cam.html
    • 3656 days old (needed 5 days)
• xdiskusage (- to 1.48-10.1)
  • Migration status for xdiskusage (- to 1.48-10.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xdiskusage would introduce bugs in testing: #965891, #999001
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdiskusage.html
    • 3664 days old (needed 5 days)
• ibam (- to 1:0.5.2-2.1)
  • Migration status for ibam (- to 1:0.5.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ibam would introduce bugs in testing: #669862, #998948
    • Build-Depends(-Arch): ibam dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibam.html
    • 3665 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
    • 3674 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
    • 3677 days old (needed 5 days)
• nxcl (- to 0.9-3.1)
  • Migration status for nxcl (- to 0.9-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nxcl would introduce bugs in testing: #965751, #999089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nxcl.html
    • 3681 days old (needed 5 days)
• vtkdata (- to 5.8.0-1)
  • Migration status for vtkdata (- to 5.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vtkdata would introduce bugs in testing: #864452
    • Not built on buildd: arch all binaries uploaded by bottoms, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtkdata.html
    • 3686 days old (needed 5 days)
• stalonetray (- to 0.8.1-1)
  • Migration status for stalonetray (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stalonetray would introduce bugs in testing: #965826
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stalonetray.html
    • 3688 days old (needed 5 days)
• mbw (- to 1.2.2-1)
  • Migration status for mbw (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mbw would introduce bugs in testing: #999328
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbw.html
    • 3699 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
    • 3705 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
    • 3706 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
    • 3713 days old (needed 5 days)
• zemberek-ooo (- to 1.0~rc2-10.4)
  • Migration status for zemberek-ooo (- to 1.0~rc2-10.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zemberek-ooo would introduce bugs in testing: #802416, #965924
    • Not built on buildd: arch all binaries uploaded by rene, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: zemberek-ooo zemberek
    • Depends: zemberek-ooo zemberek
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zemberek-ooo.html
    • 3714 days old (needed 5 days)
• cowbell (- to 0.2.7.1-7)
  • Migration status for cowbell (- to 0.2.7.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cowbell would introduce bugs in testing: #965473
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cowbell.html
    • 3716 days old (needed 5 days)
• pstotext (- to 1.9-6)
  • Migration status for pstotext (- to 1.9-6): 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
    • 3716 days old (needed 5 days)
• tralics (- to 2.14.4-2)
  • Migration status for tralics (- to 2.14.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tralics would introduce bugs in testing: #965847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tralics.html
    • 3719 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)
    • 3723 days old (needed 5 days)
• btag (- to 1.1.3-1)
  • Migration status for btag (- to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btag would introduce bugs in testing: #997224
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btag.html
    • 3735 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
    • 3743 days old (needed 5 days)
• php-services-json (- to 1.0.3-1)
  • Migration status for php-services-json (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-services-json would introduce bugs in testing: #823683
    • 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/php-services-json.html
    • 3757 days old (needed 5 days)
• php-mime-type (- to 1.3.1-1)
  • Migration status for php-mime-type (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mime-type would introduce bugs in testing: #783420
    • 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/php-mime-type.html
    • 3758 days old (needed 5 days)
• libgcr410 (- to 2.4.0-9.2)
  • Migration status for libgcr410 (- to 2.4.0-9.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgcr410 would introduce bugs in testing: #999332
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgcr410.html
    • 3760 days old (needed 5 days)
• midish (- to 1.0.4-1.1)
  • Migration status for midish (- to 1.0.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating midish would introduce bugs in testing: #999244
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/midish.html
    • 3778 days old (needed 5 days)
• raul (- to 0.8.0+dfsg0-0.1)
  • Migration status for raul (- to 0.8.0+dfsg0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating raul would introduce bugs in testing: #967207
    • raul unsatisfiable Build-Depends(-Arch) on amd64: python
    • raul unsatisfiable Build-Depends(-Arch) on arm64: python
    • raul unsatisfiable Build-Depends(-Arch) on armel: python
    • raul unsatisfiable Build-Depends(-Arch) on armhf: python
    • raul unsatisfiable Build-Depends(-Arch) on i386: python
    • raul unsatisfiable Build-Depends(-Arch) on mips64el: python
    • raul unsatisfiable Build-Depends(-Arch) on mipsel: python
    • raul unsatisfiable Build-Depends(-Arch) on ppc64el: python
    • raul unsatisfiable Build-Depends(-Arch) on s390x: python
    • Not built on buildd: arch all binaries uploaded by alessio, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raul.html
    • 3802 days old (needed 5 days)
• sac (- to 1.9b5-3)
  • Migration status for sac (- to 1.9b5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sac would introduce bugs in testing: #965807, #999192
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sac.html
    • 3820 days old (needed 5 days)
• jodreports (- to 2.4.0-3)
  • Migration status for jodreports (- to 2.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by twerner, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jodreports.html
    • 3847 days old (needed 5 days)
• dis51 (- to 0.5-1.1)
  • Migration status for dis51 (- to 0.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dis51 would introduce bugs in testing: #965488
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dis51.html
    • 3853 days old (needed 5 days)
• concalc (- to 0.9.2-2)
  • Migration status for concalc (- to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating concalc would introduce bugs in testing: #965467
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/concalc.html
    • 3863 days old (needed 5 days)
• spd (- to 1.3.0-1)
  • Migration status for spd (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spd would introduce bugs in testing: #925834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spd.html
    • 3865 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
    • 3900 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
    • 3905 days old (needed 5 days)
• gpr (- to 0.15deb-2)
  • Migration status for gpr (- to 0.15deb-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpr would introduce bugs in testing: #1005435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpr.html
    • 3907 days old (needed 5 days)
• snmpkit (- to 0.9-16)
  • Migration status for snmpkit (- to 0.9-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating snmpkit would introduce bugs in testing: #857299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snmpkit.html
    • 3908 days old (needed 5 days)
• nslint (- to 3.0a2-1.1)
  • Migration status for nslint (- to 3.0a2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nslint would introduce bugs in testing: #965749, #998985
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nslint.html
    • 3941 days old (needed 5 days)
• latrace (- to 0.5.11-1)
  • Migration status for latrace (- to 0.5.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating latrace would introduce bugs in testing: #890457, #907308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latrace.html
    • 3958 days old (needed 5 days)
• combat (- to 0.8.1-1)
  • Migration status for combat (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating combat would introduce bugs in testing: #899479
    • Not built on buildd: arch all binaries uploaded by tgg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/combat.html
    • 3963 days old (needed 5 days)
• gkrellm-x86info (- to 0.0.2-9)
  • Migration status for gkrellm-x86info (- to 0.0.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gkrellm-x86info would introduce bugs in testing: #1002714, #669731, #998977
    • Build-Depends(-Arch): gkrellm-x86info dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gkrellm-x86info.html
    • 3973 days old (needed 5 days)
• coinor-flopc++ (- to 1.0.6-3.1)
  • Migration status for coinor-flopc++ (- to 1.0.6-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coinor-flopc++ would introduce bugs in testing: #897723, #965464
    • Not built on buildd: arch all binaries uploaded by luk, a new source-only upload is needed to allow migration
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coinor-flopc++.html
    • 3995 days old (needed 5 days)
• libuninum (- to 2.7-1.1)
  • Migration status for libuninum (- to 2.7-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libuninum would introduce bugs in testing: #965695, #999178
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libuninum.html
    • 3998 days old (needed 5 days)
• python-pmw (- to 1.3.2-6)
  • Migration status for python-pmw (- to 1.3.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-pmw/amd64 has unsatisfiable dependency
    • python-pmw/arm64 has unsatisfiable dependency
    • Updating python-pmw would introduce bugs in testing: #886617, #938036, #966783
    • Not built on buildd: arch all binaries uploaded by segre, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pmw.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 4007 days old (needed 5 days)
• iitalian (- to 1:2.3-3)
  • Migration status for iitalian (- to 1:2.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iitalian would introduce bugs in testing: #965591, #996361, #999201
    • autopkgtest for courier/n/a: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iitalian.html
    • 4042 days old (needed 5 days)
• hasciicam (- to 1.1.2-1)
  • Migration status for hasciicam (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hasciicam would introduce bugs in testing: #965578
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hasciicam.html
    • 4063 days old (needed 5 days)
• v86d (- to 0.1.10-1)
  • Migration status for v86d (- to 0.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating v86d would introduce bugs in testing: #965866, #998975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/v86d.html
    • 4063 days old (needed 5 days)
• cl-umlisp (- to 1:2007ac.2-6)
  • Migration status for cl-umlisp (- to 1:2007ac.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-umlisp would introduce bugs in testing: #998935
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4087 days old (needed 5 days)
• cl-umlisp-orf (- to 3.3.2-3)
  • Migration status for cl-umlisp-orf (- to 3.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-umlisp-orf would introduce bugs in testing: #999165
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4087 days old (needed 5 days)
• dhis-server (- to 5.3-2.1)
  • Migration status for dhis-server (- to 5.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dhis-server would introduce bugs in testing: #999124
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhis-server.html
    • 4104 days old (needed 5 days)
• flobopuyo (- to 0.20-5)
  • Migration status for flobopuyo (- to 0.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flobopuyo would introduce bugs in testing: #965523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flobopuyo.html
    • 4107 days old (needed 5 days)
• desklaunch (- to 1.1.8)
  • Migration status for desklaunch (- to 1.1.8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating desklaunch would introduce bugs in testing: #998966
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/desklaunch.html
    • 4210 days old (needed 5 days)
• vrrpd (- to 1.0-2)
  • Migration status for vrrpd (- to 1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vrrpd would introduce bugs in testing: #965871, #999060
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vrrpd.html
    • 4244 days old (needed 5 days)
• vsdump (- to 0.0.45-1)
  • Migration status for vsdump (- to 0.0.45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vsdump would introduce bugs in testing: #965868, #999301
    • Build-Depends(-Arch): vsdump dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vsdump.html
    • 4350 days old (needed 5 days)
• libpam-blue (- to 0.9.0-3)
  • Migration status for libpam-blue (- to 0.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-blue would introduce bugs in testing: #965674, #999318
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-blue.html
    • 4393 days old (needed 5 days)
• xcolmix (- to 1.07-10)
  • Migration status for xcolmix (- to 1.07-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcolmix would introduce bugs in testing: #999219
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcolmix.html
    • 4397 days old (needed 5 days)
• xplot (- to 1.19-9)
  • Migration status for xplot (- to 1.19-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xplot would introduce bugs in testing: #999308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xplot.html
    • 4397 days old (needed 5 days)
• xwrits (- to 2.21-6.1)
  • Migration status for xwrits (- to 2.21-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xwrits would introduce bugs in testing: #999114
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xwrits.html
    • 4403 days old (needed 5 days)
• spew (- to 1.0.8-1)
  • Migration status for spew (- to 1.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spew would introduce bugs in testing: #998965
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spew.html
    • 4410 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
    • 4464 days old (needed 5 days)
• floatbg (- to 1.0-28)
  • Migration status for floatbg (- to 1.0-28): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating floatbg would introduce bugs in testing: #999330
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/floatbg.html
    • 4468 days old (needed 5 days)
• printfilters-ppd (- to 2.13-11.1)
  • Migration status for printfilters-ppd (- to 2.13-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • printfilters-ppd/amd64 has unsatisfiable dependency
    • printfilters-ppd/arm64 has unsatisfiable dependency
    • printfilters-ppd/armel has unsatisfiable dependency
    • printfilters-ppd/armhf has unsatisfiable dependency
    • printfilters-ppd/i386 has unsatisfiable dependency
    • printfilters-ppd/mips64el has unsatisfiable dependency
    • printfilters-ppd/mipsel has unsatisfiable dependency
    • printfilters-ppd/ppc64el has unsatisfiable dependency
    • printfilters-ppd/s390x has unsatisfiable dependency
    • Updating printfilters-ppd would introduce bugs in testing: #876566, #965788, #999212
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/printfilters-ppd.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
    • 4470 days old (needed 5 days)
• portreserve (- to 0.0.4-1)
  • Migration status for portreserve (- to 0.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating portreserve would introduce bugs in testing: #965783, #999140
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/portreserve.html
    • 4495 days old (needed 5 days)
• deskmenu (- to 1.4.5)
  • Migration status for deskmenu (- to 1.4.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deskmenu would introduce bugs in testing: #999241
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deskmenu.html
    • 4498 days old (needed 5 days)
• keylaunch (- to 1.3.9)
  • Migration status for keylaunch (- to 1.3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating keylaunch would introduce bugs in testing: #999135
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keylaunch.html
    • 4498 days old (needed 5 days)
• mailto (- to 1.3.2-3)
  • Migration status for mailto (- to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailto would introduce bugs in testing: #998978
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailto.html
    • 4528 days old (needed 5 days)
• crafty-books-medium (- to 1.0.debian1-2)
  • Migration status for crafty-books-medium (- to 1.0.debian1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crafty-books-medium would introduce bugs in testing: #999036
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4533 days old (needed 5 days)
• crafty-books-medtosmall (- to 1.0.debian1-2)
  • Migration status for crafty-books-medtosmall (- to 1.0.debian1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crafty-books-medtosmall would introduce bugs in testing: #999091
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4533 days old (needed 5 days)
• crafty-books-small (- to 1.0.debian1-2)
  • Migration status for crafty-books-small (- to 1.0.debian1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crafty-books-small would introduce bugs in testing: #998983
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4533 days old (needed 5 days)
• swac-get (- to 0.3-2.1)
  • Migration status for swac-get (- to 0.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swac-get would introduce bugs in testing: #965831, #999179
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swac-get.html
    • 4548 days old (needed 5 days)
• hawknl (- to 1.6.8+dfsg2-1)
  • Migration status for hawknl (- to 1.6.8+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hawknl would introduce bugs in testing: #965579, #999277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hawknl.html
    • 4555 days old (needed 5 days)
• empire-lafe (- to 1.1-1)
  • Migration status for empire-lafe (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating empire-lafe would introduce bugs in testing: #999280
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/empire-lafe.html
    • 4557 days old (needed 5 days)
• gnuit (- to 4.9.5-3)
  • Migration status for gnuit (- to 4.9.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnuit would introduce bugs in testing: #965566, #998945
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuit.html
    • 4594 days old (needed 5 days)
• gtkpool (- to 0.5.0-9)
  • Migration status for gtkpool (- to 0.5.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkpool would introduce bugs in testing: #965575, #999174
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkpool.html
    • 4594 days old (needed 5 days)
• gplcver (- to 2.12a-1.1)
  • Migration status for gplcver (- to 2.12a-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gplcver would introduce bugs in testing: #965565
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gplcver.html
    • 4637 days old (needed 5 days)
• madwimax (- to 0.1.1-1)
  • Migration status for madwimax (- to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating madwimax would introduce bugs in testing: #999230
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/madwimax.html
    • 4639 days old (needed 5 days)
• resample (- to 1.8.1-1)
  • Migration status for resample (- to 1.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resample would introduce bugs in testing: #965801
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resample.html
    • 4650 days old (needed 5 days)
• randomsound (- to 0.2-5)
  • Migration status for randomsound (- to 0.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating randomsound would introduce bugs in testing: #965796, #999258
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/randomsound.html
    • 4653 days old (needed 5 days)
• dbench (- to 4.0-2)
  • Migration status for dbench (- to 4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dbench would introduce bugs in testing: #965484, #999156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbench.html
    • 4802 days old (needed 5 days)
• socket (- to 1.1-10)
  • Migration status for socket (- to 1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socket would introduce bugs in testing: #965823, #999271
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket.html
    • 4805 days old (needed 5 days)
• setcd (- to 1.5-6)
  • Migration status for setcd (- to 1.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating setcd would introduce bugs in testing: #965821, #998970
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/setcd.html
    • 4806 days old (needed 5 days)
• mkelfimage (- to 2.7-7)
  • Migration status for mkelfimage (- to 2.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mkelfimage would introduce bugs in testing: #965725
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkelfimage.html
    • 4837 days old (needed 5 days)
• sbrsh (- to 7.6.1)
  • Migration status for sbrsh (- to 7.6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sbrsh would introduce bugs in testing: #965809, #999043
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbrsh.html
    • 4841 days old (needed 5 days)
• gbase (- to 0.5-2.2)
  • Migration status for gbase (- to 0.5-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gbase would introduce bugs in testing: #965536, #998989
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbase.html
    • 4855 days old (needed 5 days)
• fdflush (- to 1.0.1.3)
  • Migration status for fdflush (- to 1.0.1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fdflush would introduce bugs in testing: #965520, #999200
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdflush.html
    • 4911 days old (needed 5 days)
• fig2sxd (- to 0.20-1)
  • Migration status for fig2sxd (- to 0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fig2sxd would introduce bugs in testing: #965518
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fig2sxd.html
    • 4966 days old (needed 5 days)
• selfhtml (- to 8.1.2-1)
  • Migration status for selfhtml (- to 8.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating selfhtml would introduce bugs in testing: #1002966
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4982 days old (needed 5 days)
• cryptcat (- to 20031202-4)
  • Migration status for cryptcat (- to 20031202-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cryptcat would introduce bugs in testing: #670928, #965470, #999150
    • Build-Depends(-Arch): cryptcat dpatch
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptcat.html
    • 5039 days old (needed 5 days)
• falselogin (- to 0.3-4)
  • Migration status for falselogin (- to 0.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating falselogin would introduce bugs in testing: #965514, #999289
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/falselogin.html
    • 5069 days old (needed 5 days)
• itop (- to 0.1-4)
  • Migration status for itop (- to 0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating itop would introduce bugs in testing: #904206, #965601, #999317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itop.html
    • 5085 days old (needed 5 days)
• iat (- to 0.1.3-7)
  • Migration status for iat (- to 0.1.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iat would introduce bugs in testing: #965589, #999305
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iat.html
    • 5125 days old (needed 5 days)
• multimail (- to 0.49-2)
  • Migration status for multimail (- to 0.49-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating multimail would introduce bugs in testing: #965737, #998938
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multimail.html
    • 5175 days old (needed 5 days)
• fapg (- to 0.41-1)
  • Migration status for fapg (- to 0.41-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fapg would introduce bugs in testing: #965516, #999118
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fapg.html
    • 5204 days old (needed 5 days)
• wmcpu (- to 1.4-4)
  • Migration status for wmcpu (- to 1.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmcpu would introduce bugs in testing: #965877
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmcpu.html
    • 5208 days old (needed 5 days)
• cue2toc (- to 0.4-5)
  • Migration status for cue2toc (- to 0.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cue2toc would introduce bugs in testing: #965475, #999171
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cue2toc.html
    • 5226 days old (needed 5 days)
• ftjam (- to 2.5.2-1.1)
  • Migration status for ftjam (- to 2.5.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ftjam would introduce bugs in testing: #965524, #998979
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ftjam.html
    • 5366 days old (needed 5 days)
• tcd-utils (- to 20061127-2)
  • Migration status for tcd-utils (- to 20061127-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcd-utils would introduce bugs in testing: #965835, #999110
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcd-utils.html
    • 5386 days old (needed 5 days)